Hitachi

uCosminexus Application Server System Design Guide


3.11.1 Configuration in which executing node and standby node of Application Server are in 1-to-1 ratio (when transaction service is not used)

This subsection describes the configuration where the executing node and standby node of Application Server are in a 1-to-1 ratio, and the transaction service is not used.

Organization of this subsection

(1) Features of the system configuration

This is a system configuration that does not use transaction service when using local transaction.

This subsection also describes the configuration in which Application Server performs the node switching. For details about the configuration in which the node switching is performed by Management Server, see 3.11.3 Configuration in which executing node and standby node of Management Server are in 1-to-1 ratio.

The following figure shows an example of configuration where transaction service is not used:

Figure 3‒49: Example of system configuration where executing node and standby node are in 1-to-1 ratio and cluster software is used (when transaction service is not used)

[Figure]

Note: For other legend items, see 3.2 Description of the system configuration.

Features
  • The executing node and standby node are configured in a 1-to-1 ratio.

  • A shared disk device is not required when you use HA monitor. However, a shared disk device is required when you use Windows Server Failover Cluster. The above figure shows the configuration with HA monitor.

  • When the database has a cluster configuration and if Application Server identifies only the virtual address (Logical address), you can still establish the connection.

  • For details about allocating Management Server and Application Server on the same machine, see 3.11.6 Configuration in which the executing node and standby node of the host unit management model are in an N-to-1 ratio.

Flow of requests

The client recognizes one machine for both the Application Server instance in the executing node and instance in the standby node. All the requests are sent to the Application Server in the executing node.

Node switching flow

Node switching is executed when there is a failure in the Application Server machine in executing node. Node switching is executed when the OS or Administration Agent is down. Also, node switching is performed when a command is executed explicitly for node switching, or when there is an event where node switching is to be performed for cluster software.

On executing node switching, Administration Agent of Application Server in the standby node and the processes that were stopped until then are started.

(2) Processes to be invoked on the respective machines

The following subsections describe the software and processes required on the respective machines:

(a) Application Server machine (executing node)

The following are the processes that must be started for using the cluster software:

  • Administration Agent

The required software and the processes to be invoked on the Application Server machine are different for each system configuration depending on the used functions. Allocate the required software and processes depending on the used functions.

(b) Application Server machine (standby node)

You must match the configuration of software installed on the Application Server machine in the standby node with the executing node. However, the process will not start unless node switching takes place.

(c) Management Server machine

You must install Application Server on the Management Server machine.

Invoke the following process:

  • Management Server

(d) Client machine

Install the following software on client machine:

For Web client configuration

Web browser

For EJB client configuration

uCosminexus Client (in Windows), Application Server