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 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. Then install the agent, let's call it Agent 5, on the computer 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 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 your 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. 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 cscript installWAAgent.vbs -new -uname user_name -password user_password -gateway local -gwid gateway_site_label -acceptlicense yes
    Agent 5 cscript installWAAgent.vbs -new -uname user_name -password user_password -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. Choose a valid user account ID for your operating system. The installation creates the user on your computer, if it does not exist.
    -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 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. The valid range is from 1 to 65535.
    -jmport port_number
    This corresponds to the port number of Agent 5 . 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.
By default the agent is installed in the%ProgramFiles%\HCL\WA_HWAuser directory by using the 31114 port. If the 31114 port is already in use you receive the following message:
AWSFAB374E JM port is already used in some other instance. 
Please specify some other port.

Since Agent 4 was probably installed using the default port number 31114, then to install the Agent 5, you must specify -gwport jmport_number_Agent4 and -jmport jmport_number assigning a value different from the one you used to install Agent 4.

The following table describes the syntax to use to specify a different port number than the default port number assigned:
Table 2. Installation syntax for agents in different network zones and using a port number different from the default value
Agent Installation syntax
Agent 4 cscript installWAAgent.vbs -new -uname user_name -password user_password -gateway local -gwid gateway_site_label -jmport port_number -acceptlicense yes
Agent 5 cscript installWAAgent.vbs -new -uname user_name -password user_password -gateway remote -gwid gateway_site_label -gwhostname host_name_of_Agent4 -gwport jmport_number_Agent4 -jmport port_number -acceptlicense yes

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

To customize any of the default installation settings, see Windows command syntax and parameters.

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.

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.