Accessing the MBean for ProcessRuntime(WLI) through WLST

Question

Since the cmo is not available for Custom MBeans and WLI MBeans are custom, how can I access or execute the methods for the MBean from WLST. I guess I can probably do it with the invoke command but the sytax foroperation invocation is not that intuitive. Is there another way i can access the ProcessRuntime Bean and invoke the methods directly.
Thanks.

Answer 1

Marc,
This is just a guess(have'nt done this), but I think the settings are not an exception, and you should be able to find the MBean here:
http://docs.oracle.com/cd/E17904_01/webcenter.1111/e12405/wcadm_intro.htm#BHCCJJED
This section of the doc seems to walk through an example setting properties in adf-config.xml
I would interpret those instructions in the official doc to mean :
1. If you don't mind changing this at deploy time and re-deploying(like we do when we're in deep development), you can change this and redeploy.
2. If you have a deployed application, you can make changes through WLST. But keep in mind that the changes you make through WLST will not be overwritten later when you change the adf-config in Jdev and redeploy.
(This lets you fine tune the timeouts for specific environments. ex: bigger timeouts for dev envs hosted with smaller resources/unstable un-optimized code, rather than guess a timeout that works for all environments )
Now comes the conflicting parts :
"If you must modify these properties, post deployment, you must edit adf-config.xml manually."
I think,they mean "manually using WLST". This can probabaly be done with both WLST commands and the MBeans.
Now once you make these changes to a deployed application, the changes you made are stored in MDS. This means that this "tuning" will survive a re-deployment.
So if we :
set the timeout to 1 minute initially at design time,
then change that to 5 minutes through WLST,
and then edit adf-config again in Jdev to a 10 minute value and redeploy,
the MDS still has the 5 minute value, and it will overwrite the 10 minute value we set later at design time and redeployed.
MDS documents are always applied on top of the deployed stuff.
The doc you refered to : http://docs.oracle.com/cd/E17904_01/webcenter.1111/e12405/wcadm_app_config_files.htm#CHDGEDGJ
does make a good explanation of how the changes persisted in MDS affects the final configuration.
Hop that helps !