Updating the application

Use the CICS Explorer® to update the resources for the application, then update and re-version the application bundle.

Before you begin

Ensure that all of the projects related to the application are present in your local workspace for CICS Explorer, including the platform project for the target platform. CICS Explorer requires the platform project in order to validate the application project and the application binding project.

To update an application, you need to edit the application project, and then the application binding project. If you do not have a versioned backup system that enables you to revert to a previous version of the projects, instead of editing the existing projects directly as described in these instructions, you might prefer to copy them to another project and then edit the new copies.

About this task

You use CICS Explorer to update your CICS® bundles, and to update the application and application binding. This scenario shows the update process that is described in Updating applications deployed on platforms. For detailed help about each step in the procedure, see Working with applications in the CICS Explorer product documentation.

You manage different versions of applications by using version control. Each CICS bundle, application bundle, and application binding has an ID and version information to uniquely identify it. The version uses major, minor, and micro identifiers, so you can indicate the significance of a change and manage the dependencies between bundles. This concept is called semantic versioning. For more details about semantic versioning, see Updating applications deployed on platforms.

Procedure

  1. In CICS Explorer, select Window > Open Perspective > Other, then select CICS Cloud and click OK to open the CICS Cloud perspective. The Project Explorer view, which is included in the CICS Cloud perspective, shows the projects in your local workspace.
  2. In the projects that contain the components of your application, make changes to the web page displayed by the application, which you can use to distinguish the new version of the application from the older version of the application. In the application used in the demonstration, in the OSGi bundle that contains the presentation logic, new information is added to the web page, and the web page style sheet is changed to display a different background image.
  3. For any OSGi web bundle project and OSGi application project where you made changes to resources, edit the bundle manifest file MANIFEST.MF or the application manifest file APPLICATION.MF to increment the version number for the bundle or application, and point to the new version of the web content. The manifest files are in the META-INF folder for the project. In the application used in the demonstration, the following changes are made:
    • In the bundle manifest file for the OSGi bundle that contains the presentation logic, the version number in the value of the Bundle-Version header is updated to 1.1.0. The value of the Web-ContextPath header is changed to /demo.liberty.appV1.1 to specify the new path for the new version of the application.
    • In the application manifest file for the OSGi application project that packages the presentation logic, the version number in the value of the Application-Version header is updated to 1.1.0. The version number for the OSGi bundle that contains the presentation logic, which is specified in the Application-Content header, is also updated to 1.1.0.
  4. Rename any changed OSGi application projects to indicate the new version of the application. In the CICS bundle projects that package the changed OSGi application projects, update the .ebabundle file to specify the new names of the OSGi application projects. The name for an OSGi application project is used to create the name of the enterprise bundle archive (EBA), which must be unique in the Liberty JVM server.
  5. For any CICS bundle project where you made updates to resources that are defined or packaged in the bundle, update the version number in the CICS bundle manifest file cics.xml. Expand the META-INF folder for the CICS bundle and double-click the cics.xml file to open it in the bundle manifest editor. Increment the minor version number for the CICS bundle, and save your changes. In the application used in the demonstration, the version number of the CICS bundle that contains the .ebabundle file for the new version of the application is changed to 1.1.0.
  6. Update the CICS application bundle that packages the application. Expand the META-INF folder for the application project, and double-click the application.xml file or the bundles.xml file to open the application editor.
    1. Remove the old versions of updated CICS bundles from the application bundle by selecting them and clicking Remove in the application editor. When you update the version number for a CICS bundle, CICS Explorer marks the old version with an error in the application descriptor editor.
    2. Include the new versions of updated CICS bundles in the application bundle by clicking Add in the application descriptor editor, and selecting the new versions of the CICS bundles from the list of CICS bundles that are available in your workspace.
    3. Use the Version field in the application descriptor editor to increment the minor version number for the application. Then save your changes.
    In the application used in the demonstration, the old version of the CICS bundle that contains the .ebabundle file with the presentation logic is removed from the application bundle, and the new version is added. The CICS bundle that contains the application logic is not updated. The version number of the application is changed to 1.1.0.

What to do next

Next, edit the application binding project, and the CICS bundle where the URIMAP resource for the application is defined, which is deployed with the application binding project. Updating the application binding explains how to do this.


update_app.html | Timestamp icon Last updated: Sunday, 4 June 2017