HCL Workload Automation, Version 9.4

Switching a master domain manager or dynamic domain manager

Switching a master domain manager or dynamic domain manager affects the running dynamic workload broker server.

The installation of a master domain manager or dynamic domain manager and of its backup workstations includes also the installation of a dynamic workload broker server.

Before you switch your master domain manager or dynamic domain manager to a backup workstation, you must stop the dynamic workload broker server. After the switch completed, you must start the dynamic workload broker server on the new master domain manager or dynamic domain manager. The process is not automatic and you must ensure that you avoid having two concurrently active servers.

If you have to switch the master domain manager or dynamic domain manager because the system running the current workstation failed, make sure that also the dynamic workload broker server is down. In this case, you need only to start the new dynamic workload broker server after switching the master.

If you switch the master domain manager or dynamic domain manager for any other reason than a system failure, and you are switching to a backup workstation while the system running the current master domain manager or dynamic domain manager is up, you risk having two concurrently active servers. To avoid this stop the current dynamic workload broker server before you switch, and start the new instance after the backup workstation takes over.

Here is the procedure to follow every time you switch the master domain manager or dynamic domain manager if you run dynamic scheduling in your network:
  1. If the dynamic workload broker server on the current master domain manager or dynamic domain manager is still running, stop it. Use wastool stopBrokerApplication.sh on UNIX and Linux or stopBrokerApplication.bat on Windows as follows: 
    stopBrokerApplication [-user username -password password] [-port portnumber]
    where,
    username and password
    The credentials used at installation. The user and password are optional. By default, the script looks for the credentials in the soap.client.props file located in the properties directory of the WebSphere Application Server profile.
    portnumber
    The parameter is optional. If it is not specified, the default is used.
  2. Switch the master domain manager or dynamic domain manager to a backup workstation. Use either the conman switchmgr command or the Dynamic Workload Console. For more information, see the section about the switchmgr command in HCL Workload Automation: User's Guide and Reference.
  3. Start the dynamic workload broker server running with the new workstation. Use wastool startBrokerApplication.sh on UNIX and Linux or startBrokerApplication.bat on Windows as follows: 
    startBrokerApplication [-user username -password password] [-port portnumber]
    where,
    username and password
    The credentials used at installation. The user and password are optional. By default, the script looks for the credentials in the soap.client.props file located in the properties directory of the WebSphere Application Server profile.
    portnumber
    The parameter is optional. If it is not specified, the default is used.
  4. Link the dynamic workload broker server running with the new workstation running the following command: 
    conman link broker_workstation_name