Creating the database for MSSQL for the master domain manager

Instructions for creating and populating the HCL Workload Automation database for MSSQL for the master domain manager

About this task

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

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.

You can run the configureDb command specifying a typical set of parameters. In this case, default values are used for all remaining parameters. By default, MSSQL authentication is used. To modify the authentication type, see How can I specify the authentication type when using an MSSQL database?.

For more information about all parameters and supported values of the configureDb command, see Database configuration - configureDB script.

Default values are stored in the configureDbMSSQL.properties file, located in image_location/TWS/interp_name.

If you need to modify any of the default values, edit the configureDbMSSQL.properties file, but do not modify the configureDbMSSQL.template file located in the same path.

Note: Only on Windows systems hosting an MSSQL database, the path hosting the tablespaces must be existing before you run the configureDb.vbs command.

To create the HCL Workload Automation database and schema, perform the following steps:

Procedure

  1. Only on Windows systems hosting an MSSQL database, create the path for hosting the following tablespaces, if the path is not already existing:
    • TWS_DATA
    • TWS_LOG
    • TWS_PLAN
  2. Only on Windows systems hosting an MSSQL database, specify the path for the tablespaces when running the configureDb.vbs command or when filling in the configureDbMSSQL.properties properties file with the following parameters:
    • --iwstspath
    • --iwslogtspath
    • --iwsplantspath

  3. On the server where you plan to install the master domain manager, extract the HCL Workload Automation package to a directory of your choice.
  4. Browse to image_location/TWS/interp_name.
  5. To populate the HCL Workload Automation database with typical settings, type the following command:
    On Windows operating systems
    cscript configureDb.vbs --rdbmstype MSSQL --dbname db_name 
    --dbhostname db_hostname --dbadminuser db_administrator 
    --dbadminuserpw db_administrator_password
     --iwstspath DATA_tablespace_path 
    --iwslogtspath LOG_tablespace_path
    --iwsplantspath PLAN_tablespace_path
    On UNIX operating systems
    ./configureDb.sh --rdbmstype MSSQL --dbname db_name 
    --dbhostname db_hostname --dbadminuser db_administrator 
    --dbadminuserpw DB_administrator_password
    --iwstspath DATA_tablespace_path 
    --iwslogtspath LOG_tablespace_path
    --iwsplantspath PLAN_tablespace_path
    where:
    --rdbmstype
    The database vendor.
    --dbhostname db_hostname
    The host name or IP address of database server.
    --dbport db_port
    The port of the database server.
    --dbname db_name
    The name of the HCL Workload Automation database.
    dbuser db_user
    The user to be granted access to the HCL Workload Automation tables on the database server.
    --dbadminuser db_admin_user
    The database administrator user that creates the HCL Workload Automation schema objects on the database server.
    --dbadminuserpw db_admin_password
    The password of the DB administrator user that creates the HCL Workload Automation schema objects on the database server.
    --iwstspath|-tp table_space
    The path of the tablespace for HCL Workload Automation data. This parameter is optional. The default value for all databases other than Oracle is:
    For all operating systems, except z/OS
    TWS_DATA
    For z/OS operating system
    TWSDATA
    Only on Windows systems hosting an MSSQL database, ensure the folder for the tablespace is already existing before running the configureDb command and specify the path using this parameter. Specify the path using forward slashes (/), for example: c:/<my_path>/TWS_DATA.
    --iwslogtspath|-lp log_path_table_space
    The path of the tablespace for HCL Workload Automation log. This parameter is optional. The default value for all databases other than Oracle is TWS_LOG. This parameter applies only to the server components. Only on Windows systems hosting an MSSQL database, ensure the folder for the tablespace is already existing before running the configureDb command and specify the path using this parameter. Specify the path using forward slashes (/), for example: c:/<my_path>/TWS_LOG.
    --iwsplantspath|-pp plan_path_table_space
    The path of the tablespace for HCL Workload Automation plan. This parameter is optional. The default value for all databases other than Oracle is TWS_PLAN. This parameter applies only to the server components.

    Only on Windows systems hosting an MSSQL database, ensure that the folder for the tablespace is already existing before running the configureDb command and specify the path using this parameter. Specify the path using forward slashes (/), for example: c:/<my_path>/TWS_PLAN.

    Note: The following parameters specified with the configureDb command are also required when installing the server components and their values must be the same:
    • rdbmstype
    • dbhostname
    • dbport
    • dbname
    • dbuser

Results

You have now successfully created and populated the HCL Workload Automation database.

You can now proceed to Creating and populating the database for MSSQL for the Dynamic Workload Console.