In Service Platform, you can configure all standby nodes on a single machine by setting the HCSC server configuring the load-balancing cluster to a cold standby configuration equivalent to the High availability cluster.This configuration is called as N-to-1 cluster configuration.

The following figure shows the configuration (N-to-1cluster configuration) when HCSC servers are clustered:

Figure 1-13 FigureConfiguration of the HCSC server (in the case of N-to-1cluster configuration)

The follow table describes whether or not the execution requests of service components are received with the load balancer used in the N-to-1 cluster configuration.

Table 1-3 TableReceipt of the execution requests of service components with the load balancer used in the N-to-1 cluster configuration

Standard reception	Received/Not received
Standard synchronous reception (Web services)	Y
Standard synchronous reception (SessionBean)	Y
Standard asynchronous reception (MDB(WS-R))	N
Standard asynchronous reception (MDB (DB queue))	N

Legend:

Y: Receives the execution request.

The used load balancer is the same as the load balancer used when you set the HCSC server to load-balancing cluster configuration. For details, see "2.5 Environment setup to change HCSC server to load balancing cluster configuration".

N: Does not receive the execution request.

However, you can receive asynchronous execution requests made directly to individual HCSC servers. In this case, you set the destination of the service requester sending execution requests of service components to the set of HCSC servers equivalent to the HA cluster without fail.

If you set the destination for load-balancing cluster configuration, the execution request of service components might get processed incorrectly. Therefore, set such that the execution request for service components to standard asynchronous reception (MDB (WS-R) / MDB (DB queue)) with the load balancer is not received.