HCL Workload Automation, Version 9.4

Configuring for a DB2 database

Before you begin

In the case where DB2® on the master domain manager is using the DB2 JDBC Type 2 driver, and the Dynamic Workload Console from where you want to work with reports is on a workstation different from the master domain manager, there are a few configuration steps that you must perform on the Dynamic Workload Console workstation to enable a successful connection to the HCL Workload Automation engine.
  1. Install the DB2 client on the Dynamic Workload Console workstation.
  2. To connect the DB2 client to the server, run the following commands in this order:
    db2 catalog tcpip node <TWS_NODE_NAME> remote <TWS_HOST> server <TWS_SRVC_PORT>
    db2 attach to <TWS_NODE_NAME> user <TWS_ADMIN_USER> using "<TWS_ADMIN_PW>"
    db2 catalog db <TWS_DB> at node <TWS_NODE_NAME>
    where,
    <TWS_NODE_NAME>
    The node name, for example, TWS_ND.
    <TWS_HOST>
    The host name of the DB2 server workstation.
    <TWS_SRVC_PORT>
    The port number of the DB2 server workstation.
    <TWS_ADMIN_USER>
    The user name of the DB2 server user.
    <TWS_ADMIN_PW>
    The password of the DB2 server user.
    <TWS_DB>
    The HCL Workload Automation database name.
    An example might be:
    db2 catalog tcpip node TWS_ND remote nc125139.romelab.it.ibm.com server 50000
    db2 attach to TWS_ND user db2admin using "db2admin"
    db2 catalog db TWS at node TWS_ND
  3. Stop the Dynamic Workload Console WebSphere Application Server.
  4. Edit the setupCmdLine.sh script located in the path <JAZZSM_Profile>/bin/ by adding the following lines at the end of the script:
    LD_LIBRARY_PATH=$LD_LIBRARY_PATH:<DB2_CLIENT_HOME>/lib64; export LD_LIBRARY_PATH
    LIBPATH=$LIBPATH:<DB2_CLIENT_HOME>/lib64; export LIBPATH SHLIB_PATH=$SHLIB_PATH:
    <DB2_CLIENT_HOME>/lib64; export SHLIB_PATH
  5. Restart the Dynamic Workload Console.

About this task

For DB2, the IT administrator, or the HCL Workload Automation IT administrator, or both working together, do the following:
  1. Create an operating system user and specify a password.
  2. Launch the following script:
    <TWA_home>/TWS/dbtools/DB2/scripts/dbgrant.bat/.sh 
    		<ID_of_user_to_be_granted> 
    		<database_name> 
    		[<database_admin_user> <password>]
    where the variables are as follows:
    <TWA_home>
    The HCL Workload Automation instance directory
    <ID_of_user_to_be_granted>
    The ID of the user created in step 1, who is going to be granted the access to the reports
    <database_name>
    The name of the database, as created when the master domain manager was installed
    [<database_admin_user> <password>]
    The user ID and password of the database administration user. If you are running this command as the database administration user, you can omit these parameters.
  3. Log on to the Dynamic Workload Console.
  4. In the Portfolio, select Manage Engines. The Manage Engines panel is displayed.
  5. Select the engine you defined or create another engine. The Engine Connection properties panel is displayed.
  6. In Database Configuration for Reporting, do the following:
    1. Check Enable Reporting to enable the engine connection you selected to run reports.
    2. In Database User ID and Password, specify the database user and password that you authorized to access reports.