HCL Workload Automation on Amazon Web Services

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

Installation procedure for computers that reside 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.

This scenario describes your environment if you have a network with different zones, for example Zone A and Zone B, and in each zone at least one computer can connect to the master domain manager site, for example Agent 1 for Zone A and Agent 4 for Zone B. A zone identifies a part of your network in which all the computers can communicate with each other. This computer acts as a gateway in your network zone.

To configure your network, first install the agent, let's call it Agent 4, on the computers that can connect to the master domain manager. Then install the agent, let's call it Agent 5, on the computers than cannot connect to the master domain manager. Complete the following steps to install Agent 4 and Agent 5:

  1. Verify the supported operating systems and prerequisites.
  2. Before you start the installation, ensure that your computer meets the following requirements:
    Temporary disk space
    300 MB
    Installation directory space
    480 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, in this example, /WAAgent.
  5. Extract the agent installation files TWS94_IBM_I_AGENT.zip to the /WAAgent directory.
  6. On the computer on which you want to install the product, sign on as the QSECOFR user.
  7. Use the PASE shell or the AIXterm command to extract the package:
    Using PASE shell:
    1. Open the PASE shell.
    2. Run the command "CALL QP2TERM".
    3. Locate the folder where you downloaded the agent installation files and run the command:
      "unzip TWS94_IBM_I_AGENT.zip"
    4. Exit from the PASE shell.
    Using AIXterm command:
    1. Start the Xserver on your desktop.
    2. On the iSeries machine, open a QSH shell and export the display.
    3. In QSH shell, go to the directory /QopenSys and run the command "aixterm -sb".
    4. A pop-up window is displayed on your desktop. By Using this pop-up window, unzip the TWS94_IBM_I_AGENT.zip file.
  8. Change to the directory where you downloaded the agent installation files.
  9. To install the agents, run the appropriate command from the directory where you downloaded the agent installation files as described in the following table:
    Table 1. Agent installation command for computers in different network zones
    Agent Installation syntax
    Agent 4 ./installWAAgent.sh -new [-uname user_name] -gateway local -gwid gateway_site_label -acceptlicense yes
    Agent 5 ./installAWAgent.sh -new [-uname user_name] -gateway remote -gwhostname host_name_of_Agent4 -gwport jmport_number_Agent4 -jmport port_number -acceptlicense yes
    Where:
    -uname user_name
    The name of the user for which the agent is installed.
    -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.
    -gwid gateway_site_label
    This is a name that identifies your gateway site. This parameter is required when you have more than one zone. The default is GW1. The name must start with an alphabetic character or an underscore character (_), and it can contain only the following types of characters: alphabetic, numeric, underscores (_), hyphens (-), and periods (.). Gateways that have the same gateway_site_label 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, when you install Agent 4, you must ensure that you specify a gateway_site_label different from the one for Agent 1 in the other network zone. So, for example, -gwid Rome. If the -gwid option was not specified at the time of installation of Agent 1, then its gateway_site_label assumes the default value GW1.
    -gwhostname host_name_of_Agent4
    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 4.
    -gwport jmport_number_of_Agent4
    This corresponds to the jmport number of Agent 4.
    -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.
    -acceptlicense yes|no
    Specify whether or not to accept the License Agreement. If you specify no, the update exits without performing any action.
The agent is installed using port 31114. It is installed in the /opt/HCL/WA_user_name directory, if you logged in as the root user. It is installed in the home_dir/WA directory, if you logged in with a different login. Ensure that the directory permission of home_dir or of /opt/HCL, if it already exists, is set to 755. If you want to install the agent by customizing one or more default values, see UNIX, Linux, and IBM i command syntax and parameters. For example, if the 31114 port number is already in use, then the following message is issued:
AWSFAB374E JM port is already used in some other instance.
Please specify some other port value.
In this case, to install your agent you must specify an alternative port number in the range 1-65535 using the -jmport port_number parameter. For example, to install Agent 4, you must specify a port number in the range 1-65535 using the -jmport port_number parameter, and to install Agent 5, you must specify -gwport port_number where port_number is the jmport number of Agent 4. The following table describes the syntax to use to specify a different port number than the default port number assigned:
Table 2. Agent installation command for computers in different network zones and using a port number different from the default value
Agent Installation syntax
Agent 4 ./installWAAgent.sh -new [-uname user_name] -gateway local -gwid gateway_site_label -jmport port_number -acceptlicense yes
Agent 5 ./installWAAgent.sh -new [-uname user_name] -gateway remote -gwid gateway_site_label -gwhostname host_name_of_Agent4 -gwport jmport_number_Agent4 -jmport port_number -acceptlicense yes

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.

If you have a proxy installed in your environment, perform the following steps:
  1. In the directory where the agent was installed, locate the JobManagerGW.ini file. By default, the file is located in install_dir/TWS/ITA/cpa/config.
  2. Open the file in a text editor and browse to the [ITA] section.
  3. In the [ITA] section, add the following string:
    http_proxy = http://<PROXY_IP_ADDRESS>:<PROXY_PORT>
    where
    PROXY_IP_ADDRESS
    Is the proxy IP address
    PROXY_PORT
    Is the proxy port number
  4. From the agent installation directory, run the ShutDownLwa command.
  5. From the agent installation directory, run the StartUpLwa command.