HCL Workload Automation on Amazon Web Services

Scenario 2: Computers that cannot connect to the master domain manager but connect through a computer that acts as a gateway

Installation procedure for computers that cannot connect to master domain manager but connect through a computer that acts as a gateway.

This scenario describes your environment if you have computers in your network that cannot connect to the master domain manager. The following installation procedure uses an agent installed on a computer which can successfully connect, as a gateway, for those computers that cannot.

To configure your network, first install the agent, let's call it Agent 1, on the computer that can connect to the master domain manager using the install.bat file as explained in Scenario 1: Direct connection; your computer can connect to the master domain manager. The install.bat file uses the default installation parameter settings. On the computers than cannot connect to the master domain manager, install the agent, , let's call it Agent 2, as follows:

  1. Verify the supported operating systems and prerequisites.
  2. Before you start the installation, ensure your computer meets the following requirements:
    • temporary disk space 360 MB
    • installation directory space 660 MB
  3. If you did not already download the agent installation files, go to the Dynamic Workload Console landing page. In the Download and Install section, you can download the agent installation files for the selected operating system platform.
  4. Go to the directory where you saved the compressed agent installation files, for example \WAAgent.
  5. Extract the TWS94_WINDOWS_X86_64.zip agent installation file.
  6. The installation steps require that you login as Administrator and that the User Account Control (UAC) is set to Never notify. To verify that the User Account Control (UAC) is set to Never notify, see Check your Windows User Account Control (UAC) settings.
  7. To log in as Administrator, open a command prompt with the Administrator login account, by right-clicking the Command Prompt icon and selecting Run as Administrator.
  8. In the command prompt, move to the directory where you extracted the agent installation files.
  9. The installation of this agentAgent 2 depend on whether you installed Agent 1 using the default installation settings or if you installed Agent 1 using custom settings.
    Agent 1 installed using the default installation parameter settings or using the install.bat file
    The install.bat file or a default installation assigns port number 31114 to the -jmport parameter to dispatch the workload, and port number 31132 for the -gwiefport parameter to dispatch events. To install Agent 2 using default installation settings, submit the following command:
    cscript installWAAgent.vbs -new -uname <user_name> 
    -password <user_password> -gateway remote -gwhostname 
    <host_name_of_Agent1> -acceptlicense yes
    This command performs an installation assigning default values. If you want to customize some of these values, for example, the value of the -jmport parameter, or other parameters such as the installation directory or the display name for your agent, see Windows command syntax and parameters.
    Agent 1 installed using a custom installation, with a custom value for the -jmport parameter
    If you installed Agent 1 using a custom installation to customize the -jmport parameter such as following:
    cscript installWAAgent.vbs -new -uname <user_name> 
    -password <user_password> -jmport <jmport_value>
    -acceptlicense yes
    Then, install Agent 2 as follows:
    cscript installWAAgent.vbs -new -uname <user_name> 
    -password <user_password> [-jmport <jmport_value>]
    -gateway remote -gwhostname <host_name_of_Agent1>
    -gwport <jmport_of_Agent1> -acceptlicense yes
    specifying -jmport <jmport_value> only if you need to assign a value different from the default value.
    Where:
    -uname user_name
    The name of the user for which the agent is installed. Choose a valid user account ID for your operating system. The installation creates the user on your computer, if it does not exist. The agent you install runs with this account ID, or with the user name you received by email when you requested your subscription.
    -password user_password
    The password of the user for which you are installing the agent. Password may include alphanumeric, dash (-), and underscore (_) characters, and the following symbols: ()!?=ˆ*/˜ [] $`+;:.,@. Follow your company rules for the password characters and length.
    -gateway local|remote
    • Use local to specify that the computer can connect directly with the master domain manager site and that it also routes communication for other computers that cannot communicate directly with the site. This is the default setting.
    • Use remote to specify that the computer on which you are installing the agent communicates with the master domain manager site through a gateway configured on a different agent.
    -gwhostname host_name_of_Agent1
    This is the fully qualified host name or IP address of the remote gateway you want to use. In our example, this corresponds to Agent 1.
    -jmport port_number
    This is the port through which this agent is contacted. The default is 31114. The valid range is from 1 to 65535.
    -gwport jmport_number_of_Agent1
    This is the jmport number of the remote gateway you want to use. In our example, this corresponds to Agent 1.
    -acceptlicense yes|no
    Specify whether or not to accept the License Agreement. If you specify no, the update exits without performing any action.

    If you want to install the agent by customizing one or more default values, see Windows command syntax and parameters.

    During the installation, if you receive a security warning, click Run to continue.

After a successful installation proceed with the installation of another agent if necessary.

If the installation did not complete successfully, an error is displayed on the screen. Correct the error as described in the error Operator Response that you find in the inst_dir\logs file, and rerun the installation.