8.5.1 Creating a script to be registered into the cluster software (for UNIX)
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.
|
Verifying the Health of the Intelligent Integrated Management Database#3 |
If you are using the Intelligent Integrated Management database, verify that the Intelligent Integrated Management database is running normally.
|
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. If you are using IM database service, also kill IM database service. If you are using Intelligent Integrated Management Database (Trend data Management Database), also forcibly terminates Intelligent Integrated Management Database service.
|
- #1
-
The commands used for JP1 operations related to operation checking are the same between UNIX and Windows, but the operations are different.
Windows operations differ from UNIX operations due to their association with Windows service control. In Windows, when some of the processes terminate, the JP1 process management terminates each process automatically and places the service in stopped status. Treat service stop as an error or detect an error when a command such as jco_spmd_status returns a value of 8.
- #2
-
Executed when the IM databases are used.
- #3
-
Execute if you are using Intelligent Integrated Management Database.
- Note
-
About JP1 restart
When a JP1 failure is detected in a cluster operation system, restart of JP1 might 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 might be affected and normal operation might not be achieved. To restart JP1 successfully, use the cluster software to restart JP1.