Maintaining the dynamic workload broker server on the master domain manager and dynamic domain manager
About this task
Because one dynamic workload broker server is
installed with your master domain manager and dynamic domain manager, and one server with every backup
manager, you have at least two servers present in your HCL Workload Automation network. The server running with the
master domain manager is the only one active at any
time. The servers installed in the backup managers are idle until you switch managers, and the
server in the new manager becomes the active server. To have a smooth transition from one server to
another, when you switch managers, it is important that you keep the same configuration settings in
the ResourceAdvisorConfig.properties
and
JobDispatcherConfig.properties
files in all your servers. When you make a change in
any of these files of your running dynamic workload broker server, remember to apply the same
change also in the dynamic workload broker server
idling on your backup manager.
It is important
that you also keep the data pertinent to every dynamic workload broker server
up-to-date. If you change the host name or port number of any of your dynamic workload broker servers,
use the exportserverdata
and importserverdata
commands
from the dynamic workload broker command
line to record these changes in the HCL Workload Automation database.
For information about these commands, see Scheduling Workload Dynamically.
The database records for your workload broker workstations all have LOCALHOST as the host name of the workstation. Leave the record as-is. Do not replace LOCALHOST with the actual host name or IP address of the workstation. LOCALHOST is used intentionally to ensure that the jobs submitted from HCL Workload Automation are successfully sent to the new local dynamic workload broker when you switch the master domain manager or dynamic domain manager.