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
New Features in
vRealize Automation Since
Release 6.2 1
vRealize Automation 7.0 and later includes several architectural changes that simplify configuration and
deployment.
Architectural Changes
n
The appliance database is now clustered automatically within the appliance. There is no longer any
need for an external database load balancer or DNS entry. Detection of the master database server is
handled internally within the appliance. Manual failover is still required and can be performed from the
Virtual Appliance Management Console.
n
The instance of vRealize Orchestrator is now clustered automatically within the appliance. In 7.0 and
later, you can use the instance of vRealize Orchestrator within the vRealize Automation appliances
when they are configured in a highly-available manner.
n
Authentication is now handled by an embedded instance of VMware Identity Manager, known as
Directories Management, within vRealize Automation. There is no longer a requirement to deploy an
Identity Appliance, vCenter SSO or Platform Services Controller.
n
vRealize Application Services functionality has been merged into vRealize Automation. The vRealize
Application Services appliance no longer exists.
Deployment Changes
n
vRealize Automation deployments require two less load balanced endpoints as there is no need to
balance the appliance database and an external SSO provider.
n
Four virtual machines can potentially be removed from the footprint for most deployments, though an
external vRealize Orchestrator instance is still recommended for some situations.
VMware, Inc.
6