17.4.1 Procedure for setting the 1-to-1 node switching system of Application Server

(1) Example system configuration

The following figure shows an example of configuration for the 1-to-1 node switching system of Application Server. Note that the subsequent points describe examples of building the system using this example of system configuration.

Figure 17‒5: Configuration example of the 1-to-1 node switching system of Application Server (In Windows)

In this example, the executing node (active node) of Application Server and the standby node (spare node) of Application Server are deployed in 1-to-1 ratio. Also, Management Server is deployed in a machine different from Application Server.

In the 1-to-1 node switching system of Application Server, first of all you build a cluster, and then you define Application Server as the active node (Node1 in the example) and the spare node (Node2 in the example) within the cluster (APS in the example). Also, the active node and the spare node are defined as one resource group (ClusterA in the example) containing the 'physical disk resource', 'IP address resource', 'network name resource', and 'general-purpose script resource'.

To deploy Application Server in a cluster configuration, set the alias IP address, and specify settings so that the running node inherits the alias IP address and the client does not consider the nodes in the cluster. In the 1-to-1 node switching system, the alias IP address becomes the address that Windows Server Failover Cluster allocates dynamically (cluster IP address).

To Page Top

(2) Procedure for system setup

When integrating with Windows Server Failover Cluster, you must set the management portal and cluster administrator. The following figure shows the procedure for setting the 1-to-1 node switching system of Application Server:

Figure 17‒6:  Procedure for setting the 1-to-1 node switching system of Application Server (In Windows)

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

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

   Create the storage location for the cluster management file of Windows Server Failover Cluster. Also, when you are using a global transaction, create the storage location for the transaction information. Note that you might store the cluster management file and the transaction information in the same partition.

2. Allocate the shared disk to the system.

   When allocating the shared disk to the system, allocate the same drive character to the active node and spare node.

3. Set the environment of the cluster server with the management portal.

   Specify the settings for using Windows Server Failover Cluster in 'Configuration definition of management domain' and 'Environment setup of a logical server' of the management portal. For details, see 17.4.2 Setting the environment of the cluster server.

4. Edit the configuration files.

   Set various definition files of Administration Agent, Management Server, and Cosminexus HTTP Server. For details, see 17.4.3 Editing the configuration files.

5. Setting a cluster

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

6. Set Application Server with the management portal and cluster administrator.

   Use the management portal and the cluster administrator to deploy Application Server in the cluster configuration, and then set the J2EE applications and resource adapters. For details, see 17.4.5 Setting Application Server.

To Page Top