7.4
Table Of Contents
- Reference Architecture
- Contents
- vRealize Automation Reference Architecture Guide
- Initial Deployment and Configuration Recommendations
- vRealize Automation Deployment
- vRealize Business for Cloud Deployment Considerations
- vRealize Automation Scalability
- vRealize Business for Cloud Scalability
- vRealize Automation High Availability Configuration Considerations
- vRealize Business for Cloud High Availability Considerations
- vRealize Automation Hardware Specifications and Capacity Maximums
- vRealize Automation Small Deployment Requirements
- vRealize Automation Medium Deployment Requirements
- vRealize Automation Large Deployment Requirements
- vRealize Automation Multi-Data Center Data Deployments
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. By
default, the installer places DEM Orchestrators alongside the Manager Service. 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-specific workflow, install the instance in that location.
Assign skills to the relevant workflows and DEMs so that those workflows are always run by DEMs in the
correct location. For information about assigning skills to workflows and DEMs by using the
vRealize Automation designer console, see the vRealize Automation Extensibility documentation.
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
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
https://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.
For best product performance, review and implement configuration guidelines described in the vRealize
Orchestrator Coding Design Guide prior to importing vRealize Orchestrator content into production
deployments.
Reference Architecture
VMware, Inc. 8