HCL Workload Automation, Version 9.4

Complete procedure for switching a domain manager

This section summarizes the steps required to replace a running domain manager with its backup and to complete the procedure by restoring the original domain manager to its function. Follow these steps to make sure that no overlapping problems arise with obsolete versions of the Symphony file. The steps are documented for four scenarios:
Planned outage
The domain manager is replaced with its backup for planned maintenance work (for example, an upgrade of the operating system).
Unplanned outage
The domain manager is replaced with its backup because of an unexpected failure or malfunction.
Short-term
The domain manager is expected to return to service before the next new production period turnover (run of the JnextPlan job).
Long-term
The domain manager is not expected to return to service before the next new production period turnover (run of the JnextPlan job).
Table 1. Complete procedure for switching a domain manager in case of a planned outage.
Planned outage
Short-term Long-term
1. Switch the domain manager to a backup workstation. Use either the conman switchmgr command or the Dynamic Workload Console. For more information, see the switchmgr command in HCL Workload Automation: User's Guide and Reference.

Check that the message boxes for the domain manager undergoing maintenance are large enough not to fill up before it is restored. Increase their size if necessary.

 1 Switch the domain manager to a backup workstation. Use either the conman switchmgr command or the Dynamic Workload Console. For more information, see the switchmgr command in HCL Workload Automation: User's Guide and Reference.

Check that the message boxes for the domain manager undergoing maintenance are large enough not to fill up before it is restored. Increase their size if necessary.
2. Shut down HCL Workload Automation processing on the domain manager undergoing maintenance. 2. Shut down HCL Workload Automation processing on the original domain manager undergoing maintenance.
3. In the HCL Workload Automation database assign the role of domain manager to the backup workstation. 3. In the HCL Workload Automation database assign the role of domain manager to the backup workstation.
4. Set the workstation running the original domain manager to ignore, using either the composer cpuname command or the Dynamic Workload Console.
When ready to restore the ownership of the domain to the original domain manager: When ready to restore the ownership of the domain to the original domain manager:
4. Reassign ownership of the domain to the original domain manager in the HCL Workload Automation database. 5. Remove the ignore flag from the workstation running the original domain manager.
5. Switch from the backup workstation to the domain manager using one of the methods indicated in step 1. 6. Reassign ownership of the domain to the original domain manager in the HCL Workload Automation database.

Optionally, remove in the original domain manager the conman start command from the init procedure and delete any existing copies of the Symphony, Sinfonia, and message box files. This step is recommended to avoid that any outdated symphony present in the computer is automatically triggered at the first startup. You can add conman start again later.
6. Link the domain manager from the master to download a fresh version of the Symphony file.
7. Switch from the backup workstation to the domain manager using one of the methods indicated in step 1.
8. Link the domain manager from the master to download a fresh version of the Symphony file.
Table 2. Complete procedure for switching a domain manager after an unplanned outage.
Unplanned outage
Short-term Long-term
1. Switch the domain manager to a backup workstation. Use either the conman switchmgr command or the Dynamic Workload Console. For more information, see the switchmgr command in HCL Workload Automation: User's Guide and Reference.

Check that the message boxes for the failing domain manager are large enough not to fill up before it is restored. Increase their size if necessary.

 1 Switch the domain manager to a backup workstation. Use either the conman switchmgr command or the Dynamic Workload Console. For more information, see the switchmgr command in HCL Workload Automation: User's Guide and Reference.

Check that the message boxes for the failing domain manager are large enough not to fill up before it is restored. Increase their size if necessary.
3. In the HCL Workload Automation database assign the role of domain manager to the backup workstation. 3. In the HCL Workload Automation database assign the role of domain manager to the backup workstation.
4. Set the workstation running the failing domain manager to ignore, using either the composer cpuname command or the Dynamic Workload Console.
When ready to restore the ownership of the domain to the original domain manager: When ready to restore the ownership of the domain to the original domain manager:
4. Reassign ownership of the domain to the original domain manager in the HCL Workload Automation database.

Optionally, remove in the original domain manager the conman start command from the init procedure and delete any existing copies of the Symphony, Sinfonia, and message box files. This step is recommended to avoid that any outdated symphony present in the computer is automatically triggered at the first startup. You can add conman start again later.

For an "unplanned outage", FTA needs a new Symphony file, on the current master domain manager (previous backup master domain manager) do the following:
  1. Verify that it is linked to all agents except the old master domain manager
  2. Shut down all IBM Workload Scheduler processes (unlink from all agents).
  3. Rename Sinfonia as Sinfonia.orig
  4. Copy Symphony to Sinfonia.orig

    You now have identical Symphony and Sinfonia files.

 5. Remove the ignore flag from the workstation running the original domain manager.
5. Switch from the backup workstation to the domain manager using one of the methods indicated in step 1. 6. Reassign ownership of the domain to the original domain manager in the HCL Workload Automation database.

Optionally, remove in the original domain manager the conman start command from the init procedure and delete any existing copies of the Symphony, Sinfonia, and message box files. This step is recommended to avoid that any outdated symphony present in the computer is automatically triggered at the first startup. You can add conman start again later.
6. Link the domain manager from the master to download a fresh version of the Symphony file.
7. Switch from the backup workstation to the domain manager using one of the methods indicated in step 1.
8. Link the domain manager from the master to download a fresh version of the Symphony file.