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 also sets up the Liberty JVM server, either packaging the resource in a CICS bundle for deployment with the platform, or installing the resource in each of the CICS regions that are part of the platform.
Java™ application developer
The Java application developer creates each version of the web application and packages it as an OSGi bundle. The developer might also package each version of the web application into a CICS bundle, 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 web 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 makes the new version of the application available at the time required by the business, and later, makes the original version of the application unavailable at the time required by the business.
User
The user accesses a suitable version of the web application using the appropriate URL, either directly or through an access method such as a mobile application or an on-screen button. Before training, the user uses the original version of the web application. They receive training using the new application version, and when they are ready to transition to the new version of the application, they switch to using the new URL. They can also temporarily revert to using the older version of the application at any time, until the company ends support for the older version.
Figure 1. User role interactions to deploy the solution
Image showing the CICS system programmer, Java application developer, system administrator, and user. The system programmer configures the platform, and configures a Liberty JVM server. The Java application developer creates the original version of the web application and packages the web application as an OSGi bundle. The Java application developer then creates a CICS bundle, application bundle, and application binding, to deploy on the platform configured by the system programmer. The Java application developer exports the original version of the application to the platform home directory, creating v1.0.0 of the application. Later, the Java application developer creates, packages and exports the new version of the application, creating v1.1.0 of the application. The system administrator deploys, enables, and makes available the original version of the application, v1.0.0, on the platform. Later, the system administrator deploys and enables the new version of the application, v1.1.0, on the platform. When requested, the system administrator makes the new version of the application available. When support ends, the system administrator makes the older version of the application unavailable. The user uses a URL to access the original version of the application after the system administrator has made it available. Later, the user receives training for the new version of the application, then uses a new URL to access the new version of the application.


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