Upgrading the database tables if you are using DB2

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

1. From the HCL Workload Automation eImage, locate the dblighttool directory and copy it to a path on the database server computer or on a remote computer.
2. Modify the upgradeDB2IWSDB.properties properties file located in the IWSDBUpgrade folder assigning values to the parameters as follows:

   Table 1. Properties for DB2 upgrade procedure

   Property	DB2
   COMPONENT_TYPE	TheHCL Workload Automation component to be upgraded: MDM, BKM, DDM or BDM. The default value is MDM.
   DB_NAME	The name of HCL Workload Automation database. The default value is TWS.
   DB_HOST_NAME	The host name or IP address of the DB2 server.
   DB_PORT	The port of the DB2 server. The default value is 50000.
   DB_ADMIN_USER	The database administrator user that creates the HCL Workload Automation schema objects on the DB2 server.
   DB_ADMIN_USER_PWD	The password of the database administrator user that creates the HCL Workload Automation schema objects on the DB2 server.
   DB_USER	The user that has been granted access to the HCL Workload Automation tables on the DB2 server. The default value is db2admin.
   DB_USER_PWD	N/A
   IWS_TS_NAME	The name of the tablespace for HCL Workload Automation data (default: TWS_DATA)
   IWS_LOG_TS_NAME	The name of the tablespace for the HCL Workload Automation log (default: TWS_LOG)
   IWS_PLAN_TS_NAME	The name of the tablespace for the HCL Workload Automation plan (default: TWS_PLAN)
   HOST_NAME	The host name of the HCL Workload Automation broker (no default).
   WAS_SEC_PORT	The HTTPS port of the HCL Workload Automation broker. The default value is 31116.
   UPGRADE_DB	Set to TRUE to automatically apply the generated SQL statements to upgrade the HCL Workload Automation database schema. Set to FALSE to manually apply the generated statements in the customSQL.sql file. The default value is TRUE.

3. Run the upgrade script located in the IWSDBUpgrade folder specifying the usage and all of the required parameters as follows:

   On Windows operating systems

   launchUpgradeIWSDB.bat JAVA_HOME_PATH DB_PATH PROPERTY_FILE

   For example,

   DB2

   launchUpgradeIWSDB.bat D:\TWS\JavaExt\jre\jre 
   D:\Program Files\IBM\SQLLIB\java 
   D:\IWSDBUpgrade\upgradeDB2IWSDB.properties

   On UNIX and Linux operating systems

   ./launchUpgradeIWSDB.sh JAVA_HOME_PATH DB_PATH PROPERTY_FILE

   For example,

   DB2

    ./launchUpgradeIWSDB.sh /opt/TWS/JavaExt/jre/jre 
   /home/db2inst1/sqllib/java 
   /IWSDBUpgrade/upgradeDB2IWSDB.properties

   Table 2. Upgrade script parameters

   Parameter	Description
   JAVA_HOME_PATH	The Java home directory, where the bin directory is present.
   DB_PATH	The fully qualified directory path to the JDBC driver JAR file that contains the JDBC driver class. Specify only the path and not the JAR file name.
   PROPERTY_FILE	The fully qualified name of the file that contains a number of properties, one on each line with an assigned value, that are required for the database upgrade: upgradeDB2IWSDB.properties

   The script creates an SQL file with all the statements needed to upgrade the HCL Workload Automation database schema to the latest version. The SQL file is named: IWSDBUpgrade/customSQL.sql.

   If the UPGRADE_DB parameter is set to TRUE, then the generated SQL statements are applied to the database automatically when the script is run.

   If UPGRADE_DB parameter is set to FALSE, then the SQL statements are generated but not applied to the database. You can inspect the generated customSQL.sql and when you are ready to apply them to the database, set the value of the UPGRADE_DB parameter to TRUE in the upgradeDB2IWSDB.properties/upgradeOracleIWSDB.properties file and then rerun the launchUpgradeIWSDB.bat/launchUpgradeIWSDB.sh script to regenerate the SQL statements and apply the SQL statements .