Updating applications deployed on platforms

When you make changes to the CICS® bundles for the components of an application, update the versions of the CICS bundles, the application, and the application binding, and deploy the new versions on the platform.

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.

If your application uses only these resources, you can install and make available multiple versions of the application at the same time, on the same platform. If your application uses resources that are not supported for multi-versioning, you must disable and discard the existing version of the application before you install a new version. Alternatively, consider renaming the resources that are not supported for multi-versioning, so that they do not conflict with the resources installed for previous versions of the application.

If you have to disable an application in order to install a new version, it is unavailable to users from the time when you make the previous version of the application unavailable in order to disable and discard the installed APPLCTN resource in the CICSplex, to the time when you install the new APPLDEF resource definition, enable the new version of the application, and make it available. Plan a suitable time when this can safely occur, or plan an alternative solution for users of the application during that time.

About this task

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 and is taken from the OSGi Alliance. Although it focuses on Java™ packages, you can use the same principles to apply to bundles in general.

Semantic versioning provides a way to increment the major, minor, or micro parts of a version to indicate the compatibility or incompatibility with previous versions of a bundle. For example, bug fixes might increment the micro part of the version, compatible changes increment the minor part of the version, and incompatible changes increment the major part of the version. For more information about semantic versioning, see the OSGi Alliance technical whitepaper Semantic Versioning.

You must apply a versioning policy to your CICS bundles, application bundles, and application bindings to deploy and manage updates in the CICS environment. You cannot use an existing version of an application bundle to install new versions of the CICS bundles for the application, and you cannot use an existing version of an application binding with a new version of an application bundle. You must update the versions of the application bundle and application binding whenever you update the CICS bundles for the application.

When you change the version of an application, according to the principles of semantic versioning, the new version should reflect the largest change in a CICS bundle that is included in the application. For example, you might change one CICS bundle for an application from Version 1.0.1 to Version 1.0.2, which is a micro version change, and change another CICS bundle for the application from Version 1.2.0 to Version 1.3.0, which is a minor version change. The application bundle that includes these two CICS bundles should therefore have a minor version change, so if the application was previously at Version 2.5.1, it should change to Version 2.6.0.

You use the CICS Explorer to update your CICS bundles, and to update the application and application binding. For detailed help about each step, see Working with bundles in the CICS Explorer product documentation and Working with applications in the CICS Explorer product documentation.

Procedure

  1. Use the bundle manifest editor in the CICS Explorer to edit the resources in the CICS bundles as required, and to increment the version number in the cics.xml file for each bundle that you modify. CICS Explorer only recognizes and exports changed CICS bundles when you increment the version number. If you want to rename any resources that are not supported for multi-versioning, so that you can install the new version of the application without disabling and discarding the previous version, rename them at this stage.
  2. Use the application descriptor editor in the CICS Explorer to update the application with the new versions of your modified CICS bundles, and to increment the version number for the application in the application.xml file for the application bundle.
  3. Either update the existing application binding to specify the new version of the application, or create a new application binding for the new version of the application. To update the existing application binding, use the application binding descriptor editor in the CICS Explorer to specify the new version of the application in the appbinding.xml file for the application binding bundle, and to increment the version number for the application binding. You can also use the application binding editor to change the deployment of the CICS bundles for the application into the region types in the platform.
  4. Export the new versions of the application bundle and the application binding bundle to the platform home directory in z/OS® UNIX. The new version number for the application is used as part of the name for the application directory, so the previous versions of the application bundle remain in the platform home directory. Any CICS bundles for which you did not increment the version number, that are already deployed to the platform home directory and installed in the CICSplex at the correct version, are not included in the export.
  5. Create a new APPLDEF resource definition with a new version number to point to the application directory for the new application version. You can create the APPLDEF resource definition during the export process. An installed APPLDEF resource definition represents a single version of the application, and it cannot be edited. You create a separate APPLDEF to manage each version of the application.
  6. If your application uses resources that are not supported for multi-versioning, use the Cloud Explorer view and the application descriptor editor in the CICS Explorer to locate, disable, and discard the installed APPLCTN resource that represents the previous version of the application. If your application uses only resources that are supported as part of multi-versioned applications, or you have renamed all the resources that are not supported for multi-versioning, you do not need to disable it, so skip this step to avoid an interruption in the service to users.
  7. Use the Cloud Explorer view and the online application editor in the CICS Explorer to install the new APPLDEF resource definition for the new version of the application, enable the application version, and verify the installation. CICSPlex® SM enables the CICS bundles in the CICS regions in the platform, but the application version is not yet available to callers through its application entry points.
  8. When you are ready to make the new application version available to users of the platform, use the Cloud Explorer view or the application descriptor editor to make the application version available. The application version is now available to callers through its application entry points.

Results

The new version of the application is deployed on the platform. The CICS bundles that are included in the new version of the application are installed in the appropriate CICS regions, and the resources that are defined inside the CICS bundles are dynamically created in the CICS regions.

When you make a new version of an application available, CICS allows callers to access the application version through the CICS resources that are declared as its application entry points. For applications that are supported for multi-versioning, if multiple versions are available, callers can either access the highest available application version, or use the EXEC CICS INVOKE APPLICATION command to specify any available application version. For more information about invoking a specific version of an application, see Invoking a multi-versioned application.

What to do next

For applications that are supported for multi-versioning, to temporarily or permanently remove any unwanted previous versions of an application from a platform, follow the procedure in Making unavailable, disabling, and discarding applications.



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