Before configuring load balancers for vRealize Automation, perform these prerequisites.
NSX-V/T— Before you start an HA implementation of vRealize Automation, vRealize Orchestrator or Workspace ONE Access using NSX-V/T as a load balancer, ensure that your NSX-V/T topology is configured and that your version of NSX-V/T is supported. This document covers the load balancing aspect of an NSX-V/T configuration and assumes that NSX-V/T is configured and validated to work properly on the target environment and networks.
To verify that your version is supported, see the vRealize Automation Support Matrix for the current release.
- F5 BIG-IP LTM — Before you start an HA implementation of vRealize Automation, vRealize Orchestrator, or Workspace ONE Access using an F5 LTM load balancer, ensure that the load-balancer is installed and licensed and that the DNS server configuration is complete.
- NetScaler – Before you start an HA implementation of vRealize Automation, vRealize Orchestrator or Workspace ONE Access using the NetScaler load balancer, ensure that NetScaler is installed and has configured at least a Standard Edition license.
- Certificates– Request Certificate Authority (CA) signed certificate containing the load-balancer fully qualified domain name and the host names of the cluster nodes in the SubjectAltNames section. This configuration enables the load balancer to serve traffic without SSL errors.
- Identity provider – Starting with vRealize Automation 8.0, the preferred Identity Provider is Workspace ONE Access, which is external to the vRealize Automation Appliance.
For more information on installation and configuration, see vRealize Automation documentation on docs.vmware.com.
If necessary, external vRealize Orchestrator cluster can be configured to work with the vRealize Automation system. This can be done after the vRealize Automation system is up and running. However, a vRealize Automation Highly Available setup already includes an embedded vRealize Orchestrator cluster.