MICRO FOCUS ONWEB FOR CICS Focus OnWeb for CICS (OWCICS) is a mainframe-resident SOA solution. It fully SOA enables existing CICS transactions (including ... DL/I and VSAM

  • View
    212

  • Download
    0

Embed Size (px)

Transcript

  • WHITE PAPER

    MICRO FOCUS ONWEB FOR CICSThe scalable, high-performance mainframe component of Micro Focus OnWeb

    Micro Focus OnWeb for CICS is a mainframe-resident SOA solution for CICS applications. It is fully integrated with Micro Focuss other solutions to ensure smooth transitions during various phases of Incremental SOA initiatives.

  • High Performance Mainframe Resident SOA Micro Focus OnWeb for CICS (OWCICS) is a mainframe-resident SOA solution. It fully SOA enables existing CICS transactions (including those implemented with CA-Ideal) as well as common mainframe data sources such as DB2, DL/I and VSAM. OWCICS is seamlessly integrated with Micro Focuss product suite, including Micro Focus OnWeb and Onweb Connectors to be used for leveraging assets currently residing on mainframe and other systems.

    OWCICS is designed to be the scalable, highperformance mainframe resident component in enterprise SOA initiatives.

    OWCICS permits the creation, deployment and invocation of standards-based Web services that represent existing CICS transactions and mainframe data sources. Web services created with OWCICS, per SOA precepts, are platform agnostic, and as such can be deployed on and invoked from any distributed platform whether it be Linux, Unix, Windows or mainframe.

    Most customers should work in phases when it comes to creating reusable services on core environments (see Micro Focus Incremental SOA Whitepaper). By working in phases, customers can prototype and test SOA schemes using the point-click-and-deploy Micro Focus OnWeb development offerings. This phased approach to SOA, however, is not a prerequisite and OWCICS can be used as a totally mainframe-centric, stand-alone solution. The high-level architecture of OWCICS is shown in figure 1.

    OWCICS is tightly integrated with IBMs CICS Transaction Server (TS) 1.3 (and greater) for z/OS (or OS/390). OWCICS can thus efficiently leverage the 3270 Bridge [TS 1.3], LINK3270 Bridge1 [TS 2.2 and greater], WebSphere MQ interface and the CICS Web Support features of CICS TS. Consequently all of the SOA enablement capabilities of OWCICS, including the mainframe-based Web server that locates and invokes OWCICS related Web services, are all achieved via software executing within CICS TS. This results in exceptional performance, scalability, resilience and security.

    OWCICS supports enhanced Multi-Region Operation (MRO) with CICS TS 2.2 (or greater). Thus transactions requiring the use of the LINK3270 Bridge mechanism do not all have to be located within the same CICS region.

    OWCICS supports both visual and non-visual CICS applications; i.e. those with a terminal interface for end user interactions as well as those designed purely for program-to-program communication. In the case of visual applications, developers can locate and capture transactions that are to be represented as Web services using the original CICS green screens displayed within an intuitive GUI IDE. This is the same IDE used by Micro Focus customers successfully since the late 1990s. The intuitive nature of the IDE allows customers to act like a user yet work like a developer. In the case of OWCICS, however, screens and transactions are not identified and represented using 3270 data stream [i.e. screen scraping] as with the non-mainframe Micro Focus OnWeb products. Refer to figure 2.

    OWCICS, given its tight integration with CICS TS, uses the native CICS data structures. Data fields are identified with the intrinsic CICS methodology, to represent and access all CICS transactions irrespective of whether they occur within a visual or non-visual application. This approach is optimal for high-volume production use but is not conducive to fast, flexible and economical SOA prototyping. A much more efficient approach is to use Micro Focus OnWebs screen scraping feature to very quickly produce a prototype service during the exploratory stage of SOA development phase.

    Once prototyped services involving CICS applications are ready for prime-time, mainframe customers can use OWCICS to create an ultra-efficient, CICSembedded solution for SOA.Oriented architecture under .NET or J2EE.

    Distinctive DifferentiatorsOWCICS differentiates itself from other mainframebased CICS SOA solutions in that it offers a synergistic combination of multiple features many of which are unique to OWCICS. They include:

    Variable granularity of transactions that can be captured to create a Web service. With OWCICS there are no limitations on the type of CICS transaction that can be made into a Web service. It is even possible to combine existing transactions to create new ones -- and do so, where necessary, by omitting some fields in the original transactions.

    Consistent, standardized support for all CICS applications [including those developed using CAIdeal] whether they are visual [BMS and non-BMS] or non-visual [i.e. so called COMMAREA applications].

    Ability to capture (and combine) transactions from visual CICS applications using either a drag-and-drop GUI IDE or intrinsic CICS data structures as used within BMS maps.

    WHITE PAPER | Micro Focus OnWeb for CICS

    IBM z/OS or OS/390

    DB2DL/IVSAMother

    IBM CICS Transaction Server 1.3[+]

    ONWEB FOR CICS

    HTTP MQ

    Appl. access

    LINK/EXCI

    Data access

    CICSAppls.

    OtherAppls.

    Multi-Region Operation with CICS TS 2.2 [+]

    IBM [or compatible]mainframe

    SOAWeb Services

    Invocation[SOAP or HTML/XML]

    SOAWeb Services

    Creation

    ProcessAutomation

    TCP/IP MQ

    WSDLdefinitions

    Web Services

    CICS WebSupport MQ

    BMS3270

    COMMAREA

    CA-Ideal

    Figure 1: General architecture of Micro Focus OnWeb for CICS

  • WHITE PAPER | Micro Focus OnWeb for CICS

    Latitude to create a Web service representing a new composite transaction, synthesized by merging multiple core transactions, using both the visual GUI and textual data structure definition mechanisms to identify the underlying transactions and pertinent data fields.

    Fully integrated support, via CICS TS, for mainframe security [e.g. RACF, ACF/2 etc.], client authentication and SSL-based, end-to-end transaction encryption.

    Web service request/response flow minimization that rationalizes and consolidates the existing request/response sequences required by CICS transactions via standard JavaScript.

    Hybrid Micro Focus OnWeb server configurations for SOA involving both OWCICS and Micro Focus OnWeb on other platforms including Micro Focus OnWeb for iSeries to give organizations options and flexibility when deploying and developing shared services.

    Option of quickly and easily prototyping SOA solutions using Micro Focus OnWeb, with screen scraping, on a non-mainframe platform and then graduating to OWCICS, exploiting the same GUI IDE, to realize the high-performance, production use implementation.

    Enhanced CICS Multi-Region Operation (MRO) with CICS TS 2.2 (or greater) to eliminate the restrictions that all transactions that wish to use the LINK3270 Bridge mechanism must reside within the same Application-Owning Region (AOR).

    Full support for guaranteed-delivery, asynchronous message interactions via WebSphere MQ for scenarios where customers wish to use MQ as the networking infrastructure for a SOA solution.

    SOA and Mainframe CICSSOA is about the reuse of existing software assets, using a run-time [i.e. service invocation via request/response] paradigm, to develop new enterprise applications. In this context of software asset reuse, CICS is tremendously important.

    Over the last 30 years enterprises around the world have invested well over 20 trillion dollars developing, enhancing and maintaining mainframe CICS applications! Each day, more than 30 million people use one or more CICS applications when using ATM machines, online banking, Internet stock trading or Web-based travel reservation systems. Thus on any given working day, CICS applications will process well over 30 billion transactions involving at least $1 trillion of financial dealings.

    With the repeated emphasis on the service aspect, it is often easy to forget that SOA is just the latest in a long-line of remote invocation, software component methodologies with the key here being remote invocation (as illustrated in figure 3). Thus with any SOA solution, the goal is not to recreate but to, in real time, reuse existing business logic residing within CICS applications.

    Any new mission-critical SOA application must be able to handle the same high-volumes of interactive traffic as the original core application. For instance lets take a new Web-based trading system, deployed in a SOA, which is expected to serve 40,000 concurrent users -- with response times not exceeding 2 seconds. In this case it would not be advisable to have the services, running the new SOA application deployed on a middle tier application server. Those types of applications need to run on scalable, highperformance mainframe resident SOA enablement mechanisms for CICS, such as OWCICS.

    OWCICS, as shown in figures 1 3, is a comprehensive, self-contained mainframe-centric SOA solution for CICS, one that is tightly integrated with CICS TS. It thus can meet the exacting

    OnWebDevelopment Tools& Object builder

    Identify & capture transactions visually ordefine them using CICS data structures.There is no screen-scraping inthis mode.

    Publish WSDL& Web Service

    IBM z/OS or OS/390

    DB2DL/IVSAMother

    IBM CICS Transaction Server 1.3[+]

    ONWEB FOR CICS

    HTTP MQ

    Appl. access

    LINK/EXCI

    Data access

    CICSAppls.

    OtherAppls.

    Multi-Region Operation with CICS TS 2.2 [+]

    ProcessAutomation

    WSDLdefinitions