Cics Connectivity

6,118 views

Published on

Palestra do Latin America CICS Roadshow

Published in: Education, Technology
1 Comment
6 Likes
Statistics
Notes
  • I can't believe that working at Ibm , it is more easy for my download this information from here, Congratulations!
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
6,118
On SlideShare
0
From Embeds
0
Number of Embeds
62
Actions
Shares
0
Downloads
334
Comments
1
Likes
6
Embeds 0
No embeds

No notes for slide
  • Cics Connectivity

    1. 1. CICS Connectivity Strategic Integration Options Tom Grieve [email_address]
    2. 2. Introduction <ul><li>Many customers want to utilize both J2EE application servers and CICS as environments to run their business applications and need to understand how applications in the two environments can invoke each other, as well as how to provide the transactional and security characteristics which they require. This presentation will focus on interoperability for the two major players – CICS and WebSphere - and the technology involved to ensure interoperability </li></ul><ul><li>Agenda: </li></ul><ul><li>SOA and the role of CICS applications </li></ul><ul><li>CICS application architecture </li></ul><ul><li>Strategic CICS integration options </li></ul><ul><ul><li>Web services </li></ul></ul><ul><ul><li>JCA </li></ul></ul><ul><li>WebSphere Process Server and ESB solutions </li></ul><ul><li>Recommendations for integration </li></ul>
    3. 3. CICS and SOA is big ! Source: Arcati Limited
    4. 4. Applications are at the Heart of SOA <ul><li>App Development Tools </li></ul><ul><ul><li>Rational Developer for System z </li></ul></ul><ul><ul><li>Debug Tools </li></ul></ul><ul><li>App Runtime Containers </li></ul><ul><ul><li>CICS Transaction Server </li></ul></ul><ul><ul><li>TXSeries </li></ul></ul><ul><ul><li>CICS VSE </li></ul></ul><ul><li>Systems Management Tooling </li></ul><ul><ul><li>Tivoli OMEGAMON </li></ul></ul><ul><ul><li>CICSPlex SM </li></ul></ul><ul><ul><li>CICS Tools </li></ul></ul><ul><ul><li>PD Tools </li></ul></ul><ul><li>Modeling Tools </li></ul><ul><ul><li>CICS Service Flow Modeler </li></ul></ul><ul><li>App Development Tools </li></ul><ul><ul><li>Rational Developer for System z </li></ul></ul>Foundational Extend End-to-End Transform Adapt Dynamically
    5. 5. CICS SOA solutions must integrate with other Service providers <ul><li>Most SOA solutions are built out of multiple services, that access data and present it to end users </li></ul><ul><li>All of these can be found inside CICS, but more often CICS plays part of the SOA solution </li></ul>Connectivity Reuse Process People Information CICS Service Flow WebSphere Process Server CICS BMS or Web Browser WebSphere Portal Server CICS VSAM DB2 CICS ISC, CICS TG MQ and Message Broker WebSphere ESB DataPower CICS Native Web Sevices WebSphere Application Server Foundational Extend End-to-End Transform Adapt Dynamically
    6. 6. Web Services <ul><li>Architecture for </li></ul><ul><ul><li>Application to application </li></ul></ul><ul><ul><ul><li>Communication </li></ul></ul></ul><ul><ul><ul><li>Interoperation </li></ul></ul></ul><ul><li>Definition: </li></ul><ul><ul><li>Web Services are software components described via WSDL that are capable of being accessed via standard network protocols such as SOAP over HTTP </li></ul></ul><ul><li>WS-I.org (Web Services Interoperability Organization) </li></ul><ul><ul><li>Ensure interoperability </li></ul></ul>
    7. 7. CICS application architecture – a framework for reuse <ul><li>Best practice in CICS application design is to separate key elements of the application, in particular: </li></ul><ul><ul><li>Presentation logic eg. 3270, HTML, XML </li></ul></ul><ul><ul><li>Integration or aggregation logic Menu, router, tooling </li></ul></ul><ul><ul><li>Business logic Reusable component </li></ul></ul><ul><ul><li>Data access logic VSAM, DB2, IMS, … </li></ul></ul><ul><li>Provides a framework for reuse and facilitates separation of concerns, clear interfaces, ownership, and optimisation </li></ul>CICS Transaction Server Client 3270 Presentation Integration logic Data access Transaction D I P Business logic B
    8. 8. Connectivity to CICS programs <ul><li>Typical clients… </li></ul><ul><ul><li>Web service requester </li></ul></ul><ul><ul><li>Java servlet or EJB running in a J2EE app server </li></ul></ul><ul><ul><li>C# application running in a Microsoft .NET VM </li></ul></ul><ul><ul><li>Web browser </li></ul></ul><ul><ul><li>Messaging middleware </li></ul></ul><ul><li>Adapter can be </li></ul><ul><ul><li>External or Internal </li></ul></ul><ul><ul><li>Written or generated by tools </li></ul></ul>A CICS TS 3270 terminal D B P Transaction Client A I A
    9. 9. Two models for SOA integration of CICS applications <ul><li>Service end-point in front-end system </li></ul><ul><ul><li>Utilizing strategic connectors between front-end and CICS (EIS) </li></ul></ul><ul><li>Service end-point in CICS </li></ul><ul><ul><li>Utilizing Web Services support in CICS </li></ul></ul><ul><ul><li>SOAP over HTTP or SOAP over MQ </li></ul></ul><ul><li>Multiple choices for interoperability </li></ul><ul><ul><li>WebSphere Application Server </li></ul></ul><ul><ul><li>WebSphere Message Broker </li></ul></ul><ul><ul><li>WebSphere Process Server and WebSphere ESB </li></ul></ul><ul><ul><li>WebSphere Datapower </li></ul></ul>
    10. 10. Two models of CICS SOA integration CICS TS Web service Client CICS Program Business logic B Requester connector Web services end-point Service Provider D Integration logic I SOAP CICS TS Web service Client CICS Web services support Integration logic Data access Business Function D I Business logic B Requester (Service Provider) SOAP A A
    11. 11. Factors Influencing your Integration Choices <ul><li>Business factors </li></ul><ul><ul><li>Agreed company standard or reference frameworks </li></ul></ul><ul><ul><li>Preferred application development environment and tools </li></ul></ul><ul><ul><li>Availability of skills </li></ul></ul><ul><li>Technical factors </li></ul><ul><ul><li>Security </li></ul></ul><ul><ul><li>Transactional scope </li></ul></ul><ul><ul><li>Performance </li></ul></ul><ul><ul><li>Reliability, availability and scalability (RAS) </li></ul></ul><ul><ul><li>Application interface consumability </li></ul></ul><ul><ul><li>Synchronous or asynchronous invocation </li></ul></ul><ul><ul><li>Inbound and outbound capability </li></ul></ul><ul><ul><li>Client/server coupling </li></ul></ul><ul><ul><li>Data conversion </li></ul></ul><ul><ul><li>State management </li></ul></ul><ul><li>Applications today are typically delivered across several e-business clients </li></ul>
    12. 12. Reusing 3270 presentation logic – Link3270 bridge <ul><li>Some programs combine presentation, integration, and business logic </li></ul><ul><li>Link3270 Bridge provides a COMMAREA interface to BMS and terminal-oriented programs </li></ul><ul><ul><li>ADS information in the COMMAREA is passed to the BMS application </li></ul></ul><ul><ul><li>Does not use VTAM or screen scraping </li></ul></ul><ul><ul><li>No changes required to existing BMS application </li></ul></ul>CICS TS 3270 terminal D I/B P Transaction I/B P Client Link3270 Bridge
    13. 13. Reusing 3270 presentation logic – HATS <ul><li>HATS provides an integrated approach to screen driven re-use </li></ul><ul><ul><li>Builds on Host Integration telnet/3270 technology (HOD/HACL) </li></ul></ul><ul><ul><li>Provides for screen transformation and programmatic reuse </li></ul></ul><ul><ul><li>Programmatic reuse via WD4Z tooling and Service Flow Modeller </li></ul></ul>CICS TS 3270 terminal D I/B P Transaction A WebSphere App Server Client
    14. 14. Service Flow Modeller <ul><li>Tool is part of WD4Z </li></ul><ul><li>Can graphically choreograph 3270 transactions and/or COMMAREA based programs into callable COMMAREA programs </li></ul><ul><li>Can generate artifacts necessary to expose the choreography as a Web Service in CICS </li></ul><ul><li>High productivity </li></ul>
    15. 15. Integration with CICS - Strategic options <ul><li>Standard architectures </li></ul><ul><ul><ul><li>Web services over SOAP </li></ul></ul></ul><ul><ul><ul><li>J2EE Connector Architecture </li></ul></ul></ul><ul><ul><ul><li>Enterprise JavaBeans </li></ul></ul></ul><ul><li>Standard transports </li></ul><ul><ul><ul><li>HyperText Transfer Protocol </li></ul></ul></ul><ul><ul><ul><li>WebSphere MQ (MQ APIs or JMS) </li></ul></ul></ul><ul><ul><ul><li>TCP/IP sockets </li></ul></ul></ul>Whitepaper: Delivering quick access to CICS systems using strategic integration options ibm.com/software/htp/cics/library/indexes/whitepapers.html 1 4 5 6 3 2
    16. 16. Access to CICS - (inbound) CICS TS Web services Servlet Browser JCA EJB WebSphere MQ TCP/IP Sockets Web services 1 4 5 6 3 2 J2EE App Server D B A I
    17. 17. Access from CICS – (outbound) CICS TS 1 5 6 B A Web services Web server WebSphere MQ TCP/IP Sockets EJB Web services J2EE App Server 4 3
    18. 18. Standard architecture - JCA <ul><li>The J2EE Connector Architecture (JCA) defines the common client interface (CCI) for a Java client to drive interactions with enterprise information systems such as CICS </li></ul><ul><li>The CICS Transaction Gateway provides the JCA access to CICS </li></ul>Client CICS TS CCI CICS Transaction Gateway JCA J2EE Server A D B 2
    19. 19. J2EE Connector Architecture (JCA) <ul><li>Connector/adapter code can be hand-written or built (e.g ‘J2C bean’ generation capability of Rational Application Developer) </li></ul>J2EE Server (e.g WebSphere Application Server) Application Component (e.g EJB) Resource Adapter (e.g CICS ECI resource adapter) Enterprise Information System (e.g CICS) System Contracts Container-Component Contract <ul><li>Connection </li></ul><ul><li>Management </li></ul><ul><li>Transaction </li></ul><ul><li>Management </li></ul><ul><li>Security </li></ul><ul><li>Management </li></ul>Common Client Interface (CCI) EIS Specific Interface ConnectionFactory cf =< JNDI lookup > Connection connection =cf.getConnection(); Interaction interaction =connection.createInteraction(); interaction.execute(<input and output data>); interaction.close(); connection.close();
    20. 20. Exposing CICS applications as Web service - Connector approach <ul><li>Wizards are available in Rational Application Developer, WebSphere Integration Developer, and WebSphere Developer for zSeries to generate the objects that do any necessary conversion and data formatting before invoking the CICS program via the CICS TG. </li></ul><ul><li>These tools can also take the generated objects and expose them as Web Services. </li></ul>CICS TS Web Service Client CICS Program Business logic B Other/Any CICS Transaction Gateway CICS TG WebSphere Application Server Web Service Support WAS J CA D A
    21. 21. J2EE Connector Architecture (JCA) CICS Network HTML WebSphere Application Server and CICS TG on z/OS WebSphere Application Server and CICS TG on a distributed platform WebSphere Application Server on a distributed platform CICS TG z/OS Topology 1 Topology 3 Topology 2 zSeries
    22. 22. CICS Transaction Gateway – Secure interoperation <ul><li>CICS TG supports </li></ul><ul><ul><li>SSL and SSL client authentication </li></ul></ul><ul><ul><li>Userid and password (and passticket) authentication </li></ul></ul><ul><ul><li>Identity assertion (when CICS TG resides on z/OS or SSL used) </li></ul></ul>CICS TS CICS Program Business logic B CICS Transaction Gateway CICS TG (z/OS) WebSphere Application Server Web Service Support WAS (any platform) J 2 C DB2 EJB SOAP EXCI RRS SSL Alice Authentication Confidentiality and Integrity Authorization Authentication (optional) Web Service Client Other/Any
    23. 23. CICS Transaction Gateway – Transactional interoperation <ul><li>J2EE standards provide for two-phase commit recovery </li></ul><ul><li>WebSphere Application Server controls the transaction </li></ul><ul><ul><li>XA protocol used for syncpointing and recovery </li></ul></ul><ul><ul><li>Two choices for XA intercommunication </li></ul></ul><ul><ul><li>1. CICS TG uses RRS to communicate with CICS when using EXCI </li></ul></ul><ul><ul><ul><li>Gateway must reside on z/OS </li></ul></ul></ul><ul><ul><li>2. CICS TS V3.2 provides XA support </li></ul></ul>CICS TS Web Service Client CICS Program Business logic B Other/Any CICS Transaction Gateway CICS TG (z/OS) WebSphere Application Server Web Service Support WAS (any platform) J 2 C VSAM DB2 DB2 EJB SOAP EXCI IPIC TCP/IP XA Global transaction
    24. 24. Sample customer configuration
    25. 25. CICS Transaction Gateway - Capability <ul><li>Capabilities </li></ul><ul><ul><li>Enabler for J2C/JCA </li></ul></ul><ul><ul><li>Synchronous </li></ul></ul><ul><ul><li>Inbound only </li></ul></ul><ul><ul><li>Gateway daemon runs on many platforms </li></ul></ul><ul><ul><li>Proprietary flows over TCP/IP or SNA </li></ul></ul><ul><ul><li>Highly optimized transports </li></ul></ul><ul><ul><li>Range of high availability configurations </li></ul></ul><ul><li>Security to zSeries </li></ul><ul><ul><li>SSL to CICS TG on z/OS or directly into CICS TS V3.2 </li></ul></ul><ul><ul><li>Asserted Identity and Thread Identity solutions to CICS TS </li></ul></ul><ul><ul><li>Passtickets supported </li></ul></ul><ul><li>Transactional scope </li></ul><ul><ul><li>Wide range of transactional controls </li></ul></ul><ul><ul><li>2-PC (XA resource) when CICS TG on z/OS or CICS TS V3.2 is used. </li></ul></ul><ul><ul><li>2-PC (last participant support with WAS V6) </li></ul></ul><ul><ul><li>1-PC for older CICS TS/TG releases. </li></ul></ul><ul><li>Interface </li></ul><ul><ul><li>J2C = Java (CICS TG) </li></ul></ul><ul><ul><li>Other languages (direct to CICS) </li></ul></ul><ul><ul><li>COMMAREA or Container interfaces </li></ul></ul><ul><ul><li>ASCII to EBCDIC performed on client or CICS (zSeries) </li></ul></ul><ul><li>Coupling </li></ul><ul><ul><li>Medium coupling, programs on both sides need to know data layout. </li></ul></ul><ul><ul><li>Layout described via IBM proprietary standard (Rational tooling) </li></ul></ul><ul><li>Tools </li></ul><ul><ul><li>Can generate Data binding beans or J2C beans from </li></ul></ul><ul><ul><ul><li>Rational Application Developer V6 </li></ul></ul></ul><ul><ul><ul><li>WebSphere Integration Developer </li></ul></ul></ul><ul><ul><ul><li>WebSphere Developer for zSeries </li></ul></ul></ul>
    26. 26. Standard architecture – Web services <ul><li>CICS provides direct access from Web service requesters and to Web service providers </li></ul><ul><li>WSDL is used to describe the service </li></ul><ul><li>Tools are typically used to generate the client proxy and message adapter </li></ul>Client A CICS Web support WebSphere MQ Trigger Monitor Pipeline CICS or custom data mapping CICS TS SOAP D B Proxy 1
    27. 27. Web services in CICS TS V3 CICS CICS provided utilities CICS Web service conversion WSDL Service Requester IDE tools WSBind file lang . structure top down bottom up Tools Runtime Business logic SOAP Pipeline CICS Web Services Assist Utilities: DFHLS2WS DFHWS2LS <ul><li>location </li></ul><ul><li>protocol </li></ul><ul><li>operation </li></ul><ul><li>message format </li></ul>
    28. 28. Exposing CICS application as Web service Direct service call approach <ul><li>Web Services Clients (examples): </li></ul><ul><ul><li>WebSphere BPEL process (Process Choreography) </li></ul></ul><ul><ul><li>WebSphere Datapower </li></ul></ul><ul><ul><li>.NET assembly </li></ul></ul><ul><ul><li>WebSphere MQ client </li></ul></ul><ul><ul><li>Another program in CICS (invoke Web service) </li></ul></ul><ul><ul><li>Anything that can invoke a Web Service </li></ul></ul>CICS TS Web Service Client CICS Web Services support Integration logic Data access Business Function D I Business logic B Other/Any (Service Provider) A
    29. 29. CICS Web Services Support - outbound <ul><li>Invoke Web Services from CICS programs </li></ul><ul><ul><li>Any Language (COBOL, Assembler, PL/I, C, C++, Java) </li></ul></ul><ul><ul><li>EXEC CICS INVOKE WEB SERVICE … </li></ul></ul><ul><li>Web Service Provider could be (examples): </li></ul><ul><ul><li>WebSphere BPEL process (Process Choreography) </li></ul></ul><ul><ul><li>A CICS based Web Service </li></ul></ul><ul><ul><li>WebSphere Datapower </li></ul></ul><ul><ul><li>.NET assembly </li></ul></ul><ul><ul><li>Any Web Service (SOAP over HTTP or MQ) </li></ul></ul>CICS TS Web Service Provider CICS Web Services support From CICS Program Business logic B Other/Any (Service Requester) A
    30. 30. CICS Web Services Support – Secure interoperation <ul><li>CICS Web services can be secured using a combination of </li></ul><ul><ul><li>Transport security </li></ul></ul><ul><ul><li>WS-Security </li></ul></ul><ul><li>End to end security is possible based on WebSphere and CICS support for WS-Security and identity assertion </li></ul>CICS TS Web Service Requester CICS Web Services support Business logic WebSphere Application Server (any platform) Pipeline J2EE DB2 WS-Security Authentication SOAP/HTTPS Confidentiality and Integrity Authorization Alice D B I
    31. 31. CICS Web Services Support – Transactional interoperation <ul><li>WS standards provide two-phase commit transactional support </li></ul><ul><ul><li>WS-AtomicTransaction </li></ul></ul><ul><ul><li>WS-Coordination </li></ul></ul><ul><li>All flows are via TCP/IP </li></ul><ul><li>WebSphere Application Server becomes the transaction manager </li></ul>CICS TS Web Service Requester CICS Web Services support Business logic WebSphere Application Server (any platform) Pipeline VSAM DB2 EJB DB2 WS-Atomic Global transaction SOAP D B I
    32. 32. CICS Web Services - Capability <ul><li>Capabilities </li></ul><ul><ul><li>Synchronous when over HTTP </li></ul></ul><ul><ul><li>Asynchronous when over WebSphere MQ </li></ul></ul><ul><ul><li>Inbound and outbound </li></ul></ul><ul><ul><li>Flexible configuration using enhanced System Management </li></ul></ul><ul><ul><ul><li>Multiple protocol configurations per server </li></ul></ul></ul><ul><ul><ul><li>Ease of use for header handlers </li></ul></ul></ul><ul><li>Security to zSeries </li></ul><ul><ul><li>WS-Security – point to point security </li></ul></ul><ul><ul><li>WS-Trust - STS can exchange or issue security tokens </li></ul></ul><ul><ul><li>Transport level security </li></ul></ul><ul><ul><ul><li>Basic Authentication and SSL when over HTTP </li></ul></ul></ul><ul><ul><ul><li>User ID and password when via MQ </li></ul></ul></ul><ul><li>Transactional scope </li></ul><ul><ul><li>Web services distributed transactions (WS-AtomicTransaction) </li></ul></ul><ul><ul><li>CICS local transaction </li></ul></ul><ul><li>Interface </li></ul><ul><ul><li>Language structure (COBOL, C, C++, PL/I) in a COMMAREA </li></ul></ul><ul><ul><li>Web services body message (XML) in a CONTAINER </li></ul></ul><ul><ul><li>XML transformation performed on zSeries </li></ul></ul><ul><li>Coupling </li></ul><ul><ul><li>Loose coupling and interoperability are inherent in a service-oriented architecture (SOA) and make it a natural choice for many enterprise applications </li></ul></ul><ul><li>Tools </li></ul><ul><ul><li>Tool enhancements (some CICS TS, some WebSphere Developer for zSeries) </li></ul></ul><ul><ul><li>Broader language support (CICS TS) </li></ul></ul><ul><ul><li>Flexible COMMAREA mapping (WD/z) </li></ul></ul><ul><ul><li>Batch converter generation </li></ul></ul><ul><ul><li>CICS TS Assistant will merge with WebSphere Developer for zSeries </li></ul></ul>
    33. 33. RMI over IIOP (EJB) <ul><li>CICS supports Enterprise JavaBeans (EJB 1.1 spec) </li></ul><ul><ul><li>Session beans </li></ul></ul><ul><ul><ul><li>Stateless and stateful </li></ul></ul></ul><ul><ul><li>Full OTS transactionality </li></ul></ul><ul><ul><ul><li>Container-managed transactions </li></ul></ul></ul><ul><ul><ul><li>Bean-managed transactions </li></ul></ul></ul><ul><ul><li>Container from WebSphere </li></ul></ul><ul><ul><ul><li>Leverages WebSphere Studio tooling </li></ul></ul></ul>3
    34. 34. Enterprise JavaBeans CICS TS EJB Business Logic WAS B EJB Business Logic B CICS TS EJB Business Logic WAS B EJB Business Logic B OR CICS TS Web Service Client Other/Any EJB Business Logic WebSphere Application Server Web Service Support WebSphere App Server B EJB Integration Logic B WAS=WebSphere Application Server
    35. 35. Enterprise JavaBeans - Capability <ul><li>Capabilities </li></ul><ul><ul><li>Synchronous (RMI over IIOP) </li></ul></ul><ul><ul><li>Inbound and outbound </li></ul></ul><ul><ul><li>Easy deployment </li></ul></ul><ul><ul><li>Can use LDAP or COS naming JNDI server </li></ul></ul><ul><ul><li>Java cycles can be dispatched to zAAP processor </li></ul></ul><ul><li>Security to zSeries </li></ul><ul><ul><li>Method level security </li></ul></ul><ul><ul><li>SSL </li></ul></ul><ul><ul><li>Asserted Identity with WebSphere Application Server V5 on z/OS </li></ul></ul><ul><li>Transactional scope </li></ul><ul><ul><li>Can be 2pc with EJBs on other platforms </li></ul></ul><ul><ul><li>Allows CICS resources to be in same unit-of-work with WebSphere Application Server </li></ul></ul><ul><ul><li>CICS/COBOL can not call out to EJBs in same transactional scope </li></ul></ul><ul><li>Interface </li></ul><ul><ul><li>EJB 1.1 Specification </li></ul></ul><ul><ul><li>Session Beans only </li></ul></ul><ul><ul><li>Stateful or Stateless </li></ul></ul><ul><ul><li>Arguments marshalled and de-marshalled on both sides </li></ul></ul><ul><li>Coupling </li></ul><ul><ul><li>Tight coupling, EJB required on both sides </li></ul></ul><ul><ul><li>Bindings tightly coupled with interfaces </li></ul></ul><ul><li>Tools </li></ul><ul><ul><li>Any tool that produces EJB 1.1 compliant session beans, includes </li></ul></ul><ul><ul><ul><li>WebSphere Studio Application Developer </li></ul></ul></ul><ul><ul><ul><li>Rational Application Developer </li></ul></ul></ul><ul><ul><ul><li>WebSphere Integration Developer </li></ul></ul></ul><ul><ul><ul><li>WebSphere Developer for zSeries </li></ul></ul></ul>
    36. 36. WebSphere Process Server and ESB <ul><li>Process Choreography </li></ul>CICS TS CICS Web Services support Integration logic Data access Business Function D I Business logic B (Service Provider) Staff Support Visual Composition Editor
    37. 37. Advanced ESB – WebSphere Message Broker <ul><li>Accepts most any input format </li></ul><ul><li>Delivers most any output format </li></ul><ul><li>Provides transformation services </li></ul><ul><li>Provides choreography services </li></ul><ul><li>Visual development environment </li></ul>CICS TS Client CICS Program Business logic B Other/Any WebSphere Message Broker z/OS or distributed Web Service CICS Adapter WebSphere MQ Web Service Files WebSphere MQ Many, Many
    38. 38. WebSphere Datapower <ul><li>WebSphere Datapower can be used for </li></ul><ul><li>Routing </li></ul><ul><li>Security functions, for example: </li></ul><ul><ul><li>Processing digital signatures </li></ul></ul><ul><ul><li>Identity mapping </li></ul></ul><ul><ul><li>Auditing </li></ul></ul><ul><li>XML transformation </li></ul>CICS TS Client CICS Program Business logic B Other/Any Web Service WebSphere MQ Web Service XML WebSphere Datapower
    39. 39. Recommendations for integration Limit to specialized applications. Plan to adopt Web services where possible Mature technology that provides low level and flexible connectivity to CICS Lowest common denominator for CICS connectivity 6. TCP/IP sockets Use for Web services and to support browsers for niche applications Industry-wide open standard Ubiquitous for direct web browser and basis for web services Lightweight W3C standard for communications over the web 5. HTTP Continue to exploit WebSphere MQ for basic messaging and flowing Web services Widely adopted B2B integration technology that includes CICS connectivity Comprehensive industry standard for assured messaging 4. WebSphere MQ Standard transport Limit to apps that can benefit from consistent J2EE connectivity. Continue to exploit Java as an application language Niche technology that provides highly functional standards-based connectivity to CICS Comprehensive J2EE standard for J2EE components including EJBs in CICS 3. Enterprise JavaBeans Continue to exploit JCA and use within an SOA and ESB Widely adopted precision CICS connectivity with highest qualities of service today Lightweight J2EE standard for calling CICS and other EIS’s 2. JCA Establish plans to transform CICS apps so they can participate in a SOA pattern with Web services Industry-wide open standard integration technology that includes CICS connectivity. Improving QoS, features and performance Comprehensive W3C standards for messaging over the Web supporting SOA to and from CICS 1. Web services Recommendation Positioning Description Standard architecture
    40. 40. Summary <ul><li>CICS TS continues to add features for interoperability </li></ul><ul><li>Positioning CICS as a full participant in SOA solutions alongside WebSphere Application Server </li></ul><ul><ul><li>Utilizing multiple connector technologies </li></ul></ul><ul><ul><li>Built on standard protocols and transports </li></ul></ul>

    ×