Typical installation scenario

Scenario for a fresh typical installation at the latest product version of HCL Workload Automation

This image describes the steps required for installing the full software stack for HCL Workload Automation: creating and populating the database, creating the wa user, installing Open Liberty, installing the master domain manager andbackup master domain manager, the Dynamic Workload Console servers, and the agents.
This scenario describes how to perform a fresh install at the latest product version of the full software stack for HCL Workload Automation, which consists of the following components and workstations:
  • One workstation for the database server which hosts both the master domain manager and Dynamic Workload Console databases.
  • One workstation for the master domain manager and the related Open Liberty.
  • One workstation for the backup master domain manager and the related Open Liberty. The master domain manager and backup master domain manager share the same database. This ensures the backup master domain manager has the latest data and can take over seamlessly, in case the master domain manager fails.
  • Two workstations for two Dynamic Workload Console installations, each of them with their related Open Liberty. The two Dynamic Workload Console instances share the same database.
  • A number of agents.

Typical HCL Workload Automation architecture describes how the HCL Workload Automation components listed above are usually installed.

Figure 1. Typical HCL Workload Automation architecture
architecture diagram displaying a server machine with two database instances, one for the MDM and BKMDM, and the other for two Dynamic Workload Console instances. It also displays a number of agents connected to the MDM. There are 4 Liberty application servers, one for the MDM, one for the BKM, and one each for the Dynamic Workload Console.

If you already have WebSphere Application Server Liberty Base installed, you can use it with HCL Workload Automation, otherwise you can install Open Liberty, as described below.

Starting from version 10.2.1, using certificates is mandatory when installing or upgrading the product. You can use the certman command to extract certificates from an existing keystore, generate new certificates from a new or existing CA, and much more. For more information, see Managing certificates using Certman

If you install the master domain manager on recent UNIX operating systems, you can use the OpenSSL 3.0.x libraries provided with the operating system. The list of UNIX operating systems whose libraries you can use is as follows:
  • Ubuntu 22
  • AIX 7.3
  • Red Hat 9

To ensure HCL Workload Automation uses these libraries, always launch the installation or upgrade procedure from a brand new shell. You can also check the OpenSSL library currently in use with the which openssl command and check the OpenSSL version with the openssl version command.

This release installs a new version of the file tws_env.sh (tws_env.cmd) and also creates a backup file named, tws_env.sh.bk (tws_env.cmd.bk), which are both saved to the TWA_HOME/TWS directory, where TWA_HOME is the HCL Workload Automation installation directory. After completing the installation, if you have modified the original version, merge the content of the new version with the content of the customized version to carry your customized content into the new version. When merging the two versions as described above, ensure you do not modify the paths to OpenSSL libraries.

You can now proceed to Installing Open Liberty.