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 install an HCL Workload Automation component, either agent or server, in the C:\ or C:\Program Files\ directories, the twsuser or any user other than the Administrator might encounter issues when running commands from the command-line interface due to security settings. For example, the resource command-line interface might fail to run commands, and the conman command might display error or warning messages. To prevent these issues, open the command prompt with the Run as administrator option to run commands.
• 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.
• If TWS_USER is a domain user, the user performing the installation must be a domain administrator.

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.

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. Symbolic link options 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