Hitachi

JP1 Version 12 JP1/Automatic Operation Configuration Guide 

4.3.2 Procedure to change the host name of the JP1/AO server (cluster system)

For a cluster system, the host name of the logical host can be changed, but not the host name of the physical host.

If JP1/OA, Hitachi Command Suite products, or Hitachi Ops Center products are installed, you need to change the settings in JP1/OA, Hitachi Command Suite products, or Hitachi Ops Center products at the same time. For details, see the manuals for JP1/OA, Hitachi Command Suite products, or Hitachi Ops Center products.

Before you begin

Log in to the JP1/AO server as a user who has not only administrator or root permissions on the OS, but also administrator permissions on the cluster.

To change the host name of the JP1/AO server:

  1. In the Tasks window, check the tasks. If any tasks are in execution status (In Progress, Waiting for Input, In Progress (with Error), In Progress (Terminating), or Long Running), stop execution of the tasks or wait until the task status changes to the ended status.

  2. Use the cluster software to move the resource group where the JP1/AO service is registered to the active server.

  3. Use the cluster software to bring the above resource group online.

  4. Use the cluster software to take services other than the HiRDB/ClusterService _HD1 service and scripts offline.

  5. On the active server, execute the hcmds64srv command with the /stop option specified to stop the JP1/AO service.

  6. Use the cluster software to bring the service (HiRDB/ClusterService _HD1) offline.

  7. In the cluster software, suppress failover for the resource group where JP1/AO services and scripts is registered.

    Right-click a service or script in the cluster software, select Properties, and then Policies. Then, specify the settings so that a restart does not occur if the resource fails. Perform this action for all services and scripts registered in the resource group in order to suppress failover.

  8. In the cluster software, change the logical host name (client access point) of the resource group in which JP1/AO is registered.

  9. Use the cluster software to move the resource group where the JP1/AO service is registered to the active server.

  10. On the active server, modify the cluster settings file (Common-Component-installation-folder¥conf¥cluster.conf).

    For details, see 5.5 Cluster settings file (cluster.conf).

  11. On the active server, edit the user_httpsd.conf file to change the value of the ServerName directive to the new host name.

    The user_httpsd.conf file is stored in the following folder:

    • If the OS of the JP1/AO server is Windows

      Common-Component-installation-folder\uCPSB\httpsd\conf

    • If the OS of the JP1/AO server is Linux 6, Linux 7, SUSE Linux 12

      /opt/HiCommand/Base64/uCPSB/httpsd/conf

    • If the OS of the JP1/AO server is Linux 8

      /opt/HiCommand/Base64/uCPSB11/httpsd/conf

    If HTTPS connections are enabled, re-obtain the SSL server certificate and change the value of the ServerName directive in the VirtualHost directive to the new host name.

  12. If the OS is Linux, on the active server, execute the hcmds64srv command with the status option specified to check the status of each service. If the database for the Common Component (HiRDB service) is not running, start the database by executing the hcmds64dbsrv command with the start option specified.

  13. If the HAutomation Engine Web Service is running on the active server, stop it by executing the hcmds64srv command with the /stop /server AutomationWebService option specified.

  14. Execute the setupcluster command on the active server.

  15. Use the cluster software to move the resource group where the JP1/AO service is registered to the standby server.

  16. On the standby server, create a cluster settings file (Common-Component-installation-folder¥conf¥cluster.conf).

    For details, see 5.5 Cluster settings file (cluster.conf).

  17. On the standby server, edit the user_httpsd.conf file to change the value of the ServerName directive to the new host name.

    The user_httpsd.conf file is stored in the following folder:

    • If the OS of the JP1/AO server is Windows

      Common-Component-installation-folder\uCPSB\httpsd\conf

    • If the OS of the JP1/AO server is Linux 6, Linux 7, SUSE Linux 12

      /opt/HiCommand/Base64/uCPSB/httpsd/conf

    • If the OS of the JP1/AO server is Linux 8

      /opt/HiCommand/Base64/uCPSB11/httpsd/conf

    If HTTPS connections are enabled, re-obtain the SSL server certificate and change the value of the ServerName directive in the VirtualHost directive to the new host name.

  18. If the OS is Linux, on the standby server, execute the hcmds64srv command with the status option specified to check the status of each service. If the database for the Common Component (HiRDB service) is not running, start the database by executing the hcmds64dbsrv command with the start option specified.

  19. If the HAutomation Engine Web Service is running on the standby server, stop it by executing the hcmds64srv command with the /stop /server AutomationWebService option specified.

  20. Execute the setupcluster command on the standby server.

  21. Use the cluster software to move the resource group where the JP1/AO service is registered to the active server.

  22. Use the cluster software to enable failover of the resource group where JP1/AO services and scripts is 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.

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

To Page Top

All Rights Reserved. Copyright (C) 2019, 2022, Hitachi, Ltd.