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.
12.
13.
14.
15.
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. 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.
19.
20.
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
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.
36.
37.
38.
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