Professional Documents
Culture Documents
Russ Heald
IBM Software Services for WebSphere, Hursley
healdr@uk.ibm.com
Acknowledgements
Agenda
What is e-business and how does CICS relate to it?
Three styles of Enterprise Transformation
Pervasive
Devices
Transformation
Business Process Outsourcing Composable
Mergers, Acquisitions & Divestitures Processes
Requires
Flexible IT Architecture
On demand Operating Environment
Service Oriented Architecture (SOA) Composable
Development Infrastructure Management Services
Software Integration Infrastructure
Development Management
“Innovate” by restructuring
Business Value
CICS Link3270
Existing Applications (CICS, IMS, …)
3
WSAA, WSED, Harvest Components
WSAD-IE
7 CICS and WAS Integration Options © 2003 IBM Corporation
IBM Software Group
HATS is WebSphere-based
WebSphere Studio
– HATS Studio is a plug-in.
WAS and WebSphere Portal
Server
– HATS Studio creates a .ear (or a
.war).
Open, flexible environment for
the creation of host portlets
– Screen customisation capabilities.
– Select specific data from a host
screen.
CICS TS
Transaction
3270 terminal P B D
Transaction
3270 terminal P
e-business client I B D
A
A
– Messaging middleware
A
Web services 1
J2EE App Server
Web services
JCA 2
I B D
Browser Servlet EJB 3
4
WebSphere MQ 5
TCP/IP Sockets 6
Message adapter B D
The SOAP for CICS feature provides direct access from Web service
requesters and to Web service providers
WSDL (Web Services Definition Language) is used to describe the service
Tools are typically used to generate the client proxy and message adapter
17 CICS and WAS Integration Options © 2003 IBM Corporation
IBM Software Group
CCI A
JCA Message adapter
CICS
Transaction B D
Gateway
Capabilities
– Inbound only
– 32KB maximum message size
– Synchronous and asynchronous (within a client request!)
Security to zSeries
– SSL to the CICS TG daemon
– User ID and password
Transactional scope – see next chart
– Local transactions
– Global transactions
Interface
– COMMAREA
Coupling
– Medium – typically the COBOL formatted records are exposed to the client
– Tools can abstracted the COMMAREA interface by generating easier to
use proxies
20 CICS and WAS Integration Options © 2003 IBM Corporation
IBM Software Group
JCA B D
Message adapter
A
HTTP
CICS Web support
Web API
Message adapter B D
JMS A
WebSphere MQ WebSphere MQ trigger monitor
MQ API
Message adapter B D
A
Message adapter WebSphere MQ DPL bridge B D
WMQ
WebSphere MQ
WebSphere MQ
Capabilities
– Inbound and outbound
– Asynchronous
– Assured delivery
Security to zSeries
– SSL
– User ID and password as specified in the queue definition
Transactional scope
– CICS transaction – by default the transaction encompasses the message GET
and PUT
Interface
– WebSphere MQ APIs or the COMMAREA when used with the DPL bridge
Coupling
– Medium – typically MQ clients used and data is COBOL formatted records
28 CICS and WAS Integration Options © 2003 IBM Corporation
IBM Software Group
A
TCP/IP
CICS Sockets listener
Child server
Message adapter B D
CICS Sockets
Capabilities
– Inbound and outbound
– Synchronous and possibly async
Security to zSeries
– User ID and password
Transactional scope
– CICS transaction
Interface
– CICS Sockets API – variant of the Berkeley Software Distribution 4.3
Sockets
Coupling
– High – both client and server ends are highly programmable
Comparison table
CICS Transaction Server
Standard architecture Capabilities Security to zSeries Transactional scope Interface Coupling
1. SOAP Synchronous (HTTP) User ID + password CICS transaction XML in a Low
CONTAINER
Asynchronous SSL
(WebSphere MQ)
Inbound and outbound
2. JCA 32KB max message size User ID + password Local transaction COMMAREA Medium
Inbound only Thread identity Global transaction
Synchronous and Async SSL
3. Enterprise JavaBeans EJB state management EJB security roles CICS transaction Enterprise High
Inbound and outbound SSL Global transaction JavaBean
Synchronous session bean
Standard transport
4. WebSphere MQ Inbound and outbound User ID + password CICS transaction WebSphere MQ Medium
API or
Asynchronous SSL
COMMAREA
Assured delivery
5. HTTP Inbound and outbound User ID + password CICS transaction CICS WEB API Medium
Synchronous SSL
6. TCP/IP sockets Inbound and outbound User ID + password CICS transaction CICS sockets API High
Synchronous and Async
Conclusion
CICS provides a range of access options to support
– modern connectivity architectures and
– standard transport mechanisms
With the right external connectors and internal adapters you can
maximize the reuse of existing mission-critical CICS assets
Further information
IBM CICS Transaction Server for z/OS
– Whitepaper “e-business access to CICS: strategic options”
• ibm.com/software/htp/cics/library/cicstsforzos23.html#wpapers
– Companion whitepaper “Integrating WebSphere Application Server and CICS using the JCA”
• ibm.com/software/htp/cics/library/cicstgv5.html#wpapers
– SOAP for CICS Feature - ibm.com/cics/soap/
– Redbook “Revealed! Architecting Web Access to CICS
• redbooks.ibm.com/redbooks/pdfs/sg245466.pdf
HATS – ibm.com/software/webservers/hats
IBM CICS Transaction Gateway – ibm.com/software/htp/cics/ctg/
WebSphere Application Server - ibm.com/software/webservers/appserv/was/
WebSphere MQ - ibm.com/software/integration/mqfamily/index.html
WebSphere Studio Enterprise Edition
– ibm.com/software/awdtools/studioenterprisedev/