HCL Workload Automation, Version 9.4

Extended loss or permanent change of master domain manager

Use the following procedure to switch to the backup if the original master domain manager is not expected to return to service before the next new production period turnover (final Job Scheduler and JnextPlan job). For UNIX, use forward slashes in path names.
  1. Use the conman stop function to stop HCL Workload Automation on the master domain manager and its backup.
  2. If you copied the Security file from the master domain manager to the backup master domain manager with a suffix, now delete the backup master domain manager's own Security file and rename the Security file with the suffix as just Security.
  3. If you copied the localopts file from the master domain manager to the backup master domain manager with a suffix, now merge the backup master domain manager's own localopts file with the localopts file from the master domain manager. Look at each property in turn and determine which version you want to keep on what is going to be your new master domain manager. For example, the property thiscpu needs to be the one from the backup master domain manager, but the options for controlling how the processes run can be taken from the master domain manager.
  4. On the backup master domain manager cancel the final Job Scheduler in the Symphony file (it refers to the next production period's JnextPlan on the old master domain manager).
  5. On the backup master domain manager, use composer to modify any important job streams that run on the master domain manager, in particular the final Job Scheduler. For each of these, change the workstation name to the name of the backup.
  6. Change the workstation definition of the master domain manager from manager to fault-tolerant agent.
  7. Change the workstation definition of the backup master domain manager from fault-tolerant agent to manager.
    Note: These two steps must be done in the order given, as the system will not allow you to have two managers at the same time.
  8. On the backup master domain manager, edit the <TWA_home>/TWS/mozart/globalopts file and change the master option to the name of the backup master domain manager workstation (this is used mainly for reports production)
  9. Use the conman switchmgr function to switch to the backup master domain manager. See Switching a domain manager.
  10. Submit a new final Job Scheduler to the new master domain manager (old backup master domain manager).
  11. Run JnextPlan -for 0000 on the new master domain manager to generate the new Symphony file.
  12. Remember to log on to the backup master domain manager when opening the Dynamic Workload Console, first defining a new engine to access it.
  13. If the old master domain manager has failed or is being replaced, you can now delete its workstation definition and remove it from the network.