HCL Workload Automation, Version 9.4

Setting up a High Availability configuration

You can configure multiple Dynamic Workload Console instances to share a DB2® database as a common repository instead of a local directory in a High Availability configuration of nodes.

Before you begin

Note: Exporting data from a Tivoli® Integrated Portal High Availability configuration directly to a Dashboard Application Services Hub High Availability configuration is not supported. You must migrate your Tivoli Integrated Portal environment to a Dashboard Application Services Hub environment and then enable a High Availability configuration in the new environment.
Restriction: To upgrade an existing High Availability configuration from Dashboard Application Services Hub Version 3.1 or later to a High Availability configuration in a Dashboard Application Services Hub Version 3.1.2 environment, you must first complete the steps described in Upgrading a Dashboard Application Services Hub Version 3.1.1 or earlier cluster.

If you are creating a High Availability configuration from an existing Dynamic Workload Console instance that contains custom data, ensure that you have exported its data before you begin to configure it for High Availability. After it is configured, you can import the data to one of the nodes in the new configuration.

Dynamic Workload Console is installed on a machine using the cell name designated for all console nodes within the High Availability configuration. Ensure you have installed and set up a network dispatcher (for example, IBM HTTP Server), DB2, and an LDAP as explained in Requirements.

Note: Dynamic Workload Console server must be configured using DB2 without SSL connection. If you want to configure SSL connection, you can enable it after having successfully enabled the High Availability configuration. For more information, see Enabling SSL for Dashboard Application Services HubServer.

About this task

To implement a High Availability configuration, follow the procedure:


  1. Ensure you have already created a DB2 database on the computer where DB2 is installed (see Creating databases), and completed the procedure to the change the Dynamic Workload Console settings repository from a local file repository to a settings repository on the database. This database is shared as a common repository for nodes that will be subsequently joined to the High Availability configuration. The database administrator must have the ability to create tables. To create a new database, see Creating databases. To use an existing database, see Changing settings repository.
  2. Check that you have the JDBC driver for DB2 on the computer where the Dynamic Workload Console is installed. The JDBC driver must be available at: JazzSM install_dir/lib/db2.
  3. Configure a data source in the WebSphere Application Server administrative console and for the Java™ Naming and Directory Interface (JNDI) name use jdbc/tipds. For information on configuring a data source in the WebSphere Application Server administrative console, see http://www-01.ibm.com/support/knowledgecenter/SSEQTP_8.5.5/com.ibm.websphere.base.doc/ae/tdat_ccrtpds.html.

    In relation to setting up a data source for a high availability configuration in Dashboard Application Services Hub, note the following points:

    • Create the ${DB2UNIVERSAL_JDBC_DRIVER_PATH} variable in the WebSphere Application Server administrative console.
      1. From the WebSphere Application Server console, expand Environment and select WebSphere variables.
      2. Click the DB2UNIVERSAL_JDBC_DRIVER_PATH variable from the list of variables in the right pane to edit the value.
      3. On the Configuration page, enter the path to the directory that contains the DB2 Universal JDBC Driver in the Value field.
      4. Click OK to save the changes.
    • When creating the new JDBC provider:
      • Create the JDBC provider and data source in the server scope where Dashboard Application Services Hub is deployed, for example, cells:JazzSMCell:nodes:JazzSMNode:servers:server1.
      • Select DB2 as the database type.
      • Select DB2 Universal JDBC Driver Provider as the provider type.
      • Select Connection pool data source as the implementation type.
      • In Step 2: Enter database class path information, provide the directory location for DB2 JAR archive files. For example:
        Class path:
        Example of a directory location for WebSphere Application Server ${DB2UNIVERSAL_JDBC_DRIVER_PATH} variable:
    • When creating a new data source:
      1. In the WebSphere Integrated Solutions Console, open Resources > JDBC > Data sources.
      2. Under Scope, select cells:JazzSMCell:nodes:JazzSMNode:servers:server1 and click New.
      3. In Step 1, enter the data source and JNDI names and then click Next:
        • Data source name: tipds.
        • JNDI name: jdbc/tipds.
      4. In Step 2, select the JDBC provider that you created, for example, DB2 Universal JDBC Driver Provider and click Next.
      5. In Step 3, enter the specific database properties for the data source:
        • Driver type: 4
        • Database name is the database created in DB2, for example, dashdb
      6. Check the CMP check box.
      7. Click Next.
      8. In Step 4, set up any necessary security aliases and then click Next. Select the DB2 administrator's authentication alias from the Component-managed authentication alias option.
      9. In Step 5, the summary of the new data source is provided. Click Finish.
      10. Click Save to save the changes.
      • Create the Global J2C authentication alias using a DB2 user ID that has permissions to create and modify database tables:
        1. In the WebSphere Integrated Solutions Console, open Resources > JDBC > Data sources.
        2. From the table, click the data source you just created. Click the link, do not just select the check box.
        3. Under Related Items, click JAAS - J2C authentication data.
        4. Click New and set the fields Alias, User ID (the database of the master domain manager), and the DB2 Password.
        5. Click Apply and Save.
        6. Again, open Resources > JDBC > Data sources and click your data source name.
        7. In Component-managed authentication alias, select the J2C authentication alias.
        8. In Mapping configuration alias select DefaultPrincipalMapping.
        9. Click Apply and Save.
  4. Stop and restart the Jazz for Service Management application server.
    1. In the JazzSM_WAS_Profile/bin directory, for a server named server1, run the following command:
      On Windows
      stopServer.bat server1
      On UNIX
      stopServer.sh server1
      Note: You are prompted to provide an administrator username and password.
    2. In the JazzSM_WAS_Profile/bin directory, for a server named server1, run the following command:
      On Windows
      startServer.bat server1
      On UNIX
      startServer.sh server1


The High Availability configuration is created and the Dynamic Workload Console node is joined to the configuration as the first node.

What to do next

Next, add (or join) additional nodes to the configuration.