Application Services uses the virtual cloud infrastructure features in vRealize Automation to deploy applications to the vSphere environment.

As part of the setup process, you must create custom vRealize Automation blueprints. A vRealize Automation blueprint includes specifications for provisioning virtual, cloud, or physical machines, that determine the machine attributes, how they are provisioned, and their policy and management settings. When you request a machine, you must select the blueprint from which the machine is created. vRealize Automation applies a set of custom properties defined in the build profile or in the blueprint to that requested machine. From the vRealize Automation interface, you can access the clone or linked clone blueprints and specify properties to override several properties in the vCenter Server template.


Application Services supports only the vRealize Automation virtual blueprint provisioning to vSphere.

In Application Services, you must register a cloud provider and template. When you register a cloud provider, you map a specific vRealize Automation blueprint in a business group to a cloud template in Application Services. This registration process makes this vRealize Automation blueprint available in the Application Services library. To deploy an application using this cloud template, you must map a cloud template to a logical template. You must then create a deployment environment and map this deployment environment to an applicable vRealize Automation reservation policy.

Familiarize yourself with the key concepts that relate to setting up and configuring a cloud environment for application provisioning. See Key Concepts.