7.2

For more information about changing the default MSDTC ports, see the Microsoft Knowledge Base article
Conguring Microsoft Distributed Transaction Coordinator (DTC) to work through a rewall available at
hps://support.microsoft.com/en-us/kb/250367.
vRealize Automation supports SQL AlwaysON groups only with Microsoft SQL Server 2016. When
installing SQL Server 2016, the database must be created in 100 mode. If you use an older version of
Microsoft SQL Server, use a Failover Cluster instance with shared disks. For more information on
conguring SQL AlwaysOn groups with MSDTC, see hps://msdn.microsoft.com/en-
us/library/ms366279.aspx.
Data Collection Configuration
The default data collection seings provide a good starting point for most implementations. After deploying
to production, continue to monitor the performance of data collection to determine whether you must make
any adjustments.
Proxy Agents
For maximum performance, deploy agents in the same data center as the endpoint to which they are
associated. You can install additional agents to increase system throughput and concurrency. Distributed
deployments can have multiple agent servers that are distributed around the globe.
When agents are installed in the same data center as their associated endpoint, you can see an increase in
data collection performance of 200 percent, on average. The collection time measured includes only the time
spent transferring data between the proxy agent and the manager service. It does not include the time it
takes for the manager service to process the data.
For example, you currently deploy the product to a data center in Palo Alto and you have vSphere
endpoints in Palo Alto, Boston, and London. In this conguration, the vSphere proxy agents are deployed in
Palo Alto, Boston, and London for their respective endpoints. If instead, agents are deployed only in Palo
Alto, you might see a 200 percent increase in data collection time for Boston and London.
Distributed Execution Manager Configuration
In general, locate distributed execution managers (DEMs) as close as possible to the model manager host.
The DEM Orchestrator must have strong network connectivity to the model manager at all times. Create
two DEM Orchestrator instances, one for failover, and two DEM Worker instances in your primary data
center.
If a DEM Worker instance must run a location-specic workow, install the instance in that location.
Assign skills to the relevant workows and DEMs so that those workows are always run by DEMs in the
correct location. For information about assigning skills to workows and DEMs by using the
vRealize Automation designer console, see the vRealize Automation Extensibility documentation. Because
this function is advanced, you must design your solution so that WAN communication is not required
between the running DEM and remote services, for example, vRealize Orchestrator.
For the best performance, install DEMs and agents on separate machines. For additional information about
installing vRealize Automation agents, see the vRealize Automation Installing vRealize Automation 7.2
documentation.
vRealize Orchestrator
Use the internal vRealize Orchestrator instance for all new deployments. If necessary, legacy deployments
can continue to use an external vRealize Orchestrator. See
hps://kb.vmware.com/selfservice/microsites/search.do?
language=en_US&cmd=displayKC&externalId=2147109 for the procedure to increase the memory allocated
to the internal vRealize Orchestrator instance.
Reference Architecture
12 VMware, Inc.