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 the computer where you are installing the agent cannot connect to the master domain manager site but a computer in your network can connect to the master domain manager. This computer acts as a gateway in your network zone.

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. On the computer than cannot connect to the master domain manager, install the agent, let's call it Agent 2, as follows:

Note: For operating system commands, see Command reference.
  1. Verify the supported operating systems and prerequisites.
  2. Before you start the installation, ensure your computer meets the following requirements:
    • For Solaris 64-bit: temporary disk space 250 MB, installation directory space inst_dir 470 MB
    • For Linux for IBM System z: temporary disk space 300 MB, installation directory space inst_dir 480 MB
    • For Linux for PCC: temporary disk space 325 MB, installation directory space inst_dir 420 MB
    • For Linux temporary disk space 250 MB, installation directory space inst_dir 470 MB
    • For AIX temporary disk space 270 MB, installation directory space inst_dir 570 MB
    • For HP-UX temporary disk space 270 MB, installation directory space inst_dir 570 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 agent installation files to this directory:
    • For Solaris 64 bit, extract the TWS94_SOL_I386_AGENT.zip
    • For Linux for IBM System z, extract the TWS94_LNX_S390_AGENT.zip
    • For Linux for PPC, extract the TWS94_LNX_PPC_AGENT.zip
    • For Linux, extract the TWS94_LNX_X86_64_AGENT.zip
    • For AIX, extract the TWS94_AIX_AGENT.zip
    • For HP-UX, extract the TWS94_HPIA64_AGENT.zip
  6. From a shell on the computer on which you want to install the product, log on as root.
    Installing as a non-root user is also possible, but be aware of the following implications on the use of the uname keyword of the installWAAgent command, which becomes an optional parameter, and on its effect on the user_name of the agent. That is:
    • The uname keyword can be omitted because user_name is automatically set to the login name of the installer. If the installer specifies a uname with a different user_name value, an error message is returned.
    • As a consequence, the agent can run jobs uniquely with the user name of that installer.
    • Future upgrades, modifications, and removal of the agent can be made exclusively with the same login used for installation. To keep track of the login name used by the installer, at installation time the read-only InstallationLoginUser parameter is recorded with the login name in the JobManager.ini configuration file in the agent installation directory.
    Enter the following command to set the execute permission for the installation program:
    chmod a+x installWAAgent.sh
  7. If you are installing as the root user, create the user for which the agent is installed with the home directory.
    If you are installing as a different user, this step is not necessary as the login under which you are installing automatically becomes also the user of the agent. Ensure that the directory permission of home_dir (which is where the agent will be installed) is set to 755 and that your login owns it.
    Important: If you are installing as non-root user, and you use the su- non-root username command in the shell where you are about to run installWAAgent, make sure that $HOME is set on your home directory as a non-root user (use echo $HOME to verify that the value returned corresponds to your home directory).
  8. Change to the directory where you downloaded the agent installation files.
  9. Install Agent 1 and then install Agent 2. The installation of Agent 2 depend on whether you install Agent 1 using the default installation settings or if you install Agent 1 using custom settings.
    Agent 1 installed using the default installation parameter settings
    The 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 the default installation settings, submit the following command:
    ./installWAAgent.sh -new [-uname <user_name>] 
     -gateway remote -gwhostname <host_name_of_Agent1>
     -acceptlicense yes
    This command performs an installation assigning the default values for the installation parameters. If you want to customize some of these values, for example the value of the -jmport parameter because the default port number is already in use, you can use the following command instead:
    ./installWAAgent.sh -new [-uname <user_name>] 
    -jmport <jmport_value>
    -gateway remote -gwhostname <host_name_of_Agent1> 
     -gwport <jmport_number_Agent1> 
    -acceptlicense yes
    You can also customize other parameters such as the installation directory or the display name for your agent. See UNIX, Linux, and IBM i command syntax and parameters for more information about all of the customizable parameters.
    Agent 1 installed using a custom installation, with custom values for the -jmport parameter
    If you installed Agent 1 using a custom installation to customize the -jmport parameter such as following:
    ./installWAAgent.sh -new -uname <user_name>
    -jmport <jmport_value> -acceptlicense yes
    Then, install Agent 2 and Agent 3 as follows:
    ./installWAAgent.sh -new [-uname <user_name>] 
    [-jmport <jmport_value>]
    -gateway remote -gwhostname <host_name_of_Agent1>
    -gwport <jmport_number_Agent1> -acceptlicense yes
    Where:
    -uname user_name
    • If you logged in as the root user, it is the name of the user for which the agent is installed. This is the user you created in the previous step. Do not confuse this name with the user performing the installation logged on as root, or with the user name you received by email when you requested your subscription.
    • If you logged in as another user, you do not need to specify this keyword as it automatically takes the login name.
    -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.
    -gateway local|remote
    • Use local to specify that the computer can connect directly with the master domain manager and that it also routes communication for other computers that cannot communicate directly. 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 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.
    -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.

To customize any of the default installation settings, see UNIX, Linux, and IBM i command syntax and parameters.

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.