Self-Service Catalog with DB2 in High Availability

Using DB2 instead of a local file as your settings repository allows you to use Self-Service Catalog in High Availability Configuration.

Performance can be highly improved by migrating the Dynamic Workload Console accessed by the Self-Service Catalog to High Availability Configuration, so as to have multiple console instances working at the same time as one console.

If the Self-Service Catalog app you are using is connected to a Dynamic Workload Console in High Availability configuration, all the user settings, including the Self-Service Catalog data, are stored in a DB2 repository. If you are connected to a Dynamic Workload Console in High Availability configuration using a load balancer, when you launch the Self-Service Catalog app, you are not connecting to a specific Dynamic Workload Console, but to a node in the High Availability configuration. Therefore, for example, if a node fails, new user sessions are directed to other active nodes in the configuration and this change is completely transparent to users.

If the Dynamic Workload Console repository was switched to DB2 before creating Self-Service Catalog objects, then from the Dynamic Workload Console navigation tree, click HCL Workload Automation > System Configuration > Manage Settings > Configure settings repository > Create SSC Tables to create Self-Service Catalog tables on DB2. If this is not done, an error message displays informing you that the system cannot connect to the Self-Service Catalog database, and you must ensure that the database connection data is correct in the Dynamic Workload Console.

For more information about how to configure the Dynamic Workload Console to use DB2 as a settings repository, see: Configuring High Availability, in the Mobile Applications User’s Guide.

For more information about High Availability configuration, see Configuring High Availability for Dynamic Workload Console in HCL Workload Automation Administration.