In Service Platform, you can build a system (1-to-1 node switching system) that operates the executing node and the standby node on a one-to-one basis by clustering multiple HCSC servers that are set up in the execution environment in a cold standby configuration that combines a set of 2 HCSC servers.

This configuration is called as Cluster configuration.

The following figure shows the configuration (High availability cluster configuration) when HCSC servers are clustered:

Figure 1-12 FigureConfiguration of HCSC servers (in case of High availability cluster configuration)

You require cluster software to configure the High availability cluster. Use the following cluster software in Service Platform:

• In Windows: Windows Server Failover Cluster
• In UNIX: HA monitor

In the clustered 1-to-1 node switching system, if any failure occurs in the executing node, the cluster software detects this, and continues the business by automatically switching to a standby node. The configuration of the system becomes more redundant, and you can continue and operate service components even if a failure occurs in one node.

Furthermore, in the cluster software, you perform the following settings so that the standby node HCSC server starts automatically when a failure is detected:

• Starting the standby node HCSC server
• Starting the standard reception of the standby node HCSC server

Note

• The same HCSC components must be deployed in the 2 HCSC servers that configure the High availability cluster. You must also set the same OS and user in the executing node and the standby node.
• If a failure occurs at the time of building the High availability cluster, and if the file that inputs and outputs the common folder and the file adapter is stored in the shared disk, you can re-execute the business process. However, because you cannot use the common folder for FTP reception and HTTP reception, you cannot re-execute the business process.