Business overview
Company A has a CICS® application that is presented to users through a browser interface as a web application, with the presentation logic hosted in a Liberty JVM server. The company wants to introduce a new version of the application, but to avoid disruption to the business, they do not want all of the users to move to the new version at the same time.
To manage the business impact of the new version of the application, Company A plans to train a selected subset of the existing users on the new version and ask them to switch over immediately, and also to introduce new hires to the new version in their induction training. The training for the new version of the application will then be rolled out over a period of time to the remaining users of the application. After training, the users will decide when they want to transition to using the new version of the application. When Company A judges that support for the older version of the application is no longer desirable, they will give appropriate warnings to the users who are still using the older version, then finally remove the availability of the older version.
In the past, to resource this process, Company A would have had to set up a new infrastructure of CICS regions to host the new version of the application. The infrastructure for the older version of the application would have had to be maintained during the process, even though there was a decreasing number of users. Company A would have incurred the costs for both sets of CICS regions throughout the migration process for the application.
Now, Company A can use the CICS support for multi-versioning for applications deployed on platforms to remove the requirement for additional infrastructure. The company can deploy and make available both versions of the application in the same CICS regions that are part of a platform. The users can choose, or be directed to, the new version or the older version of the application by using different URLs.
With both versions of the application available, the workload for both versions of the application is handled by the same set of CICS regions, regardless of the application version that each user selects. The older version of the application can therefore remain available at no additional cost, for as long as is needed to smooth the transition for the users, and to minimize the impact to the business. The older version of the application can even be reinstated very quickly on the platform if a user does require it after it has finally been made unavailable.