Hitachi

uCosminexus Application Server Operation, Monitoring, and Linkage Guide


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

This subsection describes an example of system configuration and the procedure for setting the system.

Organization of this subsection

(1) Example of 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 the examples of building the system using this example of system configuration.

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

[Figure]

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 build a cluster, and then define Application Server as the active node and spare node within the cluster. Also, specify the distinguished name of the server (server optional name) for the commands used in the HA monitor and the messages to be output. Specify the same name (CAP in the example) for the active node and spare node.

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 case of the 1-to-1 node switching system, the alias IP address becomes the address that the HA monitor allocates dynamically.

(2) Procedure for system setup

When integrating with the HA monitor, you must set the management portal and the files of the HA monitor. The following figure shows the procedure for setting the 1-to-1 node switching system of Application Server:

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

[Figure]

Steps 1. to 9. of the figure are as follows:

  1. When using a global transaction, create a partition in the shared disk to build a file system.

    To use a global transaction, create the storage location of the transaction information.

  2. When using a global transaction, allocate the shared disk to the system.

    When allocating the shared disk to the system, specify the same mount destination directory in the active node and spare node.

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

    Specify the settings for using the HA monitor in 'Configuration definition of management domain' and 'Environment setup of a logical server' of the management portal. For details, see 17.6.2 Setting the environment of the cluster server.

  4. Edit the configuration files.

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

  5. Set the environment of the HA monitor.

    Define the environment of the HA monitor with the sysdef file of the HA monitor. For details, see 17.6.4 Setting the environment of the HA monitor.

  6. Create the shell script file.

    Create the shell script file for monitoring the Administration Agent and for starting and stopping the Administration Agent and logical servers. For details, see 17.6.5 Creating a shell script file.

  7. Set the server-compliant environment.

    Using the servers file of the HA monitor, define the environment of the active node server and the spare node server to be operated on the nodes. For details, see 17.6.6 Setting the server-compliant environment.

  8. Set the status of LAN.

    Using the LAN status setup file of the HA monitor, specify the IP address of the LAN adapter, and define switching of LAN in the HA monitor. For details, see 17.6.7 Setting the LAN status.

  9. Using the management portal and commands of the HA monitor, specify the settings for Application Server.

    Using the management portal and commands of the HA monitor, deploy Application Server in a cluster configuration, and set the J2EE applications and resource adapters. For details, see 17.6.8 Setting Application Server.

Important note

The precautions to be taken during system setup when integrating with the HA monitor are as follows:

  • Setting the client for connecting to Application Server integrated with the HA monitor

    In the client used to connect to Application Server integrated with the HA monitor, specify Application Server with the alias IP address when invoking Application Server integrated with the HA monitor during EJB lookup.