A vApp is a container object composed of one or more component machines that can be provisioned and managed as a single entity.

vCloud Director vApps combine software-defined services when used with vCloud Automation Center to provide a single self-service portal for multiple provisioning platforms.

When you request a vApp from vCloud Automation Center, it provisions the vApp and its virtual machines in your organization's virtual data center. vCloud Automation Center manages the vApp as a parent and its virtual machines as children components in a similar manner to how it manages multi-machine services.

This relationship allows you to manage the vCloud Director vApp by managing the vCloud Automation Center vApp. You can also perform operations directly on the individual component machines. For example, you can power off the vApp in vCloud Director by using machine actions in vCloud Automation Center. If you destroy a vApp machine and its component machines in vCloud Automation Center, you destroy the corresponding vApp and its virtual machines in vCloud Director.

Tenant administrator or business group managers create vCloud Director vApp and vApp component blueprints. These blueprints specify the source vApp template from the vCloud Director endpoint or vCloud Air endpoint and define additional provisioning parameters to apply to the template. For example, additional storage volumes and capacity can be applied to a component blueprint which will be configured when the vApp virtual machine is provisioned in vCloud Director.

In vCloud Automation Center, a vApp is a container for its component machines and is not a machine itself. The vApp is not counted as a machine in reports or licensing. For reporting and license purposes, vApp component machines are treated like any machine that vCloud Automation Center manages.

For more information about vApps, see Foundations and Concepts.