Installation paths

HCL Workload Automation is the name of a family of products and components, which includes the following:
  • HCL Workload Automation
  • HCL Workload Automation for Z
  • HCL Workload Automation for Applications
  • Dynamic Workload Console

Many HCL Workload Automation components are installed in what is called an HCL Workload Automation instance.

This section describes the installation paths of the HCL Workload Automation components:
TWA_home installation path
Many of the components are installed in an HCL Workload Automation instance. Although this is a notional structure it is represented on the computer where you install HCL Workload Automation components by a common directory referred to in the documentation as TWA_home. The path of this directory is determined when you install an HCL Workload Automation component for the first time on a computer. You have the opportunity to choose the path when you make that first-time installation, but if you accept the default path, it is as follows:
On UNIX operating systems
On Windows operating systems
%Program Files%\wa\server<n>
where <n> is an integer value ranging from 0 for the first instance installed, 1 for the second, and so on.

This path is called, in the publications, TWA_home. For details about the directories created outside of TWA_home, see Directories created outside of TWA_home at installation time .

TWA_DATA_DIR and DWC_DATA_dir configuration directories

To simplify administration, configuration, and backup and recovery on UNIX systems, a new default behavior has been implemented with regard to the storage of product data and data generated by HCL Workload Automation, such as logs and configuration information. These files are now stored by default in the <data_dir> directory, which you can optionally customize at installation time.

By default, this directory is TWA_home/TWSDATA for the server and agent components, and DWC_home/DWC_DATA for the Dynamic Workload Console. The product binaries are stored instead, in the installation directory.

You can optionally customize the <data_dir> directory at installation time by setting the --data_dir argument when you install using the command-line installation. If you want to maintain the previous behavior, you can set the --data_dir argument to the HCL Workload Automation installation directory.

If you deploy the product components using Docker containers, the <data_dir> is set to the default directory name and location, and it cannot be modified.

To retrieve the TWA_DATA_DIR and DWC_DATA_dir location in case you have modified the default path, check the values for the TWS_datadir and DWC_datadir properties stored in the twainstance<instance_number> file. The file is located in /etc/TWA.

Alternatively, you can also proceed as follows:
  1. Browse to <TWA_home>/TWS path.
  2. Source the . ./ shell script.
  3. Type echo $UNISONWORK. As a result, the path to the TWA_DATA_DIR is returned.
HCL Workload Automation installation path
You can install more than one HCL Workload Automation component (master domain manager, backup master domain manager, domain manager, or backup domain manager) on a system, but each is installed in a separate instance of HCL Workload Automation, as described above.
The installation path of HCL Workload Automation is:
  • <TWA_home>/TWS
DWC_home installation path
The Dynamic Workload Console can be installed in the path of your choice, but the default installation path is as follows:
On Windows operating systems
On UNIX operating systems
On z/OS operating system
HCL Workload Automation agent installation path
The agent also uses the same default path structure, but has its own separate installation directory:
  • <TWA_home>/TWS/ITA/cpa
Note: The agent also installs some files outside this path. If you have to share, map, or copy the agent files (for example when configuring support for clustering) share, map, or copy these files, as well:
On UNIX operating systems
   (on Linux and Solaris)
   (on AIX)
   (on HP-UX)
On Windows operating systems
The agent uses the following configuration files which you might need to modify:
This file contains the parameters that tell the agent how to run jobs. You should only change the parameters if advised to do so in the HCL Workload Automation documentation or requested to do so by HCL Software Support. Its path is:
On UNIX operating systems
On Windows operating systems
When a dynamic agent is installed and -gateway local|remote is specified, then this file contains the same parameters as the JobManager.ini file except for the following differences:
  • The ResourceAdvisorUrl parameter points to the dynamic workload broker, and not the master domain manager.
The JobManagerGW.ini file is installed in the following location:
On UNIX operating systems
On Windows operating systems
This file contains parameters which determine how the agent behaves. Changing these parameters may compromise the agent functionality and require it to be reinstalled. You should only change the parameters if advised to do so in the HCL Workload Automation documentation or requested to do so by HCL Software Support. Its path is:
On UNIX operating systems
On Windows operating systems
Installation path for files giving the dynamic scheduling capability
The files that give the dynamic scheduling capability are installed in the following path:
  • <TWA_home>/TDWB
The command line client installation path
The command line client is installed outside all HCL Workload Automation instances. Its default path is:
  • TWA_home/TWS/CLI

However, the information above supplies only the default paths. To determine the actual paths of products and components installed in HCL Workload Automation instances, see Finding out what has been installed in which HCL Workload Automation instances