The system generates deployment execution plans based on the application blueprint. You can review the execution plan and add custom tasks to perform additional customized tasks in the application deployment before deploying the application.

The blue dotted lines in the execution plan define a specific order in which the deployment tasks run.

Host and agent bootstrap provisioning tasks appear next to components for each node. For applications deployed to the vCloud Automation Center environment, in addition to the host and agent bootstrap tasks, the network bootstrap provisioning task appears. These provisioning tasks display the processes that take place before the agent performs the installation and setup tasks for each component. When a deployment fails, you can see the provisioning task logs to troubleshoot the problem. You cannot add custom tasks between host, agent bootstrap, or network bootstrap provisioning tasks in an execution deployment plan.

If an application includes external services that require scripts to run, temporary virtual machines appear in the execution plan. Application Services removes these virtual machines after scripts run successfully in the host and agent bootstrap provisioning tasks. If the application fails before the temporary virtual machines are removed, you must identify the nodes that include the external services virtual machines and remove them from your cloud environment.

A blueprint helps to generate a common execution plan for an application on all of the deployment environments. Sometimes, you must customize the execution plan for each deployment environment. For example, when an application is deployed to the production deployment environment, you might need to send an email after deploying. In the test deployment environment, such checks might not be required. You can create an email custom task to send a notification email when the deployment task for a service or application component successfully finishes. You can add this task to the execution plan in the deployment profile, which deploys to the production deployment environment.

Caution

Verify that no processes are prompting for user interaction when the custom task is running. Any interruption pauses the task, causing it to remain in an idle state indefinitely. You can cancel the application deployment after an hour or Application Services fails the deployment in an idle state after three days.

Log in to Application Services as an application publisher and deployer.

Verify that at least one application is created in Application Services. See Creating Applications.

Verify that the Application Properties tab is configured. See Configure Application Properties.

Verify that at least one custom task is created in the Application Services catalog. See Add a Custom Task to the Library.

Verify that all of the required node properties in the application are assigned a value for successful deployment.

Depending on your cloud environment, you must have at least one vCloud Director or Amazon EC2 network available for the deployment environment. See Create a vCloud Director Deployment Environment or Create an Amazon EC2 Deployment Environment.

Familiarize yourself with the basic concepts of defining and configuring component properties and actions. See Developing Application Services Components.

1

Review the provisioning tasks, components, and dependencies in the execution plan.

2

Click the Expand Cluster button (Expand the clustered node) to expand the node, if the node is clustered.

If the clustered node is not expanded, the custom task is added only to the first virtual machine in the cluster. If an application architect modifies a node to a clustered node, an existing custom task is applied to only the first virtual machine in the cluster. A deployer should check during deployment whether the custom task applies to the first virtual machine or to all the virtual machines in the cluster, and perform the appropriate steps.

3

For services and components that have scripts associated with them, click the down arrow next to the component or service name to view the script or the variable definitions used in the script.

4

(Optional) Select the Add Script Task button (Add a script task) and drag the custom task to the node.

When you drag the Add Script Task button, you see anchors (Add Task anchor icon) that indicate where you can insert the custom task. For a clustered node, add the custom task to each node.

For example, you can drag one or more custom tasks to the Application Server, Database Server, or Load Balancer node.

After you drop a custom task to a node, the Add Custom Task dialog box opens.

5

(Optional) Select a task from the Library Task Name drop-down menu.

The custom task supported for that node's operating system appears. For example, if a custom task is supported on the CentOS 6.3 operating system and the operating system of the node is Ubuntu 12.4.2, the task is not listed in the menu.

When you select a custom task, the task, script, and property details appear in the dialog box.

6

(Optional) To override a property value on the Properties tab, click the property.

For example, in a send email custom task, one of the properties is the recipient's email address. You can set the property email address value to the recipient email address.

a

In the Edit Property dialog box, type the new value for the property or select an existing property from the drop-down menu to bind the property to one of the properties in the application blueprint.

b

Click Save.

7

(Optional) In the Add Custom Task dialog box, review the script and property details of the custom task, and click OK.

8

Click Next to review the deployment profile settings.

9

Click Save.

10

Click OK.

The deployment profile is listed for the application version.

Use the deployment profile to deploy the application. See Deploy with a Single Deployment Profile.