Creating and populating the database
Create the required databases before you begin the installation.
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.
Supported configurations: HCL Workload Automation supports direct customer use of the Apache Derby database in test environments only. The product does not support direct customer use of Apache Derby database in production environments. The product supports the use of Apache Derby only by internal application server components in production environments.
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.
- DB2
- Oracle
- Informix and 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.
- 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