The application blueprint provides detailed control over installation dependencies, configuration changes, and editable scripts. vCloud Application Director generates execution plans from the blueprint, which you can revise and use to deploy applications on supported cloud environments.

You model and create an application in the blueprint canvas. On the left side of the blueprint canvas are the logical templates from the vCloud Application Director catalog. On the right is a list of the services available from the catalog and application components. You can select a logical template and drag it to center of the blueprint canvas to start modeling your application.

Save your changes frequently. The vCloud Application Director user interface session expires after 30 minutes of inactivity. If the session expires, any changes that were not saved are lost.

Verify that your user account has the ROLE_APP_ARCHITECT application architect role assigned to it.

Verify that at least one application version is created in vCloud Application Director. See Create an Application Version.


On the vCloud Application Director title bar, click the drop-down menu and select Applications.


Select an existing application and open an application version.


Click Create Blueprint to create an application blueprint.

The canvas for modeling the application blueprint appears.


Select and drag one or more logical templates to the canvas to create nodes.

For example, to create a three-tiered application, you might drag three items from the OS Templates list to the canvas, or drag one template from the OS Templates list, one item from the Database Servers list, and one from the Application Servers list. The names of the lists correspond to the tags associated with a template.


(Optional) Select one of the nodes on the canvas and change the name of the node on the Details tab below the blueprint.

The name of the blueprint node must meet the following naming conventions:

Limited to 15 characters.

If the node name contains a character other than a letter, digit, underscore, or hyphen, that character is replaced with a hyphen.

For example, for a three-tiered application, you might rename each of the three nodes as Application_Server, Database_Server, and Load_Balancer.


(Optional) Set a host name on the Details tab below the blueprint if you plan to deploy the application to vCloud Director or vCloud Automation Center.

This host name serves as an identifier for the virtual machine computer name in its network. If the host name text box is left blank, vCloud Application Director generates a host name with random characters.

The host name must meet the following naming conventions:

Limited to 15 characters.

Must begin with a letter.

Can contain a letter, digit, or hyphen, but cannot end with an hyphen.

Cannot have the same host name as another node in the application blueprint.

Can include a ${random} expression at the end of a host name to generate unique characters.

For example, an Apache${random} host name might generate characters such as Apache9INOIK3YT after an application is deployed. You can view the host name with unique characters from the deployment summary page.

For a clustered node, the host name cannot exceed 15 characters with the appended node array index. For example, a clustered node called AppServer has the host names of the virtual machines in the cluster as AppServer-1, AppServer-2, and so on.


(Optional) To change the default number of CPUs or amount of memory for a deployed virtual machine, select the relevant node on the canvas and edit the values on the Details tab below the blueprint.

The tabs that appear below the blueprint correspond to the node selected.

The CPU and memory values in the blueprint might not match the corresponding values in the virtual machines created in Amazon EC2. Because Amazon EC2 allows virtual machines with specific CPU and memory combinations, it uses the values you assign in a blueprint to determine the closest possible match.


Select and drag one or more services or application components to the nodes.

For example, you might drag the MySQL service onto a database server node, drag the JBoss service onto an application server node, and drag an Apache service onto the Load Balancer node.

If a service or application component is not compatible with a particular node, you cannot drop it on the node. For example, you can drag the application component called SQL SCRIPT onto a MySQL service, but you cannot drag the SQL SCRIPT component onto a JBoss service.

Compatibility restrictions are created when the catalog administrator sets the supported operating systems and components for a catalog service. The catalog administrator can also add to the list of operating systems and tags that are already available in the catalog. For example, the MySQL service in the catalog has the supported components listed as SQL SCRIPT. Only the SQL SCRIPT application component type can be added to the MySQL service.

In addition, MySQL service has the supported operating systems set to CentOS32 6.3.0, CentOS64 6.3.0, CentOS32 6.4.0, CentOS64 6.4.0, and Ubuntu32 12.4.2. The MySQL service can be added to logical templates that include one of the operating systems.


If any preinstalled services are added to a logical template after you create a blueprint, the new preinstalled services are not added to the node. In this case, you must recreate the node and add the preinstalled services.

You can add the application components SCRIPT and Other to a node or any service.


Click Save when you finish.

Configure the services and application components you added to the application blueprint. See Configure an Application Blueprint.