Sharing a settings repository

How to share a settings repository on multiple Dynamic Workload Console instances.

Before you begin

To perform this task you need to have the TWSWEBUIAdministrator role.

About this task

User settings such as user preferences, saved tasks, and engine connections are stored in the settings repository, which by default is a local file. However, you can decide to have your settings repository on a database for all Dynamic Workload Console operations that involve user settings.

This can be useful, for example, for scalability purposes or to have multiple Dynamic Workload Console instances sharing the same user settings.

To use a database for your settings repository, you must configure the database settings, as described in the following procedure:


  1. Ensure that all the Dynamic Workload Console instances that will share the same settings repository, also use the same user registry.
  2. Ensure that one Dynamic Workload Console settings repository has been switched to database, as described in Switch repository to DB2.
  3. Specify this repository as the default one for all the other Dynamic Workload Console instances that must share it:
    1. From the HCL Workload Automation installation path, open the install_dir\wastools directory and run installTDWCDatasource wastool to create the data source, specifying the same database settings as in the first Dynamic Workload Console instance.
    2. Restart the Dynamic Workload Console.
    3. From the navigation toolbar, click System Configuration > Manage Settings.
    4. In the same panel, click Configure settings repository > Use database as settings repository to specify that settings must be saved in the database instead of a local file.
    5. In the Database connection properties section, specify the credentials required to connect to the database.
    6. Optionally, you can test the connection.
    7. Save the new configuration.


As a result, all user settings are saved in the database, shared by all the Dynamic Workload Console instances, and all the operations involving user settings are run using the settings in this repository.