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, 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:

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: 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
  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. 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 ./installWAAgent.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
    • 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|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.