User roles and interactions

The scenario involves people in different roles, each performing key tasks. The roles and their interactions are summarized here for the scenario tasks.

Developing the solution

The following roles are involved in developing the software aspects of the solution:

System programmer
The system programmer sets up the platform where the application is deployed, using suitable CICS® regions. The system programmer might also create and install the TRANSACTION resource for the transaction that runs the application, and the data sets on z/OS® where the programs for the application are stored.
Application developer
The application developer creates each version of the application, providing the updated application programs in a different data set. The developer might also use CICS Explorer® to create or update the CICS bundle that contains the resources for the application, create or update an application bundle that includes all the components of the application, and create an application binding to deploy the application on the platform that the system programmer has configured. If the developer has packaged each version of the application, they might also export each version of the application to the platform home directory, ready for the system administrator to deploy to the platform.

Deploying the solution

The following roles are involved in deploying the solution, by installing, configuring, and testing the components that provide the solution:

System administrator
If the developer has not already packaged and exported the application, the system administrator packages each version of the web application into a CICS bundle, creates or updates an application bundle that includes all the components of the application, and exports each version of the application to the platform home directory. After exporting each version of the application, the system administrator deploys the application version to the platform, and enables the application version, in order to verify that the installation was successful. The system administrator then makes the new version of the application available to implement the bug fix, and can also roll back the change if a problem is discovered with the bug fix. When the update has been verified, the system administrator can remove users' access to the older, defective version of the application.
User
The user automatically accesses the highest available version of the application when they enter the CICS transaction at a CICS terminal. The system administrator, acting as the service provider, controls the version of the application that is provided to the end user at any point in time. The user does not experience any downtime during version changes, and does not need to be aware of the version changes.
Figure 1. User role interactions to deploy the solution
Image showing the CICS system programmer, application developer, system administrator, and user. The system programmer configures the platform, and creates a TRANSACTION resource and z/OS data sets. The application developer creates the original version of the application, and creates a CICS bundle, application bundle, and application binding, to deploy on the platform configured by the system programmer. The application developer exports the original version of the application to the platform home directory, creating v1.0.0 of the application. To implement the bug fix, the application developer creates, packages and exports the new version of the application, creating v1.0.1 of the application. The system administrator deploys, enables, and makes available the original version of the application, v1.0.0, on the platform. To implement the bug fix, the system administrator deploys and enables the new version of the application, v1.0.1, on the platform. When the update has been verified, the system administrator makes the older version of the application unavailable. The user initially enters a CICS transaction and gets the original version of the application. After the system administrator has made the new version of the application available, the user enters the CICS transaction and gets the new version of the application.


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