vRealize Automation 7.0 and later includes several architectural changes that simplify configuration and deployment.

Architectural Changes

  • 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.

  • 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.

  • 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.

  • vRealize Application Services functionality has been merged into vRealize Automation. The vRealize Application Services appliance no longer exists.

Deployment Changes

  • vRealize Automation deployments require two less load balanced endpoints as there is no need to balance the appliance database and an external SSO provider.

  • 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.