HCL Workload Automation, Version 9.4

Configuring Dynamic Workload Console to use DB2

Configure Dynamic Workload Consoles to use a database as the settings repository, to have all the consoles share the same settings, thus providing high scalability and availability.

Before you begin

Make sure you have configured Dashboard Application Services Hub (Dynamic Workload Console) to work in High Availability mode and that you have the TWSWEBUIAdministrator role.

About this task

To configure Dynamic Workload Consoles to use and share a database as the settings repository, you must:
  1. Create a database for the Dynamic Workload Console. You can also use the same database created for Dashboard Application Services Hub 2.2, but it is recommended that you use a different one.
  2. Optionally, configure SSL connection between DB2 and the Dynamic Workload Console.
  3. If you have configured an SSL connection, you must also make it active on Dashboard Application Services Hub. See: Enabling SSL for Dashboard Application Services HubServer.
  4. Set up the connection between the database and the Dashboard Application Services Hub server. See: Creating datasource.
  5. Configure all the Dynamic Workload Console instances to share the same settings repository. See Sharing a settings repository.
  6. Optionally, if you want the Dynamic Workload Console to access the database repository with a user without database administrator privileges, you must change the user that updates the settings repository on DB2. See:Changing the Dynamic Workload Console user of DB repository or Changing the Dashboard Application Services Hub user of DB repository.
To create a database for the Dynamic Workload Console, perform the following procedure:

Procedure

  1. Open the DB2 control center, right-click All Databases, and select Create Database > Standard.
  2. In the Create Database Wizard, type the database name and click Finish to accept all the default options.