User roles and interactions
The topology scenario uses different roles to perform key tasks. The roles and their interactions are summarized here for the scenario tasks.
Although roles to develop the solution are listed, this scenario focuses on deploying a solution that creates a CICS® topology for an application and adds CICSPlex® SM.
Develop the solution
The following roles are involved in developing the software aspects of the solution:
- Software architect
- The software architect is responsible for dividing the required function between the components that make up a software solution. This person works with the specifications and standards used by existing IT systems, and determines where enhancements or new components must be written by the developer.
- Developer
- The developer is responsible for creating and testing the software components and linking them together. In some cases the developer might need information from the administrator; for example, if the developer must use an existing CICS transaction in the application. After the developer finishes creating the software components, the developer gives those components to the administrator for deployment.
Deploy the solution
The following roles are involved in deploying the solution for production use, by installing, configuring, and testing the components that provide the solution.
- System administrator
- The system administrator creates and configures the CICS regions that support the solution. The business might have a different administrator for each product, or one administrator might perform installation and configuration for all components. If the administrators are different they might need to exchange information. For example, in this scenario the database administrator must give the name of the database subsystem to the CICS system administrator. The system administrator also installs the application components given to them by the developer.
- Test implementer
- The test implementer runs the tests to validate the solution and to ensure that the solution is ready for production use. For example, can the solution be started, stopped, backed up, and recovered after a system failure, as well as being maintained?