CICS Transaction Server V3.

CICS Modernization & Integration

© 2006 IBM Corporation

 CICS Transaction Server V3.1

Modernization – easier than thought

“The irony is that host applications are probably better suited for exposure
as part of an SOA than many applications based on more modern 4GL
object-oriented languages
When folks wrote screen-based transactions many months ago, they
wrote it at a business function viewpoint: I add a customer, I add an
order for that customer, I check backlogs for that customer, etc. So
in many respects, those CICS screens of 15 years ago are better
suited to service orientation than a lot of the newer, distributed code
that’s been written over the last several years, because of their
affinity with a business function, what did the object-oriented guys
do? They took those screens and they broke them down into a
thousand different objects.”
Phil Murphy, Forrester Research

2 © 2006 IBM Corporation

 CICS Transaction Server V3.1

CICS and SOA is big !

Source: Arcati Limited - The Arcati Mainframe Yearbook 2007

3 © 2006 IBM Corporation

 CICS Transaction Server V3.1

Three Styles of Application Transformation

Transform Transform App Transform App

User Experience Connectivity Architecture
Enhance user interface and Supply new interfaces to Break off monolithic
workflow for quick return on existing application based on applications and create
investment open standards like JCA, JMS, flexible, reusable modules
J2EE or Web Services
componentization

gui-fication

Low Risk – no change to app Low Risk – little or no change High risk
modification
Quick return on investment Medium Return on investment High Return on investment
Affected by change Medium affected by change Reduces maintenance cost
Increases application flexibility
6 © 2006 IBM Corporation
 CICS Transaction Server V3.1

CICS Application Architecture

CICS TS
Transaction

3270
or Integration Business Data
Client HTML logic logic access
Presentation
P I B D

 Best practice in CICS application design is to separate key elements of

the application, in particular:
– Presentation logic eg. - 3270, HTML, XML
– Integration or aggregation logic - Menu, router, tooling
– Business logic - Reusable component
– Data access logic - VSAM, DB2, IMS, …
 Provides a framework for reuse and facilitates separation of concerns,
clear interfaces, ownership, and optimization
 Allows callable business logic – parameters passed via COMMAREA
7 © 2006 IBM Corporation
 CICS Transaction Server V3.1

3270 Based Program Reuse

CICS TS

Transaction
3270 terminal P I/B D

Client Link3270 Bridge

 Some programs combine presentation, integration, and business logic

 Service Flow Modeler (SFM) and Link3270 Bridge provide a callable,
COMMAREA interface to many BMS and terminal-oriented programs
– Information in the COMMAREA is passed to the BMS application
– Does not use VTAM or screen scraping
– No changes required to existing BMS application

8 © 2006 IBM Corporation

 CICS Transaction Server V3.1

Connectivity to CICS
CICS TS

Transaction
3270 terminal P

Client I B D
A
A

 Typical clients…
 Transforming technologies…
– Web service requester
– External connectors
– Java servlet or EJB running in a J2EE app
server A– Internal adapters (user written
– C# application running in a Microsoft .NET or generated by tools)
VM – Standard IP-based protocol
– Web browser
– Messaging middleware
10 © 2006 IBM Corporation
 CICS Transaction Server V3.1

Host Integration – CICS Strategies

CICS TS

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

11 © 2006 IBM Corporation

 CICS Transaction Server V3.1

Factors Influencing your Integration Choices

 Business factors
– Agreed company standard or reference frameworks
– Preferred application development environment and tools
– Availability of skills
 Technical factors
– Security
– Transactional scope (1pc, 2pc)
– Performance
– Granularity
– Reliability, availability and scalability (RAS)
– Synchronous or asynchronous invocation
– Inbound and outbound capability
– Client/server coupling
– Data conversion
– State management
 Applications today are typically delivered across several e-business clients

12 © 2006 IBM Corporation

 CICS Transaction Server V3.1

CICS Web Services Support

Other/Any CICS TS (Service Provider)
Business Function

Web CICS
Integration Business Data
Service Web
logic logic access
Client Services
support I B D

 Web Services Clients (examples):

– Another program in CICS (invoke web service)
– BPEL process (Process Choreography – WPS/WID)
– WebSphere Web Services Gateway
– .NET assembly
– WebSphere MQ client
– Anything that can invoke a Web Service
14 © 2006 IBM Corporation
 CICS Transaction Server V3.1

CICS Web services support (overview)

 protocol CICS Web Services
 operation Assist Utilities:
 message format DFHLS2WS
DFHWS2LS
 location
top down CICS provided
IDE tools WSDL utilities
Tools bottom up

WSBind
WSBind
file
file
lang.
CICS Web service structure

SOAP
Service
Runtime Pipeline conversion Business
Requester logic

CICS

 The pipeline is a set of message handlers that are executed in sequence

 Message handlers perform ‘infrastructure’ processing on request and
response messages and can be used for security, auditing, monitoring etc.
15 © 2006 IBM Corporation
 CICS Transaction Server V3.1

CICS Web Services Support (Requester)

CICS TS (Service Requester) Other/Any
From CICS Program

CICS Web
Business Web Service
logic Services Provider
B support

 Invoke Web Services from CICS programs

– Any Language (COBOL, Assembler, PL/I, C, C++, Java)
– EXEC CICS INVOKE WEB SERVICE …
 Web Service Could be (examples):
– A CICS based Web Service
– BPEL process (Process Choreography – WPS/WID)
– WebSphere Web Services Gateway
– .NET assembly
– Any Web Service (SOAP over HTTP or MQ)

17 © 2006 IBM Corporation

 CICS Transaction Server V3.1
WAS=WebSphere Application Server
CICS Transaction Gateway
WAS
CICS TG CICS TS
Servlet, JSP, J
EJB 2 CICS Program
C
CICS Business
Applet, Any J Transaction
2 logic
Java Pgm Gateway
C B
Many Languages,
Many Platforms

Other/Any WAS CICS TG CICS TS

CICS Program

WebSphere
Web Application J CICS Business
Service Server Web 2 Transaction logic
Client Service C Gateway
B
Support

23 © 2006 IBM Corporation

 CICS Transaction Server V3.1

CTG Topologies

Topology 1.
Application Server and the CICS Transaction Gateway are both deployed on a distributed (non-zSeries) platform.
Topology 2.
Application Server is deployed on a distributed platform and the CICS Transaction Gateway is deployed on z/OS.
Topology 3.
Both Application Server and the CICS Transaction Gateway are deployed on zSeries.

24 © 2006 IBM Corporation

 CICS Transaction Server V3.1
WAS=WebSphere Application Server
Enterprise JavaBeans
WAS CICS TS
CICS TS OR WAS session bean in CICS
(local / remote)
session + entity bean in
other EJS
B B B
B CICS-Pgm(DPL) über
EJB EJB Java Connector (CTG)
EJB EJB
Business Business Business JCICS: Link / Start
Business + CICS Ress.Zugriff
Logic Logic Logic
Logic
JDBC, SQLJ

"any Java", z.B. XML,

java.net, etc.

Other/Any WebSphere App Server CICS TS

WebSphere B B
Web Application
Service EJB EJB
Server Web
Client Business Business
Service
Logic Logic
Support

26 © 2006 IBM Corporation

 CICS Transaction Server V3.1

CICS Interoperability Summary

CICS Transaction Server
Standard architecture Capabilities Security to zSeries Transactional scope Interface Coupling
1. Web Services Synchronous (HTTP) User ID + password Local CICS CONTAINER Loose
transaction
Asynchronous SSL COMMAREA
(WebSphere MQ) Global transaction
XML
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 TIght
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 Tight
Synchronous and Async

40 © 2006 IBM Corporation

 CICS Transaction Server V3.1

Any more questions?

47 © 2006 IBM Corporation

 CICS Transaction Server V3.1

Thai
Traditional Chinese

Russian
Gracias Spanish

Thank You English

Merci Obrigado
French

Brazilian Portuguese
Arabic

Grazie Danke
Italian German
Simplified Chinese

Japanese

48 © 2006 IBM Corporation