Creating and populating the database

By default, the installation script is configured to install and use a Derby database. Alternatively, you can also choose to use any one of the supported databases.


This picture describes the steps required for installing the Dynamic Workload Console. You are at step 3, creating and populating the database.

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.

If you are using the default database Derby, you can skip this step. If you are using a database other than Derby, create and populate the database tables for the Dynamic Workload Console by following the procedure appropriate for your RDBMS:

Next, install the Dynamic Workload Console servers, as described in Dynamic Workload Console installation - dwcinst script.