With Application Services if an update process to modify a configuration fails or if the updated deployment has performance or availability problems, you can use the rollback feature to restore that update to the last successful state in the timeline.

About this task

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

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

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

  • 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.

  7. Review the modified clustered node and rollback script in the execution plan and click Next.

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

    Click the down arrow next to the configuration rollback script to view script details or the variable definitions used in the script.

  8. Review the changed and rollback to components in the update.

    The changed and rollback to properties are highlighted.

  9. Click Rollback.

Results

The rollback process reverts the deployment to the last successful state in the cloud.

What to do next

Review the status of the deployment from the deployment summary page. See Using the Deployment Summary Page.