ODSEE - How to View and Change the "DSCC Session Automatic Timeout Delay" when using GlassFish Server
(Doc ID 1451398.1)
Last updated on OCTOBER 07, 2019
Applies to:Oracle Directory Server Enterprise Edition - Version 6.3 to 188.8.131.52.0 [Release 6.0 to 11gR1]
Information in this document applies to any platform.
How to View and Change the "DSCC Session Automatic Timeout Delay" when using Glassfish Server
Provide instructions on how to accomplish the goal
The session timeout can be set globally for all the applications deployed on the GlassFish server by editing the default-web.xml file. The "default-web.xml" file will be under the configuration directory of the domain (the default location is /domains/domain1/config)
In the "default-web.xml" file look for the following entry: 30 For example
Once this value is modified a restart of the GlassFish server is required to pickup the modified value.
NOTE*** Be aware that this change in the "default-web.xml" file will affect ALL the applications deployed on the GlassFish Server UNLESS the session timeout is set in the deployment descriptors files (web.xml and sun-web.xml ) of the application. Setting the session timeout set in the web.xml/sun-web.xml at the application level will override the session timeout value set in the [global] "default-web.xml" file.
To set the session timeout at the application level (in this case DSCC) set the session timeout in either web.xml or sun-web.xml files that are bundled with the dscc.war file. Then repackage the application and redeploy it. Example:
unzip -d /<PATH_TO>/glassfish/webapps/dscc /<PATH_TO>/dscc.war
In this scenario the only application deployed on the GlassFish Server is the DSCC.
Please see reference the following documentation for further information on session properties:
By default, there are no session-config or session-timeout values set in any of these files. The DSCC is depending on the default session timeout on GlassFish. The default is 30 minutes. The default session-timeout value in the "default-web.xml" can be changed to be the session timeout for DSCC. However, the change in the "default-web.xml" file will affect all the applications deployed on the GlassFish Server unless the session timeout is set in the deployment descriptors (web.xml and sun-web.xml files) of each application as explained above. In this scenario the only application deployed on the GlassFish Server is the DSCC.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document