Installation considerations

Before you begin the installation using the installation wizard, consider the following items that might apply to your specific environment.

Installing on Windows operating systems

If you are installing on Windows, consider the following items.

• If you are using Windows Terminal Services, set the install user with the command: change user /install
• If <TWS_user> is a domain user, Microsoft Computer Browser Service must be active. This is required for IBM® WebSphere Application Server authentication.
• If <TWS_user> is a domain user, the user performing the installation must be a domain administrator.

Choosing language settings and national characters

If you want to use characters of a specific language locale, the language you choose for the installation wizard must match the language locale settings of the workstation on which you are installing. You cannot use national characters in the installation path of a master domain manager or backup master domain manager. Additionally, you cannot add a distributed connector to an agent that has national characters in its installation path.

Performing silent installations

When you install the latest version of HCL Workload Automation, you can create a response file based on the parameters of the initial installation. You can then use this customized response file to run silent installations using the same parameters. Before running the initial installation, you might want to consider this feature. For more information, see Performing a silent installation.

Mapped drives

When you copy the image of a specific operating system onto the workstation for installation using the wizard, you must copy the complete contents of the DVD to the drive from where you run your installation. When the drive is a UNC mapped drive, the remote path must be mapped to a drive on the installation workstation. For a complete list of the supported operating systems and their prerequisites, see the HCL Workload Automation System Requirements Document at https://workloadautomation.hcldoc.com/help/topic/com.hcl.wa.doc_9.4/distrDDguides.html.

Remote installation

You cannot install HCL Workload Automation on a Windows workstation from a remote Samba-mounted file system.

Installing for end-to-end scheduling

If you are installing HCL Workload Automation on a workstation used as a distributed agent (that is either a standard agent, fault-tolerant agent, or domain manager) for end-to-end scheduling, specify OPCMASTER as the name of the master domain manager during the installation process. For further information about installing for end-to-end scheduling, see Scheduling End-to-end with Fault Tolerance Capabilities (z/OS).

Create symbolic links

UNIX and Linux. The installation wizard installs all executable files in its own .bin directory. Before running any HCL Workload Automation commands, you run a script that sets the command-line environment to access these files. To avoid having to set the environment each time you want to run any of the commands from within a script, you can select an installation option to create symbolic links to those commands or utilities most frequently used from within scripts. Table 1 shows the binary paths and the symbolic links.

Table 1. Symbolic link options

TWS binary path	Symbolic link
<TWS_home>/bin/at	usr/bin/mat
<TWS_home>/bin/batch	usr/bin/mbatch
<TWS_home>/bin/datecalc	usr/bin/datecalc
<TWS_home>/bin/jobstdl	usr/bin/jobstdl
<TWS_home>/bin/maestro	usr/bin/maestro
<TWS_home>/bin/mdemon	usr/bin/mdemon
<TWS_home>/bin/morestdl	usr/bin/morestdl
<TWS_home>/bin/muser	usr/bin/muser
<TWS_home>/bin/parms	usr/bin/parms