Home
Configuring
Configure your environment.
Configuring High Availability
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.

Configuring
Configure your environment.
- Configuring an agent
  In this topic you can find information about how to configure an agent.
- Configuring Orchestration CLI
  The extension for Orchestration CLI is bundled with the product. If required, you can download it as a stand-alone feature also.
- Managing Workload Security
  You can manage security settings in your environment both from the Orchestration CLI and the Dynamic Workload Console.
- Configuring the Dynamic Workload Console for Single Sign-On
  Configure the Dynamic Workload Console for Single Sign-On.
- Configuring High Availability
  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.
- Configuring a user registry
  In this topic you can find information about how to configure a user registry.
- Customizing your global settings
  Learn how to customize advanced settings of the Dynamic Workload Console.

Configuring High Availability

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.

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.

Note: The minimum number of replicas for each component must be set to 2. For more information, see: HCL Universal Orchestrator.

The High Availability cannot be configured using Apache Derby®.