vRealize Automation supports managing resources in remote data centers.

To manage vSphere, HyperV, or Xen resources in remote data centers, deploy the proxy agent on a virtual machine in the remote data center.

Note:

The diagram below shows a vSphere deployment. Other endpoints require no additional configuration.

Because vRealize Orchestrator workflows will potentially communicate over a WAN, observe best practices as stated in the vRealize Orchestrator Coding Design Guide.

Table 1. Required Ports for WAN Communication

Role

Inbound Ports

Service/System Outbound Ports

vRealize Automation appliance - including embedded vRealize Orchestrator

N/A

vSphere endpoint: 443

ESXi Hosts: 903

vRealize Automation Infrastructure Load Balancer

vRealize Automation Infrastructure Proxy Agent: 443

N/A

vRealize Automation Infrastructure Web Server

N/A

vSphere endpoint: 443

vRealize Automation Infrastructure Manager Load Balancer

vRealize Automation Infrastructure Proxy Agent: 443

N/A

vRealize Automation Infrastructure DEM-worker Servers

N/A

Endpoint: **varies

* If DEM-workers are installed on the Manager Service machine or another server, these ports must be open between that machine and the target endpoint.

** The port required to a communicate with an external endpoint varies depending on the endpoint. By default for vSphere, this is port 443.

Figure 1. vRealize Automation Multi-Site Configuration