Installation considerations

Some considerations that need to be taken into account before installation.

About this task

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.
  • 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.