WAS for z/OS V5: Connectivity to CICS for z/OS

1. WAS for z/OS V5:Connectivity to CICS for z/OS

2. After completing this unit, you should be able to know: What WebSphere Application Server is Why J2EE is important What the Java Connector Architecture is How the CICS TG works as a J2EE Connector Some sample topologies Unit Objectives

3. What Is WebSphere Today? • Web and e-business software platform • WebSphere supports Java 2 Enterprise Environment (J2EE) and other Open Standards • WebSphere Application Server • The heart of the WebSphere environment • IBM's flagship J2EE Server • WebSphere Studio Application Developer • Develop J2EE-compliant applications • Strategic way to develop your new e-business applications

4. Standards WebSphere 5.0 Level Fully certified and part of Sun's JCEE list 1.3 J2EE EJB 2.0 and EJB 1.1 support 2.0 EJB JDK 1.3 1.3 JDK Servlet 2.3 2.3 Servlet JSP 1.2 1.2 JSP w/distributed transactions 1.0 JTS/JTA With Native Provider, and MQ plug-in 1.0.2 JMS 2PC across heterogeneous databases 2.0 JDBC JNDI 1.2 for EJB lookup and CosNaming 1.2 JNDI Fully supported 1.0 RMI/IIOP Plus Domino support 1.2 JavaMail/JAF JSSE and JCE 2.0 SSL Security XML in EJBs XML JAXP 1.0 IIOP 1.2 J-IDL/CORBA Bean and container managed 1.0 J2C SecureWay, iPlanet, ActiveDirectory LDAP 1.1 Yes , plus across multiple Web servers HTTP 2.2.2 Soap support for WebServices. SOAP 1.0 Tech preview SOAP-SEC w/Java wrapping & proxy COM/ASP Support JMX pending 1.0 JMX XML support 4.0 XML4J XSL parser 2.3 XSL What Is Java 2 Enterprise Edition (J2EE)? • Single industry-standard owned by Sun Microsystems, Inc • Architects the interactions between: • Transaction Monitors Database Managers HTTP Servers Java clients

5. Key Elements of Java 2 Enterprise Edition • Components • The key focus of application developers: EJBs, Servlets, JSPs, and Clients. • Component behavior specified at deployment time, not in program code. • Containers • Provide services to components transparently, including transaction support and resource pooling. • Containers and connectors conceal complexity and promote portability. • Connectors • Portable APIs which connect to existing enterprise vendor offerings (such as CICS, IMS)

6. WebSphere as a J2EE Server WebSphere Application Server Web Container http,https JSP Servlet iiop,giop EJB Container Application Client Container EJB Client Application iiop

7. Enterprise JavaBeans Overview EJB Server EJB CONTAINER Home Interface Transaction attributes Properties Events Business Logic Methods Isolation Environment properties Persistence Remote Interface Security attributes

8. J2EE Connector Architecture (JCA) IMS J2EE Server Web Container http,https JSP EIS1 Servlet cci cci iiop,giop cci Application Client Container EJB Container EIS2 cci EJB Client Application

9. J2EE Connector Architecture Container-Component Contract Application Component J2EE Application Server Common Client Interface (CCI) Connection Pooling Resource Adapter System Contracts Transaction Manager • Connection Management • Transaction Management • Security Management EIS Specific Interface Security Manager Enterprise Information System

10. CICS TG - J2EE Connector to CICS IMS WebSphere Application Server Web Container http,https JSP CICS Servlet cci EXCI CTG iiop,giop cci Application Client Container EJB Container EJB Client Application

11. CICS TG Resource Adapters • ECI resource adapter • cicseci.rar • Calls CICS COMMAREA-based programs. • EPI resource adapter • cicsepi.rar • To invoke CICS 3270-based transactions.

12. Managed and Unmanaged Environments Web Container Web Container Port 80 Java Servlet http, https tcp,or SNA, TN62 EJB Container CTGJNI.dll CCI Bean CICS TS DFH MIRS J2EE Server Managed Environment LINK Unmanaged Environment Linux CCI Java Application Transid=CPMI Bean tcp,or SNA, TN62 z/OS CTGJNI.dll

13. CICS TG - WAS Topologies WebSphere Application Server and CICS TG on a distributed platform Topology 1 Topology 2 zSeries WebSphere Application Server on a distributed platform CICS TG z/OS CICS TS WebSphere Application Server and CICS TG on zSeries Topology 3 Network HTML

14. Topology 1 WAS and CICS TG deployed on distributed platforms Distributed platform z/OS WebSphere Application Server V5 CICS TS HTTP JSP Servlet C O M M A R E A COBOL application CTG V5 EJB SNA or TCP62 or TCP/IP Client daemon CICS ECI resource adapter CCI

15. Topology 1 - Qualities of Service WAS and CICS TG deployed on distributed platforms The specific qualities of service (in terms of the JCA system contracts) that apply to this topology are as follows. Connection Management Connection pooling of local in memory Connection objects Transaction Management Resource manager local transactions or global transactions with Last Participant Support (LPS) Security Management Component managed or container managed

16. Topology 2 WAS deployed on distributed platforms, Remote Gateway daemon on z/OS Distributed platform z/OS WebSphere Application Server V5 CICS TG Daemon HTTP JNI JSP Servlet EXCI CTG V5 EJB TC/IP, HTTP, HTTPS,SSL CICS TS CICS ECI resource adapter CCI C O M M A R E A COBOL application

17. Topology 2 - Qualities of Service WAS deployed on distributed platforms, Remote Gateway daemon on z/OS The specific qualities of service (in terms of the JCA system contracts) that apply to this topology are as follows. Connection Management Connection pooling of TCP/IP network connections from the WebSphere Application Server to the Gateway daemon Transaction Management Resource manager local transactions or global transactions with Last Participant Support (LPS) Security Management Component managed or container managed (including asserted identity)

18. Topology 3a WebSphere Application Server and the CICS Transaction Gateway on z/OS z/OS WebSphere Application Server V5 CICS TS HTTP JSP Servlet C O M M A R E A CTG V5 COBOL application EXCI EJB CICS ECI resource adapter JNI CCI

19. Topology 3a - Qualities of Service WebSphere Application Server and the CICS Transaction Gateway on z/OS The specific qualities of service (in terms of the JCA system contracts) that apply to this topology are as follows. Connection Management Connection pooling of local in memory Connection objects Transaction Management Global transactions with full two-phase commit, using MVS RRS Security Management Component managed or container managed (including thread identity support)

20. Topology 3b WebSphere Application Server and CICS Transaction Gateway on Linux on zSeries z/OS Linux on zSeries WebSphere Application Server V5 CICS TS HTTP JSP Servlet C O M M A R E A COBOL application TCP62 or TCP/IP Hipersockets CTG V5 EJB Client daemon CICS ECI resource adapter CCI

21. Topology 3b - Qualities of Service WebSphere Application Server and CICS Transaction Gateway on Linux on zSeries The specific qualities of service (in terms of the JCA system contracts) that apply to this topology are as follows. Connection Management Connection pooling of local in memory Connection objects Transaction Management Resource manager local transactions or global transactions with Last Participant Support (LPS) Security Management Component managed or container managed When using WebSphere Application Server with Linux on zSeries, the zSeries HiperSockets feature can be used to provide efficient cross-memory TCP/IP connection into CICS regions running on z/OS

22. Key points from this unit: CICS TG and WebSphere Application Server go very well together Flexibility when deciding how to deploy CICS TG Code and test on the workstation and run on z/OS unchanged Unit Summary