Set Up a Load Balancer for Orchestrator Clustering › F5 Load Balancer Prerequisites

F5 Load Balancer Prerequisites

Each clustered Orchestrator needs load balancing. If you have an F5 load balancer, you can use it to balance the processing of operator requests or web services requests across clustered nodes of the target Orchestrator.

Before you install the first node of a clustered Domain Orchestrator or another clustered Orchestrator, prepare F5 to perform load balancing.

First, gather the following information:

• Identity of hosts or virtual servers where Orchestrator nodes will be deployed.
• Credentials to log in to the F5 interface.

Then, configure the following F5 elements so that the elements function with CA Process Automation.

1. Create an F5 node for each cluster node.

   For CA Process Automation, a node is any host or virtual server on which an Orchestrator cluster node is installed (or could be installed in the future).

2. Create an F5 pool for each CA Process Automation cluster.

   For CA Process Automation, each pool includes the Orchestrator cluster nodes that belong to the same clustered Orchestrator.

3. Create an F5 iRule for CA Process Automation.

   For CA Process Automation, an iRule routes operator requests that target the touchpoint of a clustered Orchestrator.

4. Create an F5 virtual server for CA Process Automation.

   F5 can have several virtual servers. CA Process Automation is set up as one of the virtual servers.

5. Configure F5 to use simplified communication with HTTPS.
6. Prepare the F5 Load Balancer for Communication Verification.
7. Enable sticky sessions on the F5 load balancer. Sticky sessions must be enabled on the F5 in order for it to work with a CA Process Automation cluster.