Examples
About this task
For all the examples described below it is assumed that HCL Workload Automation 10.1 Fix Pack 6 has been installed.
In all the examples described below the following
definitions are used:
mydom- Is the Windows® User Domain of the HCL Workload Automation user.
mytwsuser- Is the HCL Workload Automation user name.
mytwspwd- Is the password for the
MYDOM\mytwsuserdomain user. myresgroup- Is the name of the cluster resource group selected.
myip- Is the name of the IP Address resource type within the
myresgroupresource group. mynetname- Is the name of the Network Name resource type within the
myresgroupresource group. mydisk- Is the name of the Physical Disk resource type within the
myresgroupresource group. - my shared desktop
- Is the name of the shared desktop that all instances of jobmon will use.
- myResName
- Is the customized name of the resource instance.
The examples are as follows:
- Example 1: First installation of HCL Workload Automation in a Windows cluster environment
- Example 2: Install and configure the new custom resource for an existing installation of HCL Workload Automation
- Example 3: Add a new agent in a cluster environment with HCL Workload Automation already installed
- Example 4: Add a custom resource type instance to an existing cluster group
- Example 5: Configure HCL Workload Automation in a new joining node of the cluster
- Example 6: Deregister HCL Workload Automation on all nodes of the cluster except for the current node
- Example 7: Install a new version of the cluster resource DLL into the cluster
- Example 8: Force the upgrading/downgrading of the cluster resource DLL into the cluster
- Example 9: First installation of domain manager in Windows cluster environment, specifying generic options
- Example 10: Upgrading agents in a cluster-aware configuration
- Example 11: First installation of HCL Workload Automation in a Windows cluster environment, defining shared desktop
- Example 12: First installation of HCL Workload Automation in Windows cluster environment, using customized resource instance name
- Example 13: Changing the resource instance name