Creating and populating the database

Create the required databases before you begin the installation.

This picture describes the steps required for installing the master domain manager. You are now at step 3: creating and populating the HCL Workload Automation database

Before you start the installation, you must create and populate the database for both the master domain manager and the Dynamic Workload Console. If you are using the default database Derby for the Dynamic Workload Console, you can skip this step for the Dynamic Workload Console and perform only the master domain manager database procedure.

Note:

HCL Workload Automation supports Derby database in test environments only. Derby is not recommended in production environments because it is a lightweight database. In production environments, move to another supported database.

You can perform a typical database procedure, as described in the following scenarios, or you can customize the database parameters, as described in FAQ - Database customizations. Links to customization options which are specific for a single database, if any, are provided in the related scenario.

The procedure differs for each supported database, as listed below:
DB2
Oracle
Informix
OneDB
MSSQL
Azure SQL

A set of scripts and SQL files is provided for each database type to perform actions such as granting rights or reorganizing the database. These files are located in inst_dir/TWS/dbtools into a separate folder for each database type. To use these files, copy the relevant folder to the database server.

Note: If you create the schema on your own, ensure the COLLATE value is set appropriately. Consider the following examples:
DB2
db2 get db cfg for TWS | grep -i collating
The expected values are: 
Database collating sequence = IDENTITY 
Alternate collating sequence (ALT_COLLATE) =
MSSQL
select DATABASEPROPERTYEX('Your DB Name','collation')
The expected values is: 
Latin1_General_BIN2