2.6.2 Execution environment setup in HA cluster configuration

(1) Preparing setup

Perform the following operations before setup. Perform the following operations in executing node and standby node respectively.

Setting software required in the execution environment

Perform J2EE server setup. For details on setting contents and how to set, see "3.1.2 Setting up the software required for the execution environment".

During setup, Reliable Messaging system name must be the same as the name set in executing node and standby node.

To use a global transaction, the host must be fixed in the cluster IP address of J2EE server. For the method to fix the host, see the following location:

Setting 1:1 node switching system for the application server

• In Windows

  "17.4.2 Setting the environment of the cluster server" in "Application Server Operation, Monitoring, and Linkage Guide"

• In UNIX

  "17.6.2 Setting the environment of the cluster server" in "Application Server Operation, Monitoring, and Linkage Guide"

To use a local transaction, the host need not be fixed. Set the local host or physical IP address.

Sending control in the service requester

Disconnect the network for the service requester and change to the status in which service product execution request is not received in executing node and standby node.

To Page Top

(2) Execution environment (standby node) setup

The following table describes the procedures of execution environment (standby node) setup:

1. Start the process in the following order:

   Start order	Process to be started	Start method
   1	Administration Agent	See "Application Server System Setup and Operation Guide".
   2	Management Server
   3	PRF
   4	J2EE server
   5	HTTP Server	See "5.3.5 Starting HTTP Server".

2. Set up HCSC server.

   For details on how to set up HCSC server, see "3.1.3 Setting up an HCSC server".

3. Start HCSC server.

   For details on how to start the HCSC server, see "5.3.4 Starting HCSC server".

4. Deploy service adapter and business process.

   For details on how to deploy the service adapter and business process, see "3.1.8 Deploying a service adapter" and "3.1.13 Deploying a business process".

5. Start service adapter and business process.

   For details on how to start the service adapter and business process, see "5.3.6 Starting Service Adapters" and "5.3.7 Starting Business Processes".

6. Stop HCSC server.

   Stop HCSC server while the service adapter and business process are running.

   For details on how to stop the HCSC server, see "5.3.38 Terminating the HCSC Server".

7. Stop Management Server and Administration Agent.

   For details on how to stop Management Server and Administration Agent (operation management functionality), see "3.1.3 Stopping the system (when using GUI) " in "Application Server System Setup and Operation Guide".

To Page Top

(3) Execution environment (executing node) setup

The following table describes procedures for execution environment (executing node) setup:

1. Start the process in the following order:

   Start order	Process to be started	Start method
   1	Administration Agent	See "Application Server System Setup and Operation Guide".
   2	Management Server
   3	PRF
   4	J2EE server
   5	HTTP Server	See "5.3.5 Starting HTTP Server".

2. Set up HCSC server.

   For details on how to set up HCSC server, see "3.1.3 Setting up an HCSC server".

   While setting up HCSC server in executing node, the file name specified in -cluster option of cscsvsetup command must contain the same value as in standby node.

   For details on cscsvsetup command, see "cscsvsetup (Setting up an HCSC server)" in "Service Platform Reference Guide".

3. Start HCSC server.

   For details on how to start the HCSC server, see "5.3.4 Starting HCSC server".

4. Deploy service adapter and business process.

   Deploy the same service adapter and business process as the ones deployed in standby node. Ensure that sufficient service adapters and business processes are deployed between executing node and standby node.

   For details on how to deploy the service adapter and business process, see "3.1.8 Deploying a service adapter" and "3.1.13 Deploying a business process".

5. Start service adapter and business process.

   Start the same service adapter and business process as those started in standby node. Ensure that there is no difference in service adapter and business process status between executing node and standby node.

   For details on how to start the service adapter and business process, see "5.3.6 Starting Service Adapters" and "5.3.7 Starting Business Processes".

6. Start standard reception.

   For details on how to start the standard reception, see "5.3.9 Starting standard receptions".

To Page Top

(4) Setting cluster software

Set to switch to standby node if executing node fails in cluster software.

Set to execute the script for the following operations while switching to standby node. Set to execute in the following order.

OS and HCSC-Manager user must match with the executing node.

1. Start standby node process

   Set to start the process in the following order:

   • Administration Agent

   • Management Server

   • PRF

   • HTTP Server

2. Start HCSC server in standby node^#

3. Start standard reception of HCSC server in standby node

Note #

If you start HCSC server in standby node in the cluster software by cscutil command, set the following options:

-host option

Combine the host name (or IP address) starting Management Server with the port number by a colon (:) and specify. Specify "localhost" in host name. An example of specification if the port number is "28099" is described here.

-host localhost:28099

-mnguser option

Specify user ID of the Management user of Management Server.

-mngpass option

Specify password of the Management user of Management Server.

To Page Top