HCL Workload Automation, Version 9.4

Changing a domain manager or dynamic domain manager

About this task

A domain manager or dynamic domain manager might need to be changed because you want it to run on a different workstation, or it might be forced on you as the result of network linking problems or the failure of the domain manager or dynamic domain manager workstation itself. This section, and its subsections, describes how to prepare for and use a backup domain manager or dynamic domain manager. However, if the domain manager to be changed is a master domain manager, there are some specific additional steps to perform; see Changing a master domain manager.

Running without a domain manager has the following effects:
  • Agents and subordinate domain managers cannot resolve inter-workstation dependencies, because activity records broadcast by the master domain manager are not being received.
  • The upward flow of events is interrupted. This impacts events that report the status of jobs, job streams and dependencies defined on workstations in the HCL Workload Automation network hierarchy under the failed domain manager.
  • Standard agents that are hosted by the failed domain manager cannot perform any processing, since they depend on the domain manager for all scheduling and job launching.

If the problem is expected to be of short duration, you can wait for the problem to be resolved and HCL Workload Automation will recover on its own, as described in the HCL Workload Automation: Troubleshooting Guide in the section about network linking problems. If you are uncertain about the duration, or if you want to restore normal agent operation, you must switch to a backup, as described in the following sections.