You can start the operations of the N-to-1 cluster configuration system after the creation and setup of the environment ends. To start operations:

1. Check the status of components of the executing node and the standby node
   The components of the executing node and standby node that are equivalent to the High availability cluster cpmfogiratopmmust be in the status listed in the following table in all load-balancing clusters of N-to-1 cluster configuration.
   

   Table 5-8 Status of components equivalent to the High availability cluster configuration

   Components	Status
   	Executing node	Standby node
   Administration Agent	Y	-
   Management Server	Y	-
   PRF	Y	-
   Smart Agent	Y	-
   CTM (applicable if CTM is used)#1	Y#1	-
   J2EE server	Y#2	-
   HCSC server	Y#3	-
   HTTP Server	Y	-

   Legend:

   Y: Started.

   --: Stopped

   #1

   The CTM domain manager and CTM daemon must also be active.

   #2

   The status of applications such as Reliable Messaging must match. The system name for Reliable Messaging must be unique in each HCSC server in the load-balancing cluster.

   #3

   The deployed service adapter and business process, and standard reception must have the same status.

   
   
2. Service requester transmission control
   Set the service requester to a status in which it can accept service component execution requests by connecting the network for the service requester that cannot accept service component execution requests because its network was disconnected during setup.
   

The method to end operations of the system of the N-to-1 cluster configuration is the same as the load-balancing cluster configuration. For details on how to end the operations of the load-balancing cluster configuration, see "5.6.1(2) Ending operations".

You can add or delete HCSC servers that configure the N-to-1 cluster without stopping operations. In the case of a load balancer, you can add or delete the HCSC server without stopping operations only when the function for dynamically adding and deleting IP addresses is available.

The method to add and delete HCSC servers that configure the N-to-1 cluster is as follows:

(a) Adding HCSC servers

1. Set up the execution environment for the HCSC server to be added to the N-to-1 environment.
   For details on how to setup the execution environment equivalent to the load-balancing cluster, see "2.5.2(2) Execution environment setup".
   For details on how to setup the execution environment equivalent to the High availability cluster, see "2.6.2(2) Execution environment (standby node) setup" and "2.6.2(3) Execution environment (executing node) setup".
   
2. Start up the HCSC server
   For details on how to start up HCSC servers, see "5.3.4 Starting HCSC server".
   
3. Deploy the service adapter.
   For details on how to deploy service adapters, see "3.1.8 Deploying a service adapter".
   
4. Deploy the business process.
   For details on how to deploy business processes, see "3.1.13 Deploying a business process".
   
5. Start the service adapter.
   For details on how to start service adapters, see "5.3.6 Starting Service Adapters".
   
6. Start the business process.
   For details on how to start business processes, see "5.3.7 Starting Business Processes".
   
7. Start the standard reception.
   For details on how to start the standard reception, see "5.3.9 Starting standard receptions".
   
8. Set up the load balancer.
   Set up the load balancer such that service component execution requests are dynamically sent to the HCSC server you have added.
   If you are using CTM, all HCSC servers must have the same CTM domain manager name and Smart Agent port number.
   For details on how to set up a load balancer, see the documentation for the load balancer you are using.
   

   Note

   If you are using CTM, service component execution requests are assigned to HCSC servers when the standard reception for the added HCSC server starts.

(b) Deleting HCSC servers

1. Set up the load balancer.
   Set up the load balancer such that that no service component execution request is sent to the HCSC server to be deleted. At this time, confirm that all execution requests that are currently being processed are completed. If you are using CTM, the queue for sending service component execution requests to the target J2EE server is locked. For locking of the queue when you use CTM, see "3.7.4 Lock control of the schedule queue" in "Application Server Expansion Guide".
   For details on how to set up a load balancer, see the documentation for the load balancer you are using.
   
2. Stop the standard reception.
   For details on how to stop the standard reception, see "5.3.28 Terminating the Standard Reception".
   
3. Stop the business process.
   For details on how to stop business processes, see "5.3.31 Terminating the Business Process".
   
4. Stop the service adapter.
   For details on how to stop service adapters, see "5.3.30 Terminating the Service Adapter".
   
5. Delete the business process.
   For details on how to delete business processes, see "3.3.2 Deleting a business process".
   
6. Delete the service adapter.
   For details on how to delete service adapters, see "3.3.1 Deleting a service adapter".
   
7. Stop the HCSC server to be deleted.
   For details on how to stop the HCSC server, "5.3.33 Terminating the HCSC Server".
   
8. Delete the HCSC server.
   For details on how to delete HCSC servers, see "3.3.5 Unsetting up an HCSC server".
   

This subsection describes how to add, delete, and change service adapters and business processes to HCSC servers that configure the N-to-1 cluster.

You add, delete, or change service adapters and business processes to HCSC servers that configure the N-to-1 cluster for each set of the High availability cluster configuration in a sequence.

(a) Adding and deleting service adapters

For details on how to add and delete new service adapters without stopping service adapters already deployed to the HCSC server, see "5.6.1(4) Adding and deleting service adapters to and from the load-balancing cluster".

(b) Adding and deleting business processes

For details on how to add and delete new business processes without stopping business processes already deployed to the HCSC server, see "5.6.1(5) Adding and deleting business processes to and from the load-balancing cluster".

(c) Changing service adapters

For details on how to change service adapters without stopping service adapters already deployed to the HCSC server, see "5.6.1(6) Changing service adapters in the load-balancing cluster configuration".

(d) Changing business processes

For details on how to change business processes without stopping business processes already deployed to the HCSC server, see "5.6.1(7) Changing business processes in the load-balancing cluster configuration".

To prevent failure of HCSC servers that configure the load-balancing cluster, it is recommended that that you prepare for sufficient number of HCSC servers for the load-balancing cluster. For details, see "7.9.2(1) Failure and recovery in load-balancing cluster configuration".