This section describes changing settings related to the EADs session failover functionality. With the EADs session failover functionality, preference information such as application information and global session information is stored in the EADs server cache. Because negotiation processing checks that there are no errors in settings when starting a Web application, you must initialize the preference information of the Web application, which is stored in the EADs server cache, when changing the settings of a Web application that was once started. For details on negotiation processing, see 7.3.1 Processing when starting an application.

The following figure shows the flow for changing settings related to the EADs session failover functionality:

Figure 7-14 Flow of changing settings related to the EADs session failover functionality

Reference note

Use the server management commands or management portal for starting and stopping an application. For details on starting an application, see cjstartapp (starting a J2EE application) "> in the uCosminexus Application Server Command Reference Guide. For details on stopping an application, see cjstopapp (stopping a J2EE application) in the uCosminexus Application Server Command Reference Guide. For details on the operating management portal, see 12.3 Managing a J2EE application in the uCosminexus Application Server Management Portal User Guide.

Organization of this section

7.7.1 Changing J2EE server and application settings

7.7.2 Initializing application information

7.7.3 Destroying an HTTP session