Installing the Dynamic Workload Console servers

Procedure for installing two Dynamic Workload Console servers on two separate nodes.

About this task

This picture describes the steps required for installing the master domain manager. You are now at step 6: installing the Dynamic Workload Console
Note:

HCL Workload Automation supports Derby database in test environments only. Derby is not recommended in production environments because it is a lightweight database. In production environments, move to another supported database.

Procedure for installing the Dynamic Workload Console

About this task

In this scenario, the HCL Workload Automation administrator installs two Dynamic Workload Console instances on two separate workstations, sharing the same remote database. The HCL Workload Automation administrator performs the operations listed below on both workstations.

Certificates are now required when installing HCL Workload Automation. You can no longer install HCL Workload Automation without securing your environment with certificates.

The HCL Workload Automation administrator installs the Dynamic Workload Console. The following information is required:
Table 1. Required information
Command parameter Required information Provided in..
Database information
--rdbmstype database type Creating and populating the database
--dbhostname database hostname
--dbport database port
--dbname database name
--dbuser database user name
--dbpassword database password
Security information
sslkeysfolder name and path of the folder containing certificates Installing the master domain manager and backup master domain manager
sslpassword password for the certificates Installing the master domain manager and backup master domain manager
Open Liberty information
--wlpdir Open Liberty installation directory Installing Open Liberty

You can run the dwcinst command specifying a typical set of parameters. In this case, default values are used for all remaining parameters.

Default values are stored in the dwcinst.properties file, located in the root directory of the installation image.

If you need to modify any of the default values, edit the dwcinst.properties file, but do not modify the dwcinst.template file located in the same path.

In a typical installation scenario, it is recommended you install the Dynamic Workload Console as a non-root user on UNIX systems and as a local administrator on Windows systems.

This user is automatically created by the installation process in the Open Liberty repository. Ensure that the user has full access to the Open Liberty installation directory.

Before starting the Dynamic Workload Console installation, ensure the following steps have been completed:
  1. Installing Open Liberty on the workstations where you plan to install the Dynamic Workload Console
  2. Creating and populating the database
  3. Creating the HCL Workload Automation administrative user
  4. On UNIX operating systems, ensure that umask is set to 022. To verify that umask is set to the correct value, from a command prompt, run the umask command. If the value is different from 022, modify it by running the following command:
    umask 022
Note:
  • To prevent installation failures, ensure that the inst_dir parameter is different from the directory of the installation image.
  • Recent JVMs do not fully support use of non-ASCII characters with the -jar and -javaagent commands. Use only ASCII characters in your installation directory names and paths.

To install the Dynamic Workload Console, perform the following steps:

Procedure

Start the installation specifying a typical set of parameters:
On Windows operating systems
cscript dwcinst.vbs --acceptlicense yes --rdbmstype db_type
--user dwc_admin_user --password dwc_pwd --dbname db_name
--dbuser db_user --dbpassword db_pwd --dbhostname db_hostname
--dbport db_port --wlpdir Liberty_installation_dir\wlp
--sslkeysfolder certificate_files_path --sslpassword keystore_truststore_password
On UNIX operating systems
./dwcinst.sh --acceptlicense yes --rdbmstype db_type
--user dwc_admin_user --password dwc_pwd --dbname db_name
--dbuser db_user --dbpassword db_pwd --dbhostname db_hostname
--dbport db_port --wlpdir Liberty_installation_dir/wlp
--sslkeysfolder certificate_files_path --sslpassword keystore_truststore_password
where,
user dwc_admin_user
is the administrator of the Dynamic Workload Console. You can use this account to log in to the Dynamic Workload Console and manage your environment.
password dwc_pwd
is the password of the Dynamic Workload Console user.
On Windows operating systems
Supported characters for the password are alphanumeric, dash (-), underscore (_) characters, and ()|?*~+.@!^
On UNIX operating systems
Supported characters for the password are any alphanumeric, dash (-), underscore (_) characters, and ()|?=*~+..

Results

You have now successfully installed the Dynamic Workload Console.

For more information about all dwcinst parameters and default values, see Dynamic Workload Console installation - dwcinst script.

What to do next

You can now proceed to Installing agents.