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

2. Unit Objectives
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

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
WebSphere is IBM's Internet infrastructure software - more commonly known as known as middleware. It is not one single product, it is a provides a software environment made up of heterogeneous but ultimately compatible and complimentary products. The end result is a multi-platform software environment which allows companies to develop, deploy and integrate next-generation e-business applications.
What makes the WebSphere platform so powerful is its wholehearted adoption of the leading open standards technologies. WebSphere is a Java based solution, spanning a wide range of platforms -- more than 35 at last count.. In particular, WebSphere is the industry-leading, Java™ 2 Enterprise Edition (J2EE)-compliant platform for developing, deploying and maintaining Web-based applications (see next visual).
The combination of Java technology and the adoption of Open Standards provides WebSphere customers with leading-edge tools, providing faster development times and more reliable, interoperable e-business applications -- that scale from simple Web publishing to the enterprise-scale transaction processing that we are particularly interested in during this workshop.
WebSphere transforms the way businesses manage customer, partner, and employee relationships.

4. 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
J2EE
1.3
Fully certified and part of Sun's JCEE list
EJB
2.0
EJB 2.0 and EJB 1.1 support
JDK
JDK 1.3
Servlet
2.3
Servlet 2.3
JSP
1.2
JSP 1.2
JTS/JTA
1.0
w/distributed transactions
JMS
1.0.2
With Native Provider, and MQ plug-in
JDBC
2PC across heterogeneous databases
JNDI
JNDI 1.2 for EJB lookup and CosNaming
RMI/IIOP
Fully supported
JavaMail/JAF
Plus Domino support
SSL Security
JSSE and JCE
XML JAXP
XML in EJBs
J-IDL/CORBA
IIOP 1.2
J2C
Bean and container managed
LDAP
SecureWay, iPlanet, ActiveDirectory
HTTP
1.1
Yes
, plus across multiple Web servers
SOAP
SOAP-SEC
2.2.2
Soap support for WebServices.
Tech preview
COM/ASP Support
w/Java wrapping & proxy
JMX
JMX pending
XML4J
4.0
XML support
XSL
XSL parser
Standards
Level
WebSphere 5.0
The Java 2 Enterpise Edition (J2EE) specification is an open standard specification for Java applications. Applications written to this specification can take advantage of the Java 2 component model for software re-use without sacrificing the traditional enterprise computing requirements, which CICS has been meeting for many years, namely:
Reliability
Scaleablility
Integrity
Robustness
The difference is that if you write to the J2EE specification, your enterprise application can potentially run not only on CICS on z/OS , but on any J2EE compliant server on any platform (more about this later).
So one way to look at the J2EE specification is as bringing the traditional strengths of CICS and z/OS to the world of Java, in a non-proprietary way.

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
The J2EE platform requires a database, accessible through the JDBC API, for the storage of business data. The database is accessible from web components, enterprise beans, and application client components. The database need not be accessible from applets.
iiop,giop
Application
Client
Container
EJB Container
EJB
Client
Application
iiop

7. Enterprise JavaBeans Overview
EJB Server
EJB CONTAINER
Home Interface
Transaction attributes
The process of installing an enterprise bean into a container is called deployment. Deployment tools use information provided by the enterprise bean to generate extra code which is installed into the container at the same time as the enterprise bean, and which:
Defines the interfaces available to the client (some of the classes generated by deployment run on the client).
Interfaces between the enterprise bean and the container
Establishes the context in which the enterprise bean is to run - transactional characteristics, security etc
Input to the deployment tool is the ejb-jar file created by the bean provider, which contains the classes for the enterprise bean, and an XML deployment descriptor.
The deployment process generates additional code that is necessary for the execution of the enterprise bean. The code generated is used both on the client machine and on the EJB
server. The definition of the home interface is used to generate an EJB home stub for the client and an EJB home class for the EJB server. The definition of the remote interface is used to generate an EJB object stub for the client and an EJB object class for the EJB server.
The class files for the enterprise bean are packaged into a deployed Java Archive File (JAR) and this file is used for deploying into the EJB server.
Properties
Events
Business
Logic
Methods
Isolation
Environment
properties
Remote
Interface
Persistence
Security attributes

8. J2EE Connector Architecture (JCA)
IMS
J2EE Server
Web Container
http,https
JSP
EIS1
J2EE™ Connector ArchitectureThe Connector architecture is a J2EE SPI that allows resource adapters that support access to Enterprise Information Systems to be plugged in to any J2EE product. The Connector architecture defines a standard set of system-level contracts between a J2EE server and a resource adapter. The standard contracts include:
 A connection management contract that lets a J2EE server pool connections to an underlying EIS, and lets application components connect to an EIS. This leads to a scalable application environment that can support a large number of
clients requiring access to EIS systems.
 A transaction management contract between the transaction manager and an EIS that supports transactional access to EIS resource managers. This contract
lets a J2EE server use a transaction manager to manage transactions across multiple resource managers. This contract also supports transactions that are managed internal to an EIS resource manager without the necessity of involv-ing
an external transaction manager.
 A security contract that enables secure access to an EIS. This contract provides support for a secure application environment, which reduces security threats to the EIS and protects valuable information resources managed by the EIS.
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
Version 1.0 of the J2EE Connector Architecture defines a number of components that make up this architecture:
Common Client Interface (CCI)
The CCI defines a common API for interacting with resource adapters. It is independent of a specific EIS. A Java developer communicates to the resource adapter using this API. See next chart.
System contracts
The Connector architecture defines a standard set of system-level contracts between a J2EE server and a resource adapter. The standard contracts include:
A connection management contract that lets a J2EE server pool connections to an underlying EIS, and lets application components connect to an EIS. This leads to a scalable application environment that can support a large number of clients requiring access to EIS systems.
A transaction management contract between the transaction manager and an EIS that supports transactional access to EIS resource managers. This contract lets a J2EE server use a transaction manager to manage transactions across multiple resource managers. This contract also supports transactions that are managed internal to an EIS resource manager without the necessity of involv-ing an external transaction manager.
A security contract that enables secure access to an EIS. This contract provides support for a secure application environment, which reduces security threats to the EIS and protects valuable information resources managed by the EIS.
These system contracts are transparent to the application developer,
meaning they do not have to implement these services themselves.
Resource adapter deployment and packaging
A resource adapter provider develops a set of Java interfaces/classes as part of its implementation of a resource adapter. The Java interfaces/classes are packaged together with a deployment descriptor to create a Resource Adapter Archive (represented by a file with an extension of rar ). This Resource Adapter Module is used to deploy the resource adapter into the application server.
System Contracts
Resource
Adapter
Transaction
Manager
Connection
Management
Transaction
Security
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.
The CICS Transaction Gateway provides implementations of the CCI interfaces for these two resource adapters in the com.ibm.connector2.cics package. By convention,the .rar suffix is used to denote packaged java code containing a resource adapter implementation.
The .rar files used on the distributed platofrms are cicseci.rar and cicsepi.rar.
A RAR file is much like an EAR file. It is an archive made up of JAR files and a deployment descriptor.
The z/OS ECI resource adapter cicseciRRS.rar is different from the distributed platformimplementation - it uses the MVS RRS facility to manage its tranaction environment.
Because there is no EPI implementation on z/OS, there is no EPI resource adapter for z/OS.

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
Unmanaged Environment
LINK
Linux
CCI
Java
Application
Transid=CPMI
Bean
tcp,or
SNA,
TN62
CTGJNI.dll
z/OS

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
Network
Topology 3
HTML

14. WAS and CICS TG deployed on distributed platforms
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 A R E
COBOL application
CTG V5
EJB
Client
daemon
SNA or
TCP62 or
TCP/IP
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. WAS deployed on distributed platforms, Remote Gateway daemon on z/OS
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
JSP
JNI
Servlet
EXCI
CTG V5
EJB
TC/IP, HTTP,
HTTPS,SSL
CICS TS
CICS ECI
resource
adapter
CCI C O M A R E
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. WebSphere Application Server and the CICS Transaction Gateway on z/OS
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 A R E
CTG V5
COBOL application
EJB
EXCI
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 A R E
COBOL application
CTG V5
TCP62 or
TCP/IP
Hipersockets
EJB
CICS ECI
resource
adapter
Client
daemon
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. Unit Summary 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