HCL Workload Automation, Version 9.4

Installation paths

This section describes the installation paths of the HCL Workload Automation components:
TWA_home installation path
As described above, 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 a 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:
C:\Program Files\HCL\TWA<n>
where <n> is an integer value ranging from <null> 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 Planning and Installation Guide.

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
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:
UNIX and Linux operating systems
   (on Linux and Solaris)
   (on AIX)
   (on HP-UX)
Windows operating systems
%ALLUSERSPROFILE%\Application Data\hcl\CAP\EMICPA_default.xml
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:
  • <TWA_home>/TWS/ITA/cpa/config/JobManager.ini
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:
  • <TWA_home>/TWS/ITA/cpa/config/JobManagerGW.ini
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:
  • <TWA_home>/TWS/ITA/cpa/ita/ita.ini
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
Dynamic Workload Console 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
C:\Program Files\HCL\TWAUI
The WebSphere Application Server installation path
The WebSphere Application Server is automatically installed when you create a new HCL Workload Automation instance. You can specify any path for the installation. The default installation path is:
  • <TWA_home>/WAS
  • For the Dynamic Workload Console: C:\Program Files\HCL\JazzSM
The command line client installation path
The command line client is installed outside all HCL Workload Automation instances. Its default path is:
C:\Program Files\HCL\TWS\CLI
The application server tools installation path
Because the WebSphere Application Server is not supplied with an administration GUI, many of its administration tasks are performed by running tools supplied with HCL Workload Automation, that perform the required configuration changes. These tools are known as the wastools, and are installed in:
  • <TWA_home>/wastools

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