Hitachi

Job Management Partner 1 Version 10 Job Management Partner 1/Integrated Management - Manager Configuration Guide


6.2.4 Registering into the cluster software (for Windows)

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.

The table below shows the settings for JP1/IM - Manager that are to be registered in the cluster software.

Start the services in the order from No. 1 to No. 4 in the table below. (Start the JP1/Base services and then JP1/IM - Manager services.)

Table 6‒10: Settings to be registered into the cluster software (Windows)

No.

Name

Service name

Dependencies

1

JP1/Base Event logical-host-name

JP1_Base_Event logical-host-name

IP address resource

Physical disk resource

2

JP1/Base_logical-host-name

JP1_Base_logical-host-name

Cluster resource of No. 1

3

JP1/IM-Manager DB Cluster Service_logical-host-name#1

HiRDBClusterService_JM<n>#2

Cluster resources of Nos. 1 and 2

4

JP1/IM - Manager_logical-host-name

JP1_Console_logical-host-name

Cluster resources of Nos. 1, 2, and 3#3

#1

Register the service in the cluster software only when the IM databases are used. Because this service controls the IM databases, do not register JP1/IM-Manager DB Server_logical-host-name in the cluster software. Note that the JP1/IM - Manager DB Server_logical-host-name service has started on the secondary node.

#2

<n> is a number from 1 to 9, and is the value specified in LOGICALHOSTNUMBER in the cluster setup information file. For details, see Cluster setup information file (jimdbclustersetupinfo.conf) in 2. Definition Files in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.

#3

If you do not use the IM databases, remove the cluster resource of No.3 from the dependencies.

Organization of this subsection

(1) Registering into the cluster software

(a) In MSCS (Microsoft Cluster Service) or WSFC (Windows Server Failover Cluster)

Register the services of JP1/IM - Manager and JP1/Base as MSCS or WSFC resources. Set each resource as described below. Bold type indicates an MSCS setting item. For details about how to set WSFC, see the WSFC manual.

  • For Resource Types, register as Generic Service.

  • Set Name, Dependencies, and Service name as shown in the table. The name is used to display the service, and the service name is used to specify the service that is controlled from MSCS.

  • Do not set Start parameters and Registry Replication.

  • Set the Advanced page for properties according to whether failover is to occur in the event of a JP1/IM - Manager failure.

    For example, to set failover to occur in the event of a JP1/IM - Manager failure, select the Restart and Affect the group check boxes and specify Threshold for the restart retry count. Use 3 (times) as a guideline for the value to be specified.

(b) When registering the service start and stop commands

Register into the cluster software JP1/IM - Manager and the JP1/Base services to be started and stopped. For example, specify the settings so that the services shown in the Name column in the table above will be started and stopped by the net command.

To check the operation of JP1/IM - Manager and JP1/Base, use the following commands:

  • jco_spmd_status

    Use this command to check the operation of JP1/IM - Manager (except the IM databases).

  • jimdbstatus

    Use this command to check the operation of the IM databases (when the IM databases are used).

  • jbs_spmd_status

    Use this command to check the operation of JP1/Base.

  • jevstat

    Use this command to check the operation of JP1/Base Event Service.

For details about how to use these commands, see 6.3.4 Registering into the cluster software (for UNIX).

(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 address must be available for use.

Set the start and stop sequence or dependencies in such a manner that they are controlled by the cluster software as shown below.