Business overview
A company has a CICS® application that users access by using a CICS transaction. The system administrator needs to implement a small change to fix a bug in the application.
The company can use the CICS support for multi-versioning for applications deployed on platforms, and the CICS Explorer® interface, to make the update process simple and visual. The resources used by the scenario application are either supported as part of multi-versioned applications, or are handled in appropriate ways, so the application is eligible for multi-versioning.
The system administrator, or the application developer, uses CICS Explorer to package and export the new version of the application. The system administrator deploys the new version of the application to the platform, then enables the installed application. When the application goes into enabled status, the system administrator knows that the installation was successful. At this point, the older version of the application is still provided to users when they enter the CICS transaction. When the system administrator makes the new version of the application available, CICS immediately provides the users with that version in place of the older version. The users enter the same CICS transaction as before, and there is no need for the users to take any action.
If the system administrator becomes aware of a problem with the application version that contains the bug fix, they can revert quickly to the older version of the application. By default, CICS provides callers (such as CICS transactions or other linking applications) with the highest version of the application that you have made available on the platform. If the system administrator makes, or keeps, the older version available, and then makes the new version unavailable, users are automatically provided with the older version again. User access to applications is controlled by the application entry points that are declared for the resources in your applications, which can set the resources to be available or unavailable. The system administrator does not need to disable or discard alternative versions of the application to prevent users from accessing them.
In this scenario, because the older version of the application is defective, it is appropriate to disable or discard it after the new version has been verified. However, multiple versions of applications deployed on platforms can remain available concurrently to users. Programs coded to be aware of multi-versioning can access specific major and minor versions of an application by using the EXEC CICS INVOKE APPLICATION command. Alternatively, users can choose, or be directed to, different versions of a web application by using different URLs. For a scenario example showing multiple versions of an application available by design, see Hosting two versions of a CICS application concurrently on the same platform.