When vRealize Operations Manager uses a HA enabled vRealize Automation 7.3 or earlier, only four objects can use a load balancer.

vRealize Automation now uses APIs to retrieve data to monitor vRealize Automation health. You need not install vRealize Automation nodes separately.

The four objects of the HA enabled vRealize Automation are:
  • vRealize Automation Server
  • vRealize Automation Manager Server
  • vRealize Orchestrator App Server
  • vRealize IaaS Web
The individual objects paths are.
  • /vcac
  • /vco
  • /WAPI/api/status
  • /VMPS2

User can access these objects individually in the Inventory Explorer and edit the object to enter the load balancer FQDN, IP address, port, and the path.

Note: For a distributed vRealize Automation application, you can enter the vRealize Automation virtual server FQDN in the vRA.fqdn text box to access vRealize Automation. You can access the objects in the Inventory Explorer and edit the object in the loadbalancer.hostname and hostname for vRealize Orchestrator App Server.
Figure 1. Editing an Object
When you have an external load balancer, then the FQDN, IP, and Port should be provided. The relationship of the load balancer with its respective objects is created under the same group. A load balancer resource is created and grouped against which the HTTP check is performed. This helps in collecting Availability, Response Time, and Response Code of the call. For the load balancer FQDN and IP, you have to provide the management IP of the load balancer.
Note: If you are using NSX for vSphere as a load balancer for a vRealize Automation component, provide the vCenter IP to a load balancer IP while configuring objects. For a third-party load balancer, you can provide the management pack IP address of the load balancer as it contains the management console.