Configuring High Availability

How to configure, change, and share your settings repository.

Performance can be highly improved by configuring multiple Dynamic Workload Console instances in a High Availability configuration, so as to have multiple console instances working at the same time and with the same repository settings.

The Dynamic Workload Console is set to be always in High Availability and a front-end Network Dispatcher must be set up to handle and distribute all incoming session requests.

If you use a Dynamic Workload Console in High Availability configuration, when you connect to a Dynamic Workload Console you are not actually connecting to a specific console but to a load balancer that dispatches and redirects the connections among the nodes in the configuration. Therefore, for example, if a node fails, new user sessions are directed to other active nodes in the configuration.

The High Availability cannot be configured using Apache Derby®

To implement this kind of configuration, the Administrator must ensure that the datasource.xml, located in the following path opt/wa/DWC/DWC_DATA/usr/servers/dwcServer/configDropins/overrides, has the same configuration on every Dynamic Workload Console in the cluster.

See An active-active high availability scenario for more information about an end-to-end high availability configuration using two load balancers, one between the Dynamic Workload Console server nodes and console instances, and a second one between the Dynamic Workload Consoleserver nodes and the master domain manager and backup master domain managers.

For more information about an end-to-end high availability configuration using two load balancers, one between the Dynamic Workload Console server nodes and console instances, and a second one between the Dynamic Workload Consoleserver nodes and the master domain manager and backup master domain managers, see the HCL Workload Automation: Administration Guide.