6.7 Changing settings related to the database session failover functionality
This section describes the changes in settings related to the database session failover functionality. With the database session failover functionality, store preference information such as application information and global session information in database tables. When changing the settings of a once started Web application to check that there is no error in settings by using negotiation processing executed when starting a Web application, you must initialize the preference information of a Web application stored in a database. For details on negotiation processing, see 6.4.1 Processing when starting an application.
The following figure shows the flow of changing settings related to the database session failover functionality.
|
|
![[Figure]](GRAPHICS/ZU061700.GIF)
Points to be considered when changing settings related to the database session failover functionality are:
-
Notes related to scope of stopping when changing settings
If you want to change the following settings, stop all other replicated J2EE servers or applications.
-
Setting integrity mode
-
Setting the amount of global session information in the database
-
-
Notes related to changing the maximum size of HTTP session attribute information
If you change the maximum size of HTTP session attribute information to a smaller value, when you inherit the global session information created before the change, the maximum size after the change might be exceed. If the maximum size exceeds, the KDJE34320-E message is output while serializing attribute information and global session information is not stored in the database. Therefore, if you change the maximum size of HTTP session attribute information to a smaller value, destroy the HTTP session. For details on destroying an HTTP session, see 6.7.3 Deleting global session information (destroying HTTP sessions).
This section describes the changes in settings of a J2EE server and an application, and initialization of a database.
- Reference note
-
For starting and stopping an application, use server management commands or the management portal. For details on starting an application, see cjstartapp (start J2EE application) in the uCosminexus Application Server Command Reference Guide. For details on stopping an application, see cjstopapp (stop J2EE application) in the uCosminexus Application Server Command Reference Guide. For details on operating the management portal, see 12.3 Managing a J2EE application in the uCosminexus Application Server Management Portal User Guide.