Updating defaultTimeout in adf-config.xml through WLST

Question

Hello,
I hope i have this in the right area. I'm cross posting because I think I put it in the wrong place originally. If I get an answer, I'll cross link the two.
I'm trying to change the default, min and maximum timeouts for portlets that come from our WSRP portlet producing application. The documentation I found on the time outs says to edit adf-config.xml 1 and when editing the adf-config.xml do that via WLST ^2^.
1) portlet time out: [http://docs.oracle.com/cd/E17904_01/core.1111/e10108/webcenter.htm#BABIGHDC|http://docs.oracle.com/cd/E17904_01/core.1111/e10108/webcenter.htm#BABIGHDC]
<adf-portlet-config>
<defaultTimeout>5</defaultTimeout>
<minimumTimeout>2</minimumTimeout>
<maximumTimeout>100</maximumTimeout>
<adf-portlet-config>
2) editing adf-config.xml: [http://docs.oracle.com/cd/E17904_01/webcenter.1111/e12405/wcadm_app_config_files.htm#WCADM5019|http://docs.oracle.com/cd/E17904_01/webcenter.1111/e12405/wcadm_app_config_files.htm#WCADM5019]
I can not find the MBean in the bean browser that seems to hold this setting.
There is a bit of a conflicting message in the docs though. "If you must modify these properties, post deployment, you must edit adf-config.xml manually." But the doc that describes editing adf-config.xml says that using WLST are
So... Questions:
1) Are these three elements (defaultTimeout, minimumTimeout, and maximumTimeout) some exception to being set from WLST?
2) If not, what is the MBean I should find this setting in?
Thank you very much,
Marc
Edited by: MarcDavenport on Jun 26, 2012 12:37 PM

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 !