IBM Workload Automation & Workload Scheduler

Workload Automation leverages PostgreSQL as a back-end database for the Dynamic Workload Console. This guide outlines the necessary steps to create and populate the PostgreSQL database, ensuring a seamless setup for workload automation.

Prerequisites

Before proceeding, ensure the following tasks are completed:

• PostgreSQL is installed and configured to allow remote connections.
• A dedicated database user is created (do not use the default postgres administrator account).
• SSL configuration is set up if required (for UNIX-based systems).

Refer to the official PostgreSQL documentation for additional details on remote connections and user creation.

Step 1: Creating and Populating the Dynamic Workload Console Database

Extract and Navigate to Installation Directory

1. Extract the Dynamic Workload Console package to a directory of your choice.
2. Navigate to image_location/TWS/interp_name.

Run the ConfigureDB Command

Execute the following command based on your operating system to create and populate the database tables:

For Windows:

cscript configureDb.vbs --rdbmstype POSTGRESQL --dbhostname DB_hostname --dbport db_port --dbname db_name --dbuser db_user --dbadminuser DB_admin_user --dbadminuserpw DB_admin_pwd

For UNIX/Linux:

./configureDb.sh --rdbmstype POSTGRESQL --dbhostname DB_hostname --dbport db_port --dbname db_name --dbuser db_user  --dbadminuser DB_admin_user --dbadminuserpw DB_admin_pwd

Command Parameters:

• --rdbmstype: Database type (set to POSTGRESQL).
• --dbhostname: Hostname or IP address of the database server.
• --dbport: PostgreSQL database port.
• --dbname: Name of the Dynamic Workload Console database.
• --dbuser: Dedicated user created before running this command.
• --dbadminuser: Administrator user for schema creation.
• --dbadminuserpw: Password for the administrator user.

Note: Ensure that the values used for --rdbmstype, --dbhostname, --dbport, --dbname, and --dbuser remain consistent during both database setup and Dynamic Workload Console installation.

Step 2: Creating the Workload Scheduler Administrative User

The Workload Scheduler requires an administrative user (wauser) with full access to scheduling objects.

User Creation Considerations:

• Windows:
• If the user does not exist, it is automatically created during installation.
• Use domain_name\user_name for domain users.
• Use system_name\user_name for local users.
• UNIX/Linux:
• Create the user manually before installation.
• Ensure the user has a home directory and a valid group.
• Avoid group names containing / to prevent permission issues.
• Root or non-root installation methods are available.

For further details, refer to the Workload Scheduler user management documentation.

Step 3: Configuring PostgreSQL in SSL Mode (Optional)

If using PostgreSQL in SSL mode, follow these steps:

1. Create a directory to store SSL certificates.
2. Inside this directory, create a subfolder named additionalCAs.
3. Obtain the necessary certificates from the database administrator.
4. Store the certificates in .crt format within additionalCAs.
5. Run the configureDb script using the sslkeysfolder parameter:
6. ./configureDb.sh --rdbmstype POSTGRESQL --dbhostname DB_hostname --dbport db_port --dbname db_name --dbuser db_user --sslkeysfolder /path/to/certificate/folder

Final Steps

Once the database and administrative user setup is complete, proceed with installing the master domain manager and backup master domain manager to finalize your Workload Automation deployment.

For more details on database configurations and installation procedures, refer to IBM’s or HCL’s official documentation.

Following these steps ensures a robust and efficient setup of PostgreSQL as the back-end database for Workload Automation. Happy automating!