Handling temporary configuration files resulting from session timeout
OverviewIf the console is not used for 15 minutes or more, the session times out. The same thing happens if you close the browser window without saving the configuration file. Changes to the file are saved to a temporary file when the session times out, after 15 minutes.
When a session times out, the configuration file in use is saved under the userid/timeout directory under the ServletContext's temp area. This is the value of the javax.servlet.context.tempdir attribute of the ServletContext. By default, it is: install_root/temp/hostname/Administration/admin/admin.war
You can change the temp area by specifying it as a value for the tempDir init-param of the action servlet in the deployment descriptor (web.xml) of the administrative application.
The next time you log on to the console, you are prompted to load the saved configuration file. If you decide to load the saved file:
- If a file with the same name exists in the install_root/config directory, that file is moved to the userid/backup directory in the temp area.
- The saved file is moved to the install_root/config directory.
- The file is then loaded.
If you decide not to load the saved file, it is deleted from the userid/timeout directory in the temp area.
The configuration file is also saved automatically when the same user ID logs into the non-secured console again, effectively starting a different session. This process is equivalent to forcing the existing user ID out of session, similar to a session timing out.
Working with server configuration files