18.4.1 Procedure for setting up the mutual node switching systems

(1) System configuration examples

The following figure shows an example configuration of a mutual node switching system. Note that the subsequent points describe the system configuration based on this configuration example.

Figure 18‒5: Configuration example of mutual node switching system (in Windows)

In this example, two types of application servers (assumed to be application server 1 and application server 2) are used. The executing node (active node 1) and standby node (spare node 2) of Application Server 1 and the executing node (active node 2) and standby node (spare node 1) of Application Server 2 are deployed in 1-to-1 ratio. Each Application Server deploys a Management Server having a separate management domain, and the Management Server is started on both the machines.

In the mutual node switching system, two virtual hosts are defined in one management domain and are configured as the host of the active node Application Server and the host of the spare node Application Server respectively. In this example, the combination is as follows:

• Active node 1 (virtual host 1) of Node 1 and spare node 1 (virtual host 1) of Node 2

• Active node 2 (virtual host 2) of Node 2 and spare node 2 (virtual host 2) of Node 1

The virtual host controls the starting and stopping of Application Server using one Administration Agent, but the IP addresses allocated for operations are different, so the virtual hosts are defined as apparently different hosts.

Note that in order to deploy Application Server in a cluster configuration, set the alias IP address and specify settings in such a way so that the running node inherits the alias IP address, and the client does not realize the nodes in the cluster. For the mutual node switching system, the alias IP address is the address (cluster IP address) that is dynamically allocated by the cluster software. For the IP address to be used in the operations of Application Server, you use the cluster IP address, and for sending the requests from the Management Server to the Administration Agent, you use the IP address (stationary IP address) that does not move to other nodes due to node switching.

To Page Top

(2) Procedure for system setup

When integrating the system with Windows Server Failover Cluster, you must set up Management Server and Cluster Administrator. The following figure shows the procedure for setting up the mutual node switching system:

Figure 18‒6: Procedure for setting up the mutual node switching system (in Windows)

The following points describe the step 1 through 6 of the above figure:

1. Create a partition in the shared disk to build the file system.

   You create a location for storing the cluster management file of Windows Server Failover Cluster. Also, when using the global transaction, create the location for storing the transaction information. The cluster management file and the transaction information can be stored in the same partition.

2. Allocate a shared disk to the system.

   When allocating a shared disk to the system, allocate the same drive characters to the active node 1 and spare node 1, and to the active node 2 and spare node 2.

3. Set up the cluster server environment in the Management Server.

   In the Easy Setup definition file of the Smart Composer functionality for Management Server, specify the settings for using Windows Server Failover Cluster. For details, see 18.4.2 Environment settings of the cluster server.

4. Edit the setup file.

   Specify the settings for various definition files of Administration Agent, Management Server, and Cosminexus HTTP Server that cannot be set up in the Easy Setup definition file. For details, see 18.4.3 Editing the setup file.

5. Setting a cluster.

   Create a script file for monitoring the environment settings of the cluster software, Management Sever, and Administration Agent. For details, see 18.4.4 Setting a cluster.

6. Set up Application Server in Management Server and Cluster Administrator.

   Use Management Server and Cluster Administrator to deploy Application Server in the cluster configuration, and to set up J2EE applications and resource adapters. For details, see 18.4.5 Setting Application Server.

To Page Top