Changing the automatic logoff setting

The default automatic logoff value is 30 minutes. You might want to change the default setting depending on your security needs.

The automatic logoff is configured to automatically timeout after a period of 30 minutes of inactivity. To extend the default period to more than 30 minutes, you change the web.xml configuration file.

Procedure

1. Back up the web.xml file. On Windows, the web.xml file is normally located in the MAXIMO_HOME\applications\maximo\maximouiweb\webmodule\WEB-INF directory. On UNIX systems, the default location is the MAXIMO_HOME/maximo/applications/maximo/maximouiweb/webmodule/WEB-INF directory. MAXIMO_HOME is the directory where the base services are installed. On Windows, the default path is c:\IBM\SMP. On UNIX systems, the default path is /opt/IBM/SMP.
2. Open the web.xml file in a text editor.
3. In the <session-config> section, search for the session timeout tag, named <session-timeout>. In the following code example, the automatic timeout is set to timeout after 90 minutes.

   <session-config>
   <!-- The session-timeout element defines the default session timeout
   interval for all sessions created in this web application. The
   specified timeout must be expressed in a whole number of minutes. -->
   <session-timeout>90</session-timeout>
   </session-config>

4. Change the existing value in the <session-timeout> tag to the value you want to specify as the new logoff value.
5. Save and close the web.xml file.
6. Rebuild the Maximo® EAR file on the administrative workstation to invoke the changes. To rebuild the Maximo EAR, run one of the following scripts, depending on your platform:
   1. On Windows systems, run the buildmaximoear script, located in the C:\ibm\SMP\Maximo\deployment directory on the administrative workstation.
   2. On UNIX systems, run the buildmaximoear.sh script, located in the /opt/IBM/SMP/maximo/deployment directory on the administrative workstation.
7. Deploy the Maximo EAR to WebSphere® Application Server. You can deploy the Maximo EAR using WebSphere Application Server or you can use the command line. To view command line instructions about how to deploy the Maximo EAR file, see Manually deploying the EAR file. To deploy the Maximo EAR on WebSphere Application Server, complete a process similar to the following example on WebSphere Application Server v6.1.0.37.
   1. Log on to WebSphere Application Server.
   2. Click Applications, then Enterprise Applications.
   3. Uninstall the previous Maximo EAR before you begin redeploying the new one because updating the existing Maximo EAR can cause caching issues.
   4. Click Install.
   5. If WebSphere Application Server is on the administrative workstation, navigate to the location of the Maximo EAR by clicking Local File System. If you do not have direct access to the administrative workstation on which the Maximo EAR is located, click Remote File System and navigate to the Maximo EAR location, for example on Windows C:\ibm\SMP\maximo\deployment\default, and click the file.
   6. Click OK, then click Next.
   7. On the Select installation options screen, make sure that the Maximo installation is selected. If there are multiple Maximo installations on your WebSphere Application Server environment, click the specific application name for the installation. Then click Next.
   8. On the Map modules to servers screen, select the web server and application server in the Clusters and Servers box, select all of the modules, then click Apply.
   9. Click Next.
   10. On the Map virtual hosts for Web modules screen, click the options for your installation and change the Virtual host options to the host you have set up for the Maximo application. Click Next.
   11. On the Summary page, review the summary and click Finish.
   12. After the Maximo EAR file has installed, click Save to save your changes. The Maximo EAR is now deployed to the server.
   13. Go to the WAS console and from the navigation tree, click Applications > Enterprise Applications. Then click MAXIMO > Class loading and update detection. For WAR class Loader Policy, the Class loader for each WAR file in application option is selected by default. Click the Single class loader for application option. Click Save to save your changes.
   14. Restart Tivoli® Provisioning Manager. If you have problems logging into Tivoli Provisioning Manager after rebuilding the Maximo EAR, see https://www-304.ibm.com/support/docview.wss?uid=swg21321974 for information about how to resolve the issue.

Results

You have configured the automatic timeout to a time length of your choice.