This topic describes how to change the session timeout from the
default value for the administrative console.
Before you begin
Ensure that you have the proper permissions to change the ${WAS_HOME}/systemApps/adminconsole.ear/deployment.xml file.
About this task
Determine whether the default session timeout value of 30 minutes
is acceptable. Some reasons that you might change the default value are:
- Users in secure environments might need shorter session timeout periods
to ensure security, encase they leave their machine and forget to log off
the console.
- Users might need longer session timeout periods if they respond slower
than typical users for accessibility reasons.
- Users in secure environments might not want the administrative console
timeout value to conflict with Lightweight Third-Party Authentication (LTPA)
cookie timeouts
Do the following actions to change the timeout value:
Procedure
Edit the ${WAS_HOME}/systemApps/adminconsole.ear/deployment.xml file
in a text editor.
Remove the symbolic link at ${WAS_HOME}/systemApps/adminconsole.ear/deployment.xml.
Copy the real file from ${INSTALL_ROOT}/systemApps/adminconsole.ear/deployment.xml to
the directory of the symbolic link that you deleted.
Edit the ${WAS_HOME}/systemApps/adminconsole.ear/deployment.xml file
in a text editor.
- Locate the xml statement <tuningParams xmi:id="TuningParams_1088453565469"
maxInMemorySessionCount="1000" allowOverflow="true" writeFrequency="TIME_BASED_WRITE"
writeInterval="10" writeContents="ONLY_UPDATED_ATTRIBUTES" invalidationTimeout="30">
- Change the invalidationTimeout value to the desired session timeout.
The default is 30.
- Save the ${WAS_HOME}/systemApps/adminconsole.ear/deployment.xml file.
Restart the
deployment manager.
Results
Once
you restart the deployment manager, the change takes effect.
What to do next
Manage WebSphere Application Server through the
administrative console.
Once you remove the symbolic
link, make updates to the ${WAS_HOME}/systemApps/adminconsole.ear/deployment.xml only
as the product reads the contents of this path and file, not the ${INSTALL_ROOT}/systemApps/adminconsole.ear/deployment.xml file.
The product ships any service updates for the deployment.xml file
in the ${INSTALL_ROOT}/systemApps/adminconsole.ear/deployment.xml location.
Merge any service updates to the ${INSTALL_ROOT}/systemApps/adminconsole.ear/deployment.xml file
into the ${WAS_HOME}/systemApps/adminconsole.ear/deployment.xml file
so that the product can pick up the service updates.