The delivered logical topology

The company integrates the insurance broker application by using web services to request information from the CICS application using SOAP over HTTP.

The delivered IT configuration includes several components that an administrator configures or uses, as shown in Figure 1.
Figure 1. Delivered logical topology
The diagram shows an application running in a CICS topology that is managed by CICSPlex SM. Business users interact with the application through a presentation layer in a terminal-owning region. An external client application also access the business logic in the application-owning region (AOR) using a web service request. The requests are processed by a pipeline in the AOR.
Client application
The client application is the web service requester application that is used by the insurance broker. It accesses customer and policy information using web services that are created from the WSDL that was generated from the CICS application. The client application sends SOAP messages over HTTP to CICS and handles the response from the CICS application.
Application-owning region (AOR)
The AOR contains the business logic for the application. The business logic is used to create a web service binding and WSDL. The region also contains the CICS resources for web services:
  • The TCPIPSERVICE resource allows inbound requests over HTTP on a specific port number.
  • The URIMAP resource directs an inbound request to the correct pipeline and web service.
  • The PIPELINE resource defines a pipeline that can handle web service requests. In this scenario, the CICS application is acting as a web service provider, so the pipeline configuration file conforms to the service provider schema and contains XML to handle inbound SOAP requests and return SOAP responses to the web service requester.
  • The WEBSERVICE resource defines the web service binding that CICS uses to transform the data from XML to the high-level language.
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®. Using this interface, the system administrator can define and manage the resources for the web services in the AOR.
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.
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.
The workload specification manages the requests from business users accessing the application from a 3270 interface. It does not manage the web service requests.


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