6.2

Table Of Contents
What to do next
Review the provisioning tasks and dependencies in the execution plan. See Review the Execution Plan
and Add Custom Tasks.
Review the Execution Plan and Add Custom Tasks
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 vRealize Automation 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.
Prerequisites
n
Log in to Application Services as an application publisher and deployer.
n
Verify that at least one application is created in Application Services. See Chapter 14 Creating
Applications.
n
Verify that the Application Properties tab is configured. See Configure Application Properties.
n
Verify that at least one custom task is created in the Application Services catalog. See Add a Custom
Task to the Library.
Using Application Services
VMware, Inc. 178