7.0
Table Of Contents
- Reference Architecture
- Contents
- vRealize Automation Reference Architecture Guide
- Updated Information
- New Features in vRealize Automation Since Release 6.2
- Initial Deployment and Configuration Recommendations
- vRealize Automation Deployment
- vRealize Business Standard Edition Deployment Considerations
- vRealize Automation Scalability
- vRealize Business Standard Edition Scalability
- vRealize Automation High Availability Configuration Considerations
- vRealize Business Standard Edition High Availability Considerations
- vRealize Automation Hardware Specifications
- vRealize Automation Small Deployment Requirements
- vRealize Automation Medium Deployment Requirements
- vRealize Automation Large Deployment Requirements
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-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.
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.0 documentation.
vRealize Orchestrator
Use an external vCenter Orchestrator system for each tenant to enforce tenant isolation. If tenant
isolation is not a requirement, you can use the internal instance of vRealize Orchestrator
The internal vRealize Orchestrator instance is a good starting point for deployments. If the internal
instance cannot handle the required workload, VMware recommends use of an external
vRealize Orchestrator cluster.
Reference Architecture
VMware, Inc. 10