The master domain manager

The HCL Workload Automation master domain manager is not supported as a cluster resource for the following reasons:

• The master domain manager runs the JnextPlan critical job stream. The responsibility of the job stream is to create a new plan for the current production day. This process cannot be interrupted. An interruption might cause malfunctions and scheduling service interruptions. Only manual steps can be used to recover from such malfunctions or service interruptions. Because failover of the cluster group that contains the HCL Workload Automation resource stops the agent on the current node and starts it on a different node, if failover happens during running of JnextPlan it could be destructive.
• The HCL Workload Automation command-line utilities (conman, composer, and so on) are not aware of the cluster and if they are interrupted (through a failover of the cluster group that contains the HCL Workload Automation resource) they might corrupt some vital information for HCL Workload Automation.