The delivered logical topology
The company adds a CICS® topology and CICSPlex® SM to scale the application. The application is split into logical parts and CICS dynamically routes the work between regions. The application can be logically managed by an administrator, even if it runs across multiple logical partitions on the z Systems™ server.

- Application structure
- The application is split into three layers:
- The business users interact with a presentation layer that resides in the terminal-owning region (TOR).
- The business logic processes the request from the business users in the application-owning region (AOR).
- The data access part of the application handles the updates to VSAM and DB2® and resides in the data-owning region (DOR).
CICS regions can assume one or more roles and it is best practice to split your applications in this way. By using this approach you can build resiliency and high availability into your system to avoid outages. You can also clone regions to scale the environment and improve performance or increase throughput. If one region has a problem or fails, CICSPlex SM can dynamically route work to another region. For more information about topologies, see .
- CICSplex and CICS system groups
- A CICSplex is a grouping of CICS regions
that is managed as a single entity. A CICSplex can optionally contain
logical groupings of the CICS regions;
for example, you can group your terminal-owning regions together,
your application-owning regions together, and your data-owning regions
together. This logical grouping is called a CICS system group.
The advantage of using system groups is that you can use a system group as a scope to update and add definitions to many CICS regions in one action. You can also use CICS system groups in workload specifications. The workload automatically picks up new CICS regions as they are added to the system group, meaning that you can scale your environment without having to update the associated workload specifications.
- Coupling facility
- The coupling facility contains the named counter server and temporary
storage queues. The named counter server is accessed by the application-owning
region. The temporary storage queues are shared between the application-owning
region and data-owning region. Any errors that occur in the application
are reported on the errors queue.
The advantage of using the coupling facility is that the logical grouping of application components can access the same queues and named counter, even if they are physically located in different logical partitions on the z Systems server.
- CMAS
- The CMAS is the management point for the CICSplex and connects to all the regions in the CICSplex. You can use the CMAS to add or remove CICS regions in the CICSplex, create resources in multiple regions in one action, and define workload management to route work efficiently between all the regions. The CMAS accesses a data repository that contains definitions for all the regions, the CICSplex, and the workload management specifications.
- WUI server
- The Web User Interface (WUI) server is a CICS region that system administrators can use to connect to the CMAS and manage the regions in the CICSplex. You can use the Web User Interface or you can use CMCI to connect from CICS Explorer®.
- Data repository
- The CICSPlex SM data repository contains all the definitions for the application, the CICS regions, and the CICSplex. The data repository also contains the workload specification that controls the dynamic routing between the CICS regions. The regions are connected using MRO because they are in the same sysplex. Because the workload specification defines how the regions are connected and work is routed, static connection definitions are not required in each CICS region.