HCL Workload Automation on Amazon Web Services

Installing additional gateways for Scenario 3 on UNIX and Linux operating systems

Installation procedure for computers that act as gateways. You are in an environment where computers are located in two different networks and cannot communicate with each other, but at least one computer in each network can connect to the master domain manager.

You can optionally install one or more additional gateways to balance the workload across several workstations to improve network traffic and performance, and to work as a backup, using additional gateways when a gateway stops working.

To configure your network, first install the agent acting as a gateway, in our example Agent 4, following the instructions in Scenario 3: Computers in two different networks cannot communicate with each other, but at least one computer in each network can connect to the master domain manager then install one or more additional agents to act as gateways; in our example Agent 4A. The same procedure applies to all the network zones in your environment.

To install another agent that acts as a gateway, complete the following steps:
  1. Install the agent, in our example Agent 4A, by using the following command:
    ./installWAAgent.sh -new [-uname user_name] -gateway local -gwid gateway_site_label
     -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.
    -gateway local
    This parameter is used 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.
    -gwid gateway_site_label
    This is a name that identifies your gateway site. This value must have the same value as the one you defined for Agent 4. In this way, Agent 4 and Agent 4A can mutually take over routing communications from the agents connected to them. All the gateways belonging to the same zone must have the same gateway_site_label and must be able to communicate with each other. In our example, specify -gwid Rome.
  2. Stop all the agents acting as gateways by running the following command from the agent installation directory:
    ./ShutDownLwa
  3. On each of these agents, go to the directory where the JobManagerGW.ini file is located. By default, this file is located in TWA_home/TWS/ITA/cpa/config/JobManagerGW.ini.
  4. Open the file in a text editor and locate the JobManagerGWURIs property. Set the JobManagerGWURIs property as follows:
    JobManagerGWURIs = https://<hostname_of_Agent_4>:<port_number_of_Agent4>/ita/JobManagerGW/
     JobManagerRESTWeb/JobScheduler/resource,https://<hostname_of_Agent4A>:
     <port_number_of_Agent4A>/ita/JobManagerGW/JobManagerRESTWeb/JobScheduler/resource
    Where:
    hostname_of_Agent4
    Is the hostname of the Agent 4 that acts as a gateway, for example, agent4.mycompany.com.
    -jmport port_number_of_Agent4
    This is the port through which this agent is contacted. The default is 31114. The valid range is from 1 to 65535.
    hostname_of_Agent4A
    Is the hostname of the Agent 4A that acts as a gateway, for example, agent4a.mycompany.com.
    -jmport port_number_of_Agent4A
    This is the port through which this agent is contacted. The default is 31114. The valid range is from 1 to 65535.
    Add an entry in the JobManagerGWURI property for each gateway you install.
  5. Start the agents acting as gateways by running the following command from the agent installation directory:
    ./StartUpLwa