HCL Workload Automation, Version 9.4

Joining a node to a High Availability configuration

You can configure a Dynamic Workload Console to join an existing High Availability configuration.

Before you begin

  1. If you are joining a stand-alone Dynamic Workload Console instance to a High Availability configuration, ensure that you first export all of its data. After you join it to the High Availability configuration, you can then import the previously exported data. Other nodes in the configuration must not contain any custom data and should effectively be new installed instances.
  2. Make sure that you have successfully enabled High Availability configuration by following the steps in Setting up a High Availability configuration.
  3. Make sure that Dynamic Workload Console is installed on the node using the same cell name that is designated for the configuration.
  4. Make sure that all console modules deployed to the High Availability configuration are already deployed on the node that you are joining to the configuration.
  5. Deploy any wires or transformations used by the nodes in the High Availability configuration.
  6. If the High Availability configuration is using any customization changes in consoleProperties.xml, copy these changes and this file to the same location on the node that you are joining to the configuration.
  7. Make sure that the node is configured to the same LDAP with the same user and group definitions as all the other nodes in the High Availability configuration.

About this task

The following parameters are used on the join option when a node is added:
  • -Dusername - specify the DB2 administrator's username
  • -Dpassword - specify the DB2 administrator's password
Perform the following procedure to join a node to the first node and for every node you want to add to the configuration:


  1. 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.
  2. 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.
  3. Stop and restart the server. For example, for a console server named server1, follow these steps:
    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


As a result, the console node is joined to the High Availability configuration.

What to do next

Next, add another node to the High Availability configuration, or if you have completed adding nodes, enable server-to-server trust to every other node in the configuration.

Depending on the Network Dispatcher that you use (for example, IBM HTTP Server) , you might have further updates to get session requests routed to the new node. For more information, refer to the documentation that is applicable to your Network Dispatcher.