HCL Workload Automation, Version 9.4

Creating or upgrading the database schema if you are using DB2

To create or upgrade the HCL Workload Automation and the dynamic workload broker database tables if you are using DB2®.

Creating the database tables for DB2

To create the HCL Workload Automation and the dynamic workload broker database tables if you are using DB2, run the following procedures:
  1. Customize the properties file. See Customizing the properties file for DB2.
  2. Generate the SQL files. See Generating the SQL files for DB2.
  3. Create the SQL tables. See Running scripts to create or upgrade the SQL tables for DB2.
See Creating the database tables if you are using DB2 for the complete procedure.

Upgrading the database tables for DB2

A new method for upgrading the HCL Workload Automation and the dynamic workload broker database schema is provided for DB2. The update or upgrade can be performed manually before you install the product component or, using the Installation Manager wizard or silent installation, the schema is updated during the installation procedure.

If you typically update your database tables manually before updating the HCL Workload Automation components in your environment, then you can use this new method which includes a script that quickly generates the required SQL statements in an SQL file and optionally applies them directly to the database in a single step.

The advantages of this new update method are:
  • A single script that dynamically generates the SQL statements and applies them directly to the database. Optionally, you can configure the script to generate only and then apply them at a later time but before installing the product component.
  • The script can be run and rerun as many times as needed without any cleanup required between runs. For example, if for some reason a database object is corrupt, you can rerun the script to regenerate the SQL file and apply it.
  • This method eliminates the requirement of installing a DB2 client to update a database located on a remote DB2 server. The script works using the JDBC drivers and connecting directly to the database server minimizing the overhead in installing and maintaining a database client.
    Important: If you already use a DB2 client and want to take advantage of this new method and eliminate it, ensure that you do not change the location of your JDBC driver. If you change the location, then remember to change it also in the WebSphere® Application Server. If instead your WebSphere Application Server does not point to the JDBC driver, then you can proceed to uninstall your DB2 client.
  • Use this method as a standalone tool to check the consistency of the database schema. The database administrator can verify if the database schema has changed and repair any inconsistencies.
Upgrading the product components using either the Installation Manager wizard or the silent installation methods automatically upgrades the database tables using this same method.
Upgrading the database schema for DB2 using this method involves the following high-levels steps:
  1. Modify the upgradeDB2IWSDB.properties file assigning the appropriate values to the parameters.
  2. Run the launchUpgradeIWSDB.bat or the launchUpgradeIWSDB.sh script to generate and apply the SQL statements. Optionally, you can choose to only generate the statements and apply them later, but before installing the product component.
See Upgrading the database tables if you are using DB2 for the complete procedure.
Parent topic: Creating or upgrading the HCL Workload Automation database tables before installing or upgrading