Updating the application and application binding

Fix the bug, then use CICS Explorer® to update the LIBRARY resource definition and re-version the bundles that are used to package the application. In the application binding, specify deployment regions for the new version of the CICS bundle with the LIBRARY resource definition, and re-version the application binding.

Before you begin

Ensure that all 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 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. Fix the bug by changing the relevant program or programs for the application. Recompile the changed programs, and store the new versions of the programs in new PDS or PDSE data sets.
  2. 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.
  3. In the CICS bundle where the LIBRARY resource is defined, expand the META-INF folder and double-click the cics.xml file to open it in the bundle manifest editor.
  4. In the Defined Resources list on the Overview tab, double-click the name of the LIBRARY resource to open it in the library resource editor. Change the values for the data set names to point to your new PDS or PDSE data sets for the new versions of the programs, and save your changes.
    • You do not need to make any other changes to the LIBRARY resource, and you do not need to make any changes to the PROGRAM resource or to the declaration of the application entry point. CICS manages multiple instances of these resources for the different versions of the application.
    • You also do not need to make any changes to the TRANSACTION resource that runs the application programs, because it is referencing the same PROGRAM resource as before, and you deployed the TRANSACTION resource separately from the application. CICS automatically provides the appropriate version of the multi-versioned application when users enter the transaction.
  5. Return to the Overview tab of the bundle manifest editor, increment the micro 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 LIBRARY resource is changed to 1.0.1.
  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 version of the updated CICS bundle where the LIBRARY resource is defined, by selecting it and clicking Remove in the application descriptor 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 version of the updated CICS bundle in the application bundle, by clicking Add in the application descriptor editor, and selecting the new version of the CICS bundle where the LIBRARY resource is defined 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 micro version number for the application, to match the change that you made to the CICS bundle, according to the principles of semantic versioning. Then save your changes. In the application used in the demonstration, the application is changed to version 1.0.1.
  7. Update the application binding for the application. In the Project Explorer view, locate the application binding, expand the META-INF folder for the application binding project, and double-click the appbinding.xml, bundles.xml, or deployment.xml file to open the application binding editor.
    1. On the Overview tab of the application binding descriptor editor, click Browse by the application name, and select the new version of the application. In the application used in the demonstration, version 1.0.1 of the application is selected.
    2. On the Deployment tab, use the switch button to switch to working with the CICS bundles. Select the new version of the CICS bundle where the LIBRARY resource is defined, and select the appropriate region type where it is to be deployed. Cancel the selection of region type for the old version of that CICS bundle.
    3. When you have completed your updates to the application binding, use the Version field in the application binding editor to increment the micro version number for the application binding, then save your changes.


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