5.5.4 Registering daemons in the cluster software
In the cluster software used in your system, register the JP1/Base daemons for failovers. For details on the registration procedure, see the documentation for your cluster software. Remember the following points when registering services:
-
Ensure that the secondary node can take over the daemons from the primary node, together with the IP address and shared disk. Also, if the failover of an application program leads to the failover of a service, ensure that the secondary node can also take over the application program.
-
After the logical IP address and shared disk have become available, start JP1/Base first, and then start JP1/IM and JP1/AJS. When stopping the products, stop them in the reverse order.
-
Before registering the daemons to the cluster software, change the value of the LANG environment variable of jbs_start.cluster to the language specified in jp1bs_env.conf for the logical host.
The information needed when registering JP1/Base into cluster software is shown below:
Functionality |
Description |
---|---|
Start |
Start JP1/Base.
|
Stop |
Stop JP1/Base.
|
Operation monitoring |
Use the return values from the jbs_spmd_status and jevstat commands to monitor whether JP1/Base is operating normally. These commands judge the operating status based on whether each process is running or not. Some clustering software does not support this functionality. Register this functionality only when a failover is required upon a failure in JP1/Base.
|
Kill |
Kill JP1/Base and release the resources it has been using.
When you execute the jbs_killall.cluster command, each process is forcibly stopped without performing any processing for stopping JP1/Base.
|
- #
-
In Windows, operation differs from that in UNIX due to the relationship with service control by Windows. If some processes have stopped in Windows, the JP1 process management automatically stops all the processes, placing the service into the stopped state. You can determine a failure by detecting the stop of the service or when the jbs_spmd_status command returns a value of 8.
- Remarks: Restarting JP1
-
If a JP1 failure is detected in a cluster system, the primary server might restart JP1 to attempt recovery before it performs a failover to the secondary server.
In such a case, we recommend that you use the clustering software control to restart JP1 rather than restarting by JP1 process management.
The clustering software attempts to restart JP1 after a failure is detected, so that it might prevent the normal operation of the JP1 restart functionality. To ensure a more reliable restart, restart JP1 under the control of the clustering software.