Hitachi

uCosminexus Application Server Operation, Monitoring, and Linkage Guide


19.4.1 Procedure for setting the N-to-1 recovery system

This subsection describes an example of the system configuration and the procedure for setting up systems, when the systems are integrated with Windows Server Failover Cluster.

Organization of this subsection

(1) Example of system configuration

The following figure shows an example of system configuration of the N-to-1 recovery system. Note that the subsequent sections describe examples of building the system using this example of system configuration.

Figure 19‒3: Example of system configuration (In the N-to-1 recovery system)

[Figure]

In this example, deploy four executing node servers and one recovery server. In three of the four executing nodes, deploy the same J2EE server called MyServer in which you deploy the same J2EE application and resource adapter. In the remaining one executing node, deploy a J2EE server called MyServer2 that is different from the other J2EE server names and has a different J2EE application and resource adapter deployed in it.

In the N-to-1 recovery configuration, build multiple virtual hosts within one cluster. A combination of the executing node and recovery node configures the virtual host with the J2EE server deployed in a cluster configuration. In the N-to-1 recovery configuration, the J2EE server operates within the virtual host rather than the cluster. Therefore, set the IP address and host name of the virtual host.

A virtual host is defined as a resource group and includes the 'physical disk resource', 'IP address resource', 'network resource name', and 'general-purpose script resource'. The following figure shows an example of the resource groups described in this section:

Figure 19‒4: Example of the resource group

[Figure]

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 N-to-1 recovery configuration, the alias IP address becomes the IP address of the virtual host.

In the J2EE server of the standby node, import and deploy a resource adapter with the same settings as all resource adapters that you are using in the J2EE servers of the executing node.

(2) Procedure for system setup

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

Figure 19‒5: Procedure for setting the N-to-1 recovery system (In Windows)

[Figure]

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

  1. Create N number of partitions in the shared disk to build a file system.

    You create a storage location for the cluster management file of Windows Server Failover Cluster. Also, to use a global transaction in the N-to-1 recovery system, create the storage location for the transaction information. Note that you may store the cluster management file and 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 executing node and standby node.

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

    You 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 19.4.2 Setting the environment of the cluster server.

  4. Edit the configuration files.

    You set up various definition files of Administration Agent, Management Server, and Cosminexus HTTP Server. For details, see 19.4.3 Editing the configuration files.

  5. Setting a cluster.

    You set up an environment for the cluster software. For details, see 19.4.4 Setting a cluster

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

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