6.2

15 Review the modified properties and actions in the update.
The dependent properties with defined update scripts are highlighted.
16 Click Update to deploy the updated application.
The update process deploys the scaled out update to the cloud.
What to do next
You can check the status of the deployment from the deployment summary page. See Using the
Deployment Summary Page.
Learn about the various processes that take place in the background when the deployed application is
updated in the cloud. See Understanding the Deployment and Update Process.
Initiate an Update Process to Scale In Deployments
With Application Services, you can create an update profile for an existing deployment to scale in clusters
of one or more nodes for example, to free unused resources and accommodate the changing load in the
scalable application. When you scale in a clustered node of a deployed application, you can configure
only the cluster size of the node that were modeled as clusters in the application blueprint.
During an update process to scale in a deployed application, based on the update settings, the update
script runs on the dependent components followed by the teardown action script to remove the nodes. In
a multitiered application, if a node depends on the scaled in clustered node, an update script must run on
the dependent node.
For example, in a deployed Clustered Dukes Bank App, you can scale in the appServer node to reduce
the load. During the update process, the update script runs on dependent load_balancer node. The
teardown action script removes the appServer_2 and appServer_3 nodes from the deployment. The
action script also calls the cloud provider API to remove the nodes from the cloud environment.
During scale-in, you can attach a custom task with a scaled-in node and perform the update. However,
when this scale-in update profile is reused, the node does not have any custom task associated with it.
This is because, during the first time scale-in, the custom task information is deleted along with the
scaled-in node. Hence it cannot be used for scale-in reuse.
You define the UPDATE and the TEARDOWN life cycle stage scripts for a dependent service or
application component during the initial application deployment. The update scripts run on dependent
nodes and the teardown scripts run on the scaled in nodes. You can also add or modify the update and
teardown script during the update process. When you configure the update or teardown script during the
update process, the script is saved for future deployments in the update profile.
Note You cannot modify the install, configure, or start scripts during an update process. You can
configure only the update and teardown script.
With REST APIs in Application Services, you can automate the scale in of a deployed application. See
Using Application Services REST APIs document.
Using Application Services
VMware, Inc. 200