HCL Workload Automation on Amazon Web Services

Configuring a master domain manager

About this task

To instantiate and configure a master domain manager, complete the following steps:
  1. Navigate AWS Marketplace and search for HCL Workload Automation.
  2. Choose the AMI for HCL Workload Automation that better fits your needs.
  3. Click Launch instance.
  4. Customize the connection for your virtual server.
    When you launch an instance, you can choose between a private or a public IP address for your virtual server. By default, the dynamic agents will use a private IP connection to communicate with the master domain manager. As an alternative, you can specify to use the public IP or a custom public IP address for the agents to connect to the master. To specify to use the public IP or the custom public IP address, complete the following steps:
    To use the public IP
    In the User Data field available in the Advanced Details section, type the following:
    usePublicIP=true
    To specify a custom public IP to override the default public IP
    In the User Data field available in the Advanced Details section, type the following:
    usePublicIP=true
    myPublicIP=custom_public_IP_address
    where
    custom_public_IP_address
    is the IP address of your choice.
  5. Associate the virtual server to a security group containing the inbound firewall rules as described in the following table:
    Protocol Port
    ssl 22
    https 443
    If you choose a public IP address for your virtual server, the following inbound firewall rule must be added to the security group associated to the virtual server:
    Protocol Port
    https 16316
  6. As soon as you have instantiated the virtual server, an automatic configuration process starts. The configuration step sets the passwords of all users to the same instance ID value of the just created instance. The configuration might require some time to complete. To ensure that the process has completed, check that the last line in the //images/Infrastructure/Utilities/postconfigscripts/reconfig.log file reads:
    I: Configuration completed; removing status file.
  7. To connect to the operating system, use SSH key authentication and the user name ec2-user, providing the keypair specified during the order. For example:
    $ ssh -i ~/.ssh/my_aws_private_key ec2-user@hostname-of-my-wa-ec2
  8. After you are logged into the machine, use the sudo command to become the waadmin user. For example:
    $ sudo -u waadmin bash
  9. If you launched the Full Stack AMI, no further configuration step is needed. The master domain manager is up and running.

    If you launched the AMI with remote Oracle database, you have to complete the configuration steps described in : Configuring your environment for Oracle

    If you launched the AMI with remote Informix database, you have to complete the configuration steps described in : Configuring your environment for Informix

The following workstations are created:
WA_MDM
Is the master domain manager.
WA_AGT
Is the dynamic agent installed on the master domain manager.
MASTERAGENTS
Is a pool including the internal dynamic agent used for the new file condition based scheduling.

The FINAL job stream has been created, and no plan has been generated yet.

What to do next

The waadmin user can stop and start the instance without specifying a password. Use the following service commands to stop and start all HCL Workload Automation on AWS components, as follows:
service hwamdm start | stop
Starts or stops the master domain manager and the agent on the master domain manager.
service hwadwc start | stop
Starts or stops the Dynamic Workload Console.
service hwadb start | stop
Starts or stops DB2.
service ihs start | stop
Starts or stops IBM HTTP Server.
Log in to the Dynamic Workload Console at the link listed below using waadmin credentials to log in as administrator:
https://<instance_IP_address>/hcl/console 
where
instance_IP_address
Is the IP address or host name of the workstation where the Dynamic Workload Console is installed.
The following users are created automatically in the Dynamic Workload Console:
waadmin
Operating system user for the HCL Workload Automation administrator
waoper
Operating system user for using the workload monitoring feature and dashboards
wadevel
Operating system user for using the Workload Design.
warep
Operating system user for using the reporting feature.

After configuring the master domain manager, optionally configure the backup domain manager, and download and install dynamic agents, as described in Installing, updating, and uninstalling agents.

You can also optionally install your own SSL certificates. By default, different self-signed certificates are automatically generated for each HCL Workload Automation on AWS instance. For more information about installing custom SSL certificates, see Configuring custom certificates.