The new “cluster instance name” local option
About this task
One of the steps of the twsClusterAdmin
utility
is instance name registration of the HCL Workload Automation cluster
resource within the local option localopts
file.
The HCL Workload Automation agent uses the value of this new local option to signal to the HCL Workload Automation cluster resource that the agent has received a stop command.
It is important to change the value of the cluster
instance name
local option every time the HCL Workload Automation resource
instance name is changed. If the clusterinstancename
local
option does not point to the right name, the HCL Workload Automation resource
will be set to failure
state from the cluster resource
monitor. Do not specify this name in double-byte character set (DBCS)
characters.
To change the HCL Workload Automation resource
instance name use the following procedure:
- Take the HCL Workload Automation resource instance offline using the Cluster Administrator console. To verify if HCL Workload Automation stopped correctly you can use the Cluster Administrator console and check the status of the HCL Workload Automation resource instance. If the resource has failed to stop you can check in the cluster and HCL Workload Automation logs for the reason. See Traces for more details on the log files.
- From the Failover Cluster
manager console, select the resource and modify the HCL Workload Automation cluster
resource name from cluster_resource_name to cluster_resource_name_new.Note: Do not specify this name in double-byte character set (DBCS) characters.
- Open
the
localopts
file using Notepad. Modify the value of theclusterinstancename
local option. Check that the name is the same you specified for the HCL Workload Automation cluster resource in Step 2. - Modify the cluster instance
name in the
StartUp_clu.cmd
andShutDown_clu.cmd
scripts. - Bring the HCL Workload Automation resource instance online in the Failover Cluster manager console.