6.2

Table Of Contents
Configuring Your Load Balancer
After you deploy the appliances for vRealize Automation, you can set up a load balancer to distribute
traffic among multiple instances of the vRealize Appliance.
The following list provides an overview of the general steps required to configure a load balancer for
vRealize Automation traffic:
1 Install your load balancer.
2 Enable session affinity, also known as sticky sessions.
3 Ensure that the timeout on the load balancer is at least 100 seconds.
4 If your network or load balancer requires it, import a certificate to your load balancer. For information
about trust relationships and certificates, see Certificate Trust Requirements in a Distributed
Deployment. For information about extracting certificates, see Extracting Certificates and Private
Keys
5 Configure the load balancer for vRealize Appliance traffic.
6 Configure the appliances for vRealize Automation. See Configuring Appliances for vRealize
Automation.
Note When you set up virtual appliances under the load balancer, do so only for virtual appliances that
have been configured for use with vRealize Automation. If unconfigured appliances are set up, you see
fault responses.
For information about scalability and high availability, see VMware vRealize Automation Reference
Architecture at https://www.vmware.com/support/pubs/vcac-pubs.html.
Configuring Appliances for vRealize Automation
After deploying your appliances and configuring load balancing, you configure the appliances for
vRealize Automation.
Configure the Identity Appliance
Configure the Identity Appliance to provide Single Sign-On (SSO) capability for the vRealize Appliance
environment.
You can use the Identity Appliance SSO provided with vRealize Automation or some versions of the SSO
provided with vSphere. For information about supported versions, see vRealize Automation Support
Matrix for this release available from https://www.vmware.com/support/pubs/vcac-pubs.html.
In vRealize Automation 6.2, Active Directory connections are handled by vSphere SSO, and most typical
deployments can use Active Directory 2003 or newer. Users should ensure that they are using vSphere
SSO 5.5b.
Installation and Configuration
VMware, Inc. 64