You can initiate an update process to modify the configurations and code of existing services in a deployed application such as Tomcat and MYSQL, or application components such as WAR and SQL. When you modify the configurations of a deployed application, you can configure only the application property values.

About this task

After the initial deployment, if you modify existing application components or services or modify components that have dependent properties, an update script must run on all of the impacted and dependent components. You define the UPDATE and the ROLLBACK life cycle stage scripts for a service or application component during the initial application deployment or in the update process.

For example, in the Clustered Dukes Bank App, if you modify the db_port property of the MYSQL service, during the deployment update process the update script runs on the MYSQL service. The Dukes_Bank_App application component on the Appserver node also runs the update script because the db_port property is bound to the db_port property of MYSQL service.

Note:

You cannot modify the install, config, or start scripts during an update process. You can configure only the update or rollback script.

You can also initiate an update process to modify the configuration and code of services or application components from the command-line interface. See Deploying and Updating an Application Using CLI. With REST APIs in Application Services, you can automate the modification of configurations of a deployed application. See Using Application Services REST APIs document.

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.

  • If you plan to add a custom task, verify that at least one custom task is created in the Application Services library. See Add a Custom Task to the Library.

  • Verify that the initial deployment is successfully deployed to a cloud environment.

    You cannot start an update process to modify the configuration and code of an existing service from a failed deployment to scale a clustered node.

  • The deployed application must have at least one service property or application component property that is Overridable at Deployment.

Procedure

  1. On the Application Services title bar, click the drop-down menu and select Deployments.
  2. Select an application deployment that is successfully deployed.
  3. From the Operations drop-down menu in the toolbar, select Update.

    The Update Profiles page opens.

  4. Select Create Update Profile.

    The Update Profile dialog box opens.

  5. In the Update Type drop-down menu, select Configuration.
  6. Name the configuration update process, add a description, and click OK.

    In the description, you can add information about the changes included in this update.

  7. 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 an update script if one does not exist or modify an existing one.

  8. From the Service or Application Component tab, modify the applicable properties and update scripts.

    If the UPDATE and ROLLBACK life cycle stage are defined, then the scripts appear with the associated service or application component. You must create an update script for the changed and dependent 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.

    For example, in the Clustered Dukes Bank App if you change the db_password property in the initialize_db_script application component, the db_password property in the Dukes_Bank_App depends on the initialize_db_script application component. The update scripts run on both because initialize_db_script is the changed component and Dukes_Bank_App is the impacted component. The update script for Dukes_Bank_App runs on all of the nodes of the Appserver cluster.

  9. (Optional) : Select the Reboot check box if the agent must restart the virtual machine after the update script runs successfully and click Next.

    The update tasks of the changed and affected components appear in the execution plan. The original execution plan does not appear during an update process.

  10. (Optional) : Add an APPD_UPDATE_PROPS property in the update script to view a list of all the changed properties.

    The update script is not saved and it applies to that particular update process only. You cannot use APPD_UPDATE_PROPS as a property name or as a qualifier for a property name.

    For example, the sample MySQL service update script includes the APPD_UPDATE_PROPS property to update the database port and password.

  11. (Optional) : Add an APPD_PREV property in the update script to view the previous value of a property.

    The update script is not saved and it applies to that particular update process only. You cannot use APPD_PREV as a property name or as a qualifier for a property name.

    For example, the sample MySQL service update script includes the APPD_PREV property to view the value of the database password.

  12. (Optional) : Click the Expand Cluster button (Expand cluster) to expand the clustered node, select a custom task, and drag the task onto each node.

    If you modify a service property or an application component property on a clustered node, the changes are applied to all of the nodes. You can configure the task properties in the Add Custom Task dialog box and save your changes.

  13. Review the modified clustered node and update script in the update execution plan.

    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 update script to view script details or the variable definitions used in the script.

  14. Review the modified clustered node and update script in the rollback 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 update script to view script details or the variable definitions used in the script.

  15. Review the changed and impacted components in the update.

    The modified properties and dependent properties are highlighted.

  16. Click Update to deploy the modified configuration for the application.

Results

The update process deploys the configured deployment to the cloud.

What to do next

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

Learn about the processes that take place in the background when the deployed application is updated in the cloud. See Understanding the Deployment and Update Process.