Hitachi

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Operation Configuration Guide


5.4.6 Procedure to register services by using the cluster software (if Common Component is already installed)

Register services by using the cluster software.

To register services by using the cluster software:

  1. Use the cluster software to move the resource group where the Hitachi Command Suite products are registered to the active server.

  2. Use the cluster software to register services in the resource group where the Hitachi Command Suite products are registered.

    Set the service dependencies in the order listed below. In the case of JP1/Base Event logical-host-name, set the dependency to the shared disk and client access point.

    Register 1 to 7 as service resources. Register 8 as a script resource.

    1. JP1/Base Event logical-host-name

    2. JP1/Base_logical-host-name

    3. HiRDB/ClusterService _HD0

    4. HBase Storage Mgmt Common Service

    5. HBase Storage Mgmt Web Service

    6. HAutomation Engine Web Service

    7. HAutomation Engine logical-host-name

    8. stopcluster command

    Here, logical-host-name means the logical host name specified in the cluster settings file.

    If values are specified in Startup Parameters in the General Tab, remove the values.

    For the stopcluster command, specify any value for the resource name and executable script name. Specify the stopcluster command to be executed only when this resource is placed offline. For details about how to specify the command, refer to the documentation of your cluster software.

    Note that, if this resource is accidentally executed online, a KNAE01635-E message is output and task operation fails. In this case, stop JP1/AO, specify this resource to be executed only offline, and then restart JP1/AO.

  3. In the cluster software, enable failover for the resource group where the Hitachi Command Suite products are registered.

    Right-click a service or script in the cluster software, select Properties, and then Policies. Then, specify the settings so that a restart can be attempted on the current node if the resource fails and all resources in the target service or application can be failed over if restart fails. Perform this action for all services and scripts registered in the resource group in order to enable failover.

  4. Bring the resource group online by using the cluster software.

Related topics