6.3.4 Registering into the cluster software (for UNIX)
To apply cluster operation to JP1/IM - Manager, you must register JP1/IM - Manager and JP1/Base on the logical host into the cluster software, and then set them to be started and terminated by the cluster software.
Start services in the order of resources, JP1/Base, and JP1/IM - Manager.
- Organization of this subsection
(1) Creating a script to be registered into the cluster software
When you use UNIX cluster software, you normally use a method such as a script to create a tool to control applications, and then register the script into the cluster software. In general, such a script must provide the start, stop, operation monitoring, and forced termination functions.
This subsection describes the JP1/IM - Manager information that is needed to design a script. You use this information to create a script that controls JP1/IM - Manager according to the cluster software specifications, and then you register the script into the cluster software.
Function to be registered |
Description |
---|---|
Start |
Starts JP1/IM - Manager.
|
Stop |
Terminates JP1/IM - Manager.
We recommend that you execute the forced termination command described below after the stop command has terminated. This enables you to terminate the process and prevent a failover error even in the event of a problem. |
JP1/IM - Manager operation monitoring#1 |
Monitors normal operation of JP1/IM - Manager.
To determine whether JP1/IM - Manager is running normally, check the return value of the jco_spmd_status command. This command determines the status from the operating status of each process. Some cluster software does not provide the operation monitoring function. If there is no need to perform failover in the event of a JP1/IM - Manager failure, do not register this function.
|
IM database operation status checking#2 |
Checks to see if the IM databases are running normally.
To determine the operating status, check the return value of the jimdbstatus command.
|
Forced termination |
Forcibly terminates JP1/IM - Manager and releases the current resources.
The jco_killall.cluster command forcibly terminates each process without performing JP1/IM - Manager termination processing.
|
- Reference note
-
About JP1 restart
When a JP1 failure is detected in a cluster operation system, restart of JP1 may be retried at the same server before failover to the secondary server is executed.
In such a case, do not perform restart using JP1 process management.
The cluster software attempts restart after detection of the JP1 failure. Depending on the nature of the failure, JP1's restart function may be affected and normal operation may not be achieved. To restart JP1 successfully, use the cluster software to restart JP1.
(2) Setting the resource start and stop sequence
To execute JP1/IM - Manager and JP1/Base on the logical host, the shared disk and logical IP addresses must be available for use.
Set the start and stop sequence or resource dependencies in such a manner that they are controlled by the cluster software as shown below.
-
When the logical host starts
-
Allocate the shared disk and logical IP addresses, and make them available for use.
-
Start JP1/Base and JP1/IM - Manager, in this order.
-
-
When the logical host terminates
-
Terminate JP1/IM - Manager and JP1/Base, in this order.
-
Release the allocation of the shared disk and logical IP addresses.
-