This subsection describes the points to be considered when you disable integrity mode.

Switching integrity mode

If you switch integrity mode from disabled to enabled, initialize the session information storage table and the application information table in the database as described in the following procedure:

1. Stop all replicated J2EE servers.
2. Destroy the HTTP session.
   For details on the procedures for destroying an HTTP session, see 6.10.3 Deleting global session information (destroying HTTP session).
   
3. Initialize the preference information stored in the database.
   For details on the procedures for initializing the preference information stored in a database, see 6.10.2 Initializing a database table.
   

Monitoring validity of global session information when stopping a J2EE server

If you stop a Web application or J2EE server, or if a process goes down due to a failure on a J2EE server, the validity of global session information is not monitored. Monitoring of validity starts when you start a Web application or when global session information is inherited on a J2EE server by receiving a request.

If integrity mode is enabled and when a J2EE server stops, another J2EE server monitors the validity. For details on validity monitoring processing, see 6.4.3 Processing when validity of global session information expires.

Operations performed when the amount of global session information reaches the upper limit

Reduce an HTTP session if the amount of global session information in a database reaches the upper limit when creating global session information. For details on reducing an HTTP session, see 5.7.3 Reducing an HTTP session.