6.2
Table Of Contents
- Using Application Services
- Contents
- Using Application Services
- Updated Information
- Introducing Application Services
- Install and Configure Application Services
- Installing Application Services
- Preparing to Install Application Services
- Start the Application Services Appliance
- Troubleshooting Problems Connecting to the Application Services Web Interface
- Unlock Your darwin_user Account
- Restart Application Services
- Configure Application Services to Use a Proxy for External URLs
- Register Application Services to vRealize Automation
- Upgrading Application Services
- Setting Up Users and Groups
- Using Tenants and Business Groups in Application Services
- Import Predefined Content to a Tenant
- Using the Application Services Web Interface
- Setting Up Application Provisioning for the Application Services Environment
- Virtual Machine Requirements for Creating vRealize Automation Custom Templates
- Creating Virtual Machine Templates in vRealize Automation
- Updating Existing Virtual Machine Templates in vRealize Automation
- Register the vRealize Automation Cloud Provider and Template
- Create a vRealize Automation Deployment Environment
- Setting Up Application Provisioning for the vCloud Director Environment
- Virtual Machine Requirements for Creating vCloud Director Custom Templates
- Creating Windows Virtual Machine Templates in vCloud Director
- Create Linux Virtual Machine Templates in vCloud Director
- Verify Cloud Template Configuration from the vCloud Director Catalog
- Updating Existing Virtual Machine Templates in vCloud Director
- Exporting Virtual Machine Templates with OVF Format
- Register the vCloud Director Cloud Provider and Template
- Create a vCloud Director Deployment Environment
- Setting Up Application Provisioning for the Amazon EC2 Environment
- Developing Application Services Components
- Managing the Application Services Library
- Creating Applications
- Working with Artifacts
- Deploying Applications
- Setting Up and Configuring a Deployment Profile
- Deploying with Deployment Profiles
- Publishing Deployment Profiles to the vCloud Automation Center Service Catalog
- Request a vRealize Automation Service Catalog Item
- Using the Deployment Summary Page
- Using the Composite Deployment Summary Page
- Understanding the Deployment and Update Process
- Understanding Deployment Failures
- Updating Application Deployments
- Initiate an Update Process to Scale Out Deployments
- Initiate an Update Process to Scale In Deployments
- Initiate an Update Process to Modify Configurations
- Use an Existing Update Profile
- Promote an Update Profile
- Rollback an Update Process
- Understanding Run Custom Task Update
- Troubleshoot Failed Update Process to Scale Deployments
- Troubleshoot Failed Update Process to Modify Configuration
- Deploying Predefined Library Components
- Managing Deployments
- View Deployment Task and Blueprint Details for an Application
- View Deployed VM Details and Execution Plan of an Application
- Start a Policy Scan
- Tear Down an Application from the Cloud
- Scale In Deployments from vCloud Automation Center
- Scale Out Deployments from vCloud Automation Center
- Tear Down an Application from vCloud Automation Center
- Delete an Application Deployment from Application Services
- Cancel a Deployment or an Update Process
- View Policy Compliance Summary
- Using the Application Services CLI
- Using the CLI Import and Export Functions
The rollback script runs on the components whose properties are changing and the other dependent
nodes. For example, in a deployed Clustered Dukes Bank App, when you modify the configuration of the
MySQL port number from 3306 to 3307, the rollback script runs on the mysql service and
dukes_bank_app component. If this update process failed, you can rollback the configuration update to
revert to the previous port value 3306. In the Rollback wizard, you can view the Current Value as 3307
and the Rollback to value as 3306. The rollback script runs on the mysql service and dukes_bank_app
component to complete the process.
You define the ROLLBACK life cycle stage script for a dependent service or application component during
the initial application deployment. You can also add or modify the rollback scripts when you rollback an
update process to modify a configuration.
Prerequisites
n
Log in to Application Services as an application publisher and deployer.
n
Familiarize yourself with the basic concepts of defining and configuring component properties and
actions. See Chapter 12 Developing Application Services Components.
n
Verify that the initial deployment is successfully deployed to a cloud environment.
Procedure
1 On the Application Services title bar, click the drop-down menu and select Deployments.
2 Select an application deployment to rollback to a previous successful state.
3 From the Operations drop-down menu in the toolbar, select Rollback.
4 Click the blueprint image to review the highlighted dependencies between services or application
components.
Note all of the dependent components so that you can create a rollback script if one does not exist or
modify an existing one.
5 From the Service or Application Component tab, modify the applicable properties and rollback
script.
If the ROLLBACK life cycle stage is defined, then the script appears with the associated service or
application component. You must create a rollback script for the changes and rollback to component.
In the case of a clustered node, if you modify a property of a service or an application component, the
changes are applied to all the nodes of the cluster.
If you update the configuration properties of a deployment that was triggered by a change in the
external service instance, you cannot rollback these updated properties.
6 (Optional) Select the Reboot check box if the agent must restart the virtual machine after the rollback
script runs successfully and click Next.
The rollback tasks of the changed and rollback to components appear in the execution plan. The
original execution plan does not appear during an rollback process.
Using Application Services
VMware, Inc. 209