Hitachi

uCosminexus Application Server Operation, Monitoring, and Linkage Guide


18.6 Starting and stopping the mutual node switching system (In Windows)

This section describes how to start and stop the system when you use the mutual node switching system.

The mutual node switching system is one of the configurations in which the executing node and standby node of Application Server are arranged in the 1-to-1 ratio. Each Application Server operates as an executing node, and each Application Server is set as the standby node of the other Application Server. For details on the executing node and the standby node, see 15.2 Operations that can be implemented by linking with cluster software.

This section describes the configuration in which Application Servers are deployed as Application Server 1 and Application Server 2. The executing node of the J2EE server A and the standby node of J2EE server B are deployed in Application Server 1, and the standby node of J2EE server A and executing node of J2EE server B are deployed in Application Server 2. The following figure shows a configuration example In this example, the executing node and the standby node of J2EE server A are set up in the resource group A, and the executing node and the standby node of J2EE server B are set up in the resource group B.

Figure 18‒9: Configuration example of mutual standby system

[Figure]

Important note

If node switching occurs due to a failure in the Management Server or Administration Agent, the process of each logical server might remain in the failed host. If process remains in the host, the logical server cannot be started when node failback occurs, therefore, all the processes must be stopped before the node failback occurs. Moreover, you implement the operations for starting the business correctly in advance.

Organization of this section