SOA 10.1.3.1 Hints - Episode 3
In today's note we will discover the steps needed to increase the inactivity timeout of the SingleSignOn - enabled consoles shipped with SOA Suite 10.1.3.1.
Some of you might have already noticed, not using the session for some minutes results in a rerouting to the login page.. and if it happens the first time some ohh, arghhh or other words may follow :D
The SOA related web consoles are ..
- BPEL Console (http://host:port/BPELConsole)
- ESB Console (http://host:port/esb/esb/EsbConsole.html)
- Rule Author (http://host:port/ruleauthor)
- and the famous Human Worklist(http://host:port/integration/worklistapp)
As all are deployed in the same way, and are JSSO enabled - here are the steps you need to follow, to increase the timeouts of them.
- 1) Stop your SOA Suite (opmnctl stopall)
- 2) Depending on your installation your OC4J container holding the apps is either located in $ORACLE_HOME/j2ee/home (basic install) or $ORACLE_HOME/j2ee/oc4j_soa (advanced install), which I refer to $OC4J_HOME from now
- 3) Go to $OC4J_HOME/config and backup jazn.xml
- 4) Add a new property called custom.sso.session.timeout inside the <jazn> section, the value is in seconds and should be a multiply of it
- 5) Step by step now - you are going to reconfigure the consoles
- BPEL Console
- Go to $OC4J_HOME/applications/orabpel/console/WEB-INF and backup web.xml
- Add the following fragment
<session-config>
<session-timeout>-1</session-timeout>
</session-config>
inside the <web-app> tags - Go to $OC4J_HOME/applications-deployments/orabpel/console and delete orion-web.xml
- ESB Console
- Go to $OC4J_HOME/applications/esb-rt/provider-war/WEB-INF and backup web.xml
- Add the following fragment
<session-config>
<session-timeout>-1</session-timeout>
</session-config>
inside the <web-app> tags - Go to $OC4J_HOME/application-deployments/esb-rt/provider-war and delete orion-web.xml
- Rule Author
- Go to $OC4J_HOME/applications/ruleauthor/ruleauthor/WEB-INF and backup web.xml
- Add the following fragment
<session-config>
<session-timeout>-1</session-timeout>
</session-config>
inside the <web-app> tags - Go to $OC4J_HOME/application-deployments/ruleauthor/ ruleauthor/ and delete orion-web.xml
- Human Worklist
- Go to $OC4J_HOME/applications/hw_services/worklistapp/ WEB-INF and backup web.xml
- Add the following fragment
<session-config>
<session-timeout>-1</session-timeout>
</session-config>
inside the <web-app> tags - Go to $OC4J_HOME/application-deployments/hw_services/ worklistapp and delete orion-web.xml
- BPEL Console
- 6) Start your SOA Suite, by opmnctl startall
Voila, the inactivity timeout in YOUR control
3 Comments:
Hi Clemens,
Is the JSSO enabled in GA release or in Beta as well. We are beta customer and having issues with JSSO. Any blog on JSSO will help us a lot...:-)
Thanks,
Rajesh
5:43 AM
Clemens,
Could you elaborate the below statement, i am confused with this.
"Add a new property called custom.sso.session.timeout inside the jazn section, the value is in seconds and should be a multiply of it"
Best Regards/Chandra
2:24 AM
just add this to your jazn.xml as property - don't forget that it is in seconds! sorry for the confusion on that.
2:35 AM
Post a Comment
<< Home