4 CICS Connecteurs Exp Fabrice JARASA

8/3/2019 4 CICS Connecteurs Exp Fabrice JARASA

1/39

CICS e-business real life examples

Fabrice JARASSAT

Juin 2003

IBM zSeries Benchmark Center

IBM Montpellier, France

[email protected]


2/39

The following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States,other countries, or both:

AIX

CICS

CICS Transaction Gateway

DB2

DFSMS

IBM

IMS

Language Environment

OS/390

RISC System/6000

RACF

RMF

S/390

VisualAge

WebSphere

z/OS

zSeries

Java and all Java based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the UnitedStates, other countries, or both.

SUN is a registered trademark of Sun Microsystems, Inc. in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.Linux is a registered trademark owned by Linus Torvalds.

Microsoft, Windows, Windows NT, Windows 2000 and the Windows logo are trademarks of Microsoft Corporation in the UnitedStates, other coutries, or both.

Other company, product or service names may be trademarks or service marks of others.

Trademarks


3/39


4/39

DesignWorkshop

Briefing +

e-BSA

October 2001, 1 day

February 2002, 2.5 days

Prototype

April- June 2002

Benchmark

May - June 2002

Prepare environment for prototype

Develop/deploy prototype application

Run prototype tests

Project

Review

June 2002, 2.5 days

Gather detailed requirementsInitial review of potential solutions

Decide scope of prototype

CPUResp

Time

TPSClients

e-business briefing

Gather initial requirements

Design Center & zSerie benchmark Center

Performance tests

Review results

Next steps

Implementation plan


5/39

Trends in CICS e-business

WWW

CICS

3270

COBOL

EJB

WWW

CICS

3270

COBOL

EJB

XMLSOAP

Evolution! .........NOT Revolution

Dynamic e-business

e-business

3270

COBOL

CICS

VSAM


6/39

Scenarios

1. Connecting WebSphere to CICS using the CTGa. Using WebSphere V3

b. Using WebSphere V4

2. CICS and Javaa. Running Java programs in CICS

b. Deploying EJBs in CICS

3. CICS and XML

4. CICS and Web services


7/39

Scenario 1a - 2000/2001

GovernmentThe IT services division taking first steps in transforming its business processes into e-businessapplications (part of eEurope program to encourage the delivery of services via the Web)

To enable citizens to handle tax affairs via the internet (e.g TVA)

Requirements:

Connectivity to existing CICS applications

Open architecture definition based on Java and WebSphere V3.5 for z/OS

Application based on servlet/JavaBean/connector model

High availabilityHigh security based on X.509 certificates

Social Services InstitutionTo have e-business services as an additional channel to provide services to claimants as well aspartners (other public organizations etc.)

Requirements:As above

Incorporate existing Java application framework in solution

Plan migration to WebSphere V4

Connecting WebSphere to CICS using the CTGConnecting WebSphere to CICS using the CTG


8/39

Scenario 1a - prototype configuration

V

I

P

A

Web LPAR1

AOR1

Web LPAR2

Application LPARS

W

A

S

C

T

GW

A

S

C

TG

W

A

S

C

T

G

IBMHTTP

Server

AOR2

AOR4

AOR3

CICSPlex SM

CMAS

CICSPlex SM

CMAS

CICSPlex SM

CMAS

AOR5

SysplexDistributor

WebSphere ApplicationServer V3.5

W

A

S

C

T

G

AOR6

W

A

S

C

T

GW

A

S

C

T

G

IBMHTTP

Server

CICSPlex SMCMAS

SysplexDistributor

CICS

Session

Data

Session

Data

CICS

WebSphere ApplicationServer V3.5

See article in IBM eserver magazine at:www.ibm.com/eserver/zseries/zbulletin/pdf/issue30/cieproject.pdf


9/39

MCICSPPT DPLC UNIVERSAL ACCESS NONE

USER ACCESS ACCESS COUNT

---- ------ ------ -----

FABRICE READ 000000

NIGEL READ 000000

CICSUSER READ 000000

PUBLIC READ 000000

ALAIN READ 000000

ETPSEC READ 000000

ERIC READ 000000

/http_shared/etc/httpd.conf

Protection SEC_Con {

ServerId SEC_Con

AuthType Basic

SSL_Clientauth client

PasswdFile %%SAF%%

UserId %%CERTIF%%

Mask Anybody

}

Protect /SEC/was/Con* SEC_Con

EXCI

CICS TS

User-id

ETPSEC

CEDF :TRANSACTION: DP01 PROGRAM: DFHMIRS TASK: 0000291 APPLID:A6E2CW20

CEMT:

Tas(0000291) Tra(DP01) Fac(RG1 ) Sus Ter Pri( 001 )Sta(TO) Use(ETPSEC ) Uow(B50D7A2DCEC98180) Hty(EDF )

IBM HTTP

Server

Servlet

Thread

RACFSSL V3Certificate

User-id

ETPSEC

Scenario 1a - end to end security

WebSphere Application

Server V3.5


10/39


11/39

Scenario 1b - 2002

Bank

New e-business architecture for bank transfers between regional branches

Architecture study to choose platform(s) and target configuration

Requirements:

Connectivity to existing CICS applications

WebSphere V4 (or V5) as application server

Initial application based on servlet/JavaBean/connector model

High availability

Authentication based on X.509 certificates

Authorisation and auditing based on userids mapped from certificates

Connecting WebSphere to CICS using the CTGConnecting WebSphere to CICS using the CTG


12/39

HTTP WAS

LDAP

CTG

RACF

CICS

z/OS

HTTP WAS

LDAP

CTG

RACF

CICS

Z

HTTP WAS

LDAP

CTG

RACF

CICS

z/OS

IHS on z/OS

WAS on

distributed

HTTP server

on distributed

WAS on z/OS

Scenario 1b - classification of configurations

Option 1

Option 2

Option 3


13/39

IHS

IHS CICS

CPSM

WAS

Server Instance

IHS

IHS

CTG

CICSCPSM

CICSAORCICSAOR

RACF

XCF

2 LPAR Front-End 2 LPAR Back-End

CICSAORCICSAORCICS

AORCICSAOR

CICSAORCICSAOR

htpps

UserId

ControlRegionControlRegion

ServerRegionServerRegion

ServerRegionServerRegion

CTG

CTGGIOP

GIOP

WLM

WLM

WLM

WLM

z/OS Parallel Sysplex

intelligentrouter

verificationof clientcertificat

Scenario 1b - IHS and WAS on z/OS

Option 1

J2EE


14/39

UNIX System Services

TCP/IP

libCTGJNI.so

Component View

ControlRegion

Port

80

Java

Servlet

Server

Region

WAS J2EE Server InstanceStartedby

Operator

Started

by

WLM

WAS J2EE Server

Scenario 1b - What's a WAS J2EE server instance ?


15/39

Scenario 1b - Apache and WAS on W2K

Windows2000

CICSCPSM

CICSAORCICSAOR

RACF

XCF

CICSAORCICSAORCICS

AORCICSAOR

CICSAORCICSAOR

CTG

CTG

CICSCPSM

SSL

UserId

htpps

SDSD

CTG

CTG

SDSD

HTTP

HTTP

WLMclones

WAS

cfg

WAS

cfgcfg

WAS

cfg

WAS

cfgcfg

plugin

plugin

plugin

plugin

LDAP

WLM

WLM

WLM

Ldapsearch

DN->UID


verificationof clientcertificat

Option 2

(SD - Syspex Distributor)


16/39

Scenario 1b - Apache on W2K, WAS on z/OS

CICSCPSM

WAS

Server Instance

CTG

CICSCPSM

CICSAORCICSAOR

RACF

XCF


CICSAORCICSAORCICS

AORCICSAOR

CICSAORCICSAOR

ControlRegion

ServerRegion

ServerRegion

CTG

CTG

WLM

UserId

Apache

Apache

HTTP

Servers

htpps

verificationof client

certificat

SDSD

SDSD

WLM

plugin

plugin

plugin

plugin

TH

THTH

WLM

WLM

mappingUserId

intelligentrouter

Option 3

(TH- Transport Handler)

J2EE


17/39

Browserhttps

Web Server

https

zSeries

z/OS

Client Plug-

in

WebSphere4.0.1 Runtime

Web

Container

EJB

ContainerTransport

Handler

t hi s d a yo f , 19 9 ,

by

AA

WARD

WARD

CC

ERTIFICATE

ERTIFICATE

P

P

RESENTEDTO:

RESENTEDTO:

We appreciate your contributionsto our organization. In

recognition ofvaluableachievementsand hard work,we

gladlypresent thiscertificate ofaward.

Type name here

Typenamehere

this da y of , 199 ,

by

AA

WARD

WARD

CC

ERTIFICATE

ERTIFICATE

P

P

RESENTEDTO:

RESENTEDTO:

We appreciate your contributions to our organization. Inrecognition of valuable achievements and hard work, we


Typenamehere

Typenamehere

t hi s day of , 199 ,by

A

A

WARD

WARD

C

C

ERTIFICATE

ERTIFICATE

P

P

RESEN TED TO :

R E S E N T E DTO :

Weappreciateyourcontributionstoourorganization.Inrecognitionofvaluableachievementsand hard work,wegladlypresentthiscertificateofaward.

Typenamehere

Type namehe re

t hi s day of , 199 ,

by

A

A

WARD

WARD

C

C

ERTIFICATE

ERTIFICATE

P

P

RESEN TED TO :

R E S E N T E DTO :

Weappreciateyourcontributionstoourorganization.Inrecognitionofvaluableachievementsand hard work,wegladlypresentthiscertificateof

award.

Typenamehere

Type namehe re

this dayof ,199 ,

by

AA

WARD

WARD

CC

ERTIFICATE

ERTIFICATE

P

P

RESENTEDTO:

RESENTEDTO:

We appreciate your contributionsto our organization. Inrecognition ofvaluable achievementsand hard work, we


Typenamehere

Typenamehere

1

2

3

12

Mutual

authentication

between

Browser and

Web server

Mutual

authentication

betweenWeb server

and

Transport

Handler (TH)

Browsercertificate

forwarded

to TH foruserid

mapping

W2K

Scenario 1b - end to end security

Lookout for new whitepaper 'HTTP Transport Handler and plug-in enhancements in WebSphereApplication Server V4.01 for z/OS and OS/390 fix level 4'

Option 3

S i 1b b ti


18/39

Scenario 1b - observations

Tight integration with RACF for certificate -->userid mapping

Local connection from WAS to CICSUserid automatically propagated to CICS when using the CCIWAS z/OS qualities of service, including workload management

No support for session affinity

Option 1 - IHS and WAS on z/OS

Require to keep RACF and LDAP databases in sync

Userid to be programatically propagated to CTG on z/OSWebSphere plugin manages session affinity

Remote connection from WAS to CICS (CCI connection pooling)

Option 2 - Apache and WAS on W2K

Option 3 - Apache on W2K, WAS on z/OS

WebSphere plugin can forward end user X.509 certificate

WAS z/OS V4 Transport handler and distributed HTTP server can bemutually authenticated by X.509 certificates

Userid automatically propagated to CICS when using the CCI

WAS z/OS qualities of service, including workload management

WebSphere plugin manages session affinity

PreferredPreferred

OptionOption

S i 2 2002


19/39

Scenario 2a - 2002

Bank

Bank wanted to validate use of Java inside CICS

Seeking benefits of merged Java and COBOL development teams

Requirements:

Functional validation of new business functions written in Java

(10 transactions ranging from simple to very complex)Setup of Java support within CICS

Benchmark with performance goals

200 concurrent active users

18 transactions per second

Response time less than 1 second

Measure CPU consumption

Scalability tests

Stability and reliability tests

CICS and JavaCICS and Java

S i 2 fi ti


20/39

Scenario 2a - configuration

CTG 4.02

DB2

CICS TS 2.2

CICS

TRANSACTIONS

WRITTEN IN

JAVA

BUSINESS

LOGICWRITTEN IN

JAVA

THIN CLIENT

WRITTEN IN

JAVA

PC OS/390

S i 2 lt


21/39

Scenario 2a - results summary

Transactions(per second) Averageresp tme(seconds)

MIPS pertransaction DASD I/Oper second

Performance 19 0.2 9 120

Scalability 71 0.5 11 450

Stability(8 hour run)

19 0.2 12 120

Note: the CPU increase for the scalability and stability tests was due to the DB2 databasesize and disorganization of the database

See white paper 'Java - CICS TS V2.2 benchmark'at http://www.ibm.com/software/ts/cics/enews/

Scenario 2a observations


22/39

Scenario 2a - observations

Major tuning parameters were:

Number of JVMs (optimum for benchmark was 10) - avoid 'JVM stealing'Size of JVM (optimum for benchmark was 56M)

CICS uses the JDK 1.3.1 JVM in resettable modeJVM is reset between each transaction

Avoid 'unresettable events' (e.g modification of global static variables)

Transaction abends cause reset of JVM

Customer was pleasantly surprised by performanceof Java in CICS

Next step is to consider replacing fat client with thinbrowser client and WebSphere application

Scenario 2b 2001


23/39

Scenario 2b - 2001

Airline

Validation of z/OS as platform for J2EE applications

Developing new EJB application and investigating deployment options

Prototype used example redbook application Trader

Requirements:

CICS and WebSPhere positioning

Deploy EJBs in CICS and in WebSphere

Workload management of EJBs

CICS

WebSphere

CICS EJB performance guidelines

CICS and JavaCICS and Java

Scenario 2b 2001


24/39

Scenario 2b - 2001

To help understand the role of WAS V4 in

the broader z/OS Application Frameworksolution it is useful to examine its core aims:

Provide a complete implementation of the

foundation of the WebSphere platform on

z/OS through support of J2EE standards

Provide a complete run-time for new

web-centric applications on z/OSProvide a strong integration server for the

integration of heterogenous back-ends in new

business function

Make full use of z/OS quality of service features,

such as Parallel Sysplex and Workload Manager

To help understand the role of CICS TS V2

in the broader z/OS Application Frameworksolution it is useful to examine its core aims:

Enable the efficient and optimizedre-use and

extension of existing CICS applications and business

logic

Allow core business logic in CICS to seamlesslyfit into broader Framework solutions

Provide a run-time for Enterprise logic written using

mixed languages and AD skills

Enable enterprise's with a strong investment in CICS

skills and infrastructure to easily embrace Enterprise

JavaBeans and the Application Framework, by building

on those CICS skills

Scenario 2b Trader EJB application


25/39

Scenario 2b - Trader EJB application

CICS TS V2.1

TraderBean

TRADERBL(COBOL

application)

COMMAREA

JCICS

or CCF

RMI/IIOP

WebSphere

Application Server

V3R5

TraderServlet

HTTP

Sysplex

JNDI

Server

Lookup (*)

(*) Object obj = ctx.lookup("ETP1/NW01/Trader");

Note: at the time of this project the only JNDI server supported by CICS was provided by WebSphereApplication Server AE. The IBM LDAP server on z/OS is now recommended for the CICS JNDI server.

EjbCreateLogon()

GetCompanies()

Buy()

Logoff()

Scenario 2b - CICS EJB workload management


26/39

Scenario 2b - CICS EJB workload management

SharedData

CICSPlex/SM

MVS Workload Manager

Sysplex

AOR

AOR

Listener

Listener

Listener AOR

Logical EJB Server

Client

AOR

AOR

Listener

Listener

DNS

Connection

Optimisation

For an explanation of the differences between Sysplex Distributor and DNS Connection Optimisation see the whitepaper'Leveraging z/OS TCP/IP Dynamic VIPAs and Sysplex Distributor for higher availability'athttp://www.ibm.com/servers/eserver/zseries/library/techpapers/gm130165.html

RequestModelCorbaServer

Type

Beanname

INTFacetype

Operation

Transid TRDE

RequestModel

RMETP3T

ETP1

Ejb

Trader

Both

*

Transaction

Transaction TRDE

Program FJJIIRPDynamic Yes

CorbaServer

HostCorbaServer ETP1

cicsejb.etplex.pssc

JNDIprefx ETP1/NW01Port 683

Scenario 2b - CICS EJBs and CICSPlex/SM


27/39

Scenario 2b - CICS EJBs and CICSPlex/SM



28/39


Deploying EJBs in CICS is relatively simple

Workload management of EJBs in CICS builds onexisting CICS and MVS capabilities

Dynamic transaction routing, CICSPlex/SM

MVS Workload Manager (WLM)

Workload management of EJBs in WebSphere basedon MVS WLM

See Design Center scenario for European Government in redbook publishedNovember, 2002

'Enabling High Availability e-business on zSeries (SG24-6850-00)'

Guidance can be provided on performance

Scenario 3 - 2001


29/39

Scenario 3 2001

Bank

New architecture for application integration

Architecture study of XML parsing options

Requirements:

XML connectivity to existing CICS applications

Describe the different techniques to parse XML flow for generating a CICSCommarea

For each technique, describe advantages and drawbacks

CICS and XMLCICS and XML

Scenario 3 - considered solutions


30/39

Browser Client

ApplicationClient

CICS TS

COMMAREA

COBOL

Program

Websphere AS V4

Web

Container

HTTP/

HTTPS

HTTP/XML

or HTTPS

MQSeries

EJB

Container

Parse in WAS

Parse in EAI

Parse in CICS

IBM

HTTP

Server

Scenario 3 considered solutions

Scenario 3 - XML parsing in Web container


31/39

Scenario 3 XML parsing in Web container

CICS TS

Websphere Application Server V4

COMMAREA

Connector

COBOL

Program

z/OS

Web Container

Servlet

EXCI

Command

beanJSP

HTTP/

HTTPS

HTTP/XML

or HTTPS

XMLinbound

parsing

XML outbound

generation

IBM

HTTP

Server

Command bean parses XML message using classes of XML Toolkit for z/OSand OS/390 and builds Record bean which is then passed to the connector

Scenario 3 - XML parsing in WAS(pros/cons)


32/39

Advantages

SAX and DOM supportedTooling support is goodFits well with WebSphere integration roleJSP provides solution for XML generationStrategic (e.g future Web Services support in WAS/390)Open (e.g use of alternative open-source parsers, open todifferent protocols in future)

Major

Considerations

XML parser performance ?For performance considerations see:http://www.ibm.com/servers/eserver/zseries/software/xml/perform/32,500 byte limit for commarea

p g (p )

Scenario 3 - XML parsing in CICS


33/39

XML parsed in CICS by user written program which uses new XML

parsing support in Entreprise COBOL for z/OS and OS/390 V3.1

CICS TS 1.3

Websphere Application Server V4

IBM

HTTP

Server EXCI

COMMAREA

Connector

COBOL

Program

z/OS

Web Container

Servlet

Command

bean

HTTP/

HTTPS

HTTP/XML or

HTTPS

XML FlowDPL

input XML message

Cobol verb XML PARSE ....

In/out Commarea mapper

generate output XMLmessage EXEC CICS

CREATE DOCUMENT

XML

inbound

parsing

Web-aware program

XML Flow

XML outbound

generation

Scenario 3 XML parsing in CICS

Scenario 3 - XML parsing in CICS(pros/cons)


34/39

Advantages

Fits well with CICS AD strategy for easy entreprise modernizationReuse existing COBOL and CICS skillsAnticipate good performance of COBOL parserSimple parser - easy to understand by COBOL programmersContinuation allowed after some XML errorsManagement , scalabitity , performance (CICSplex config )

Major

Considerations

No benchmark data for COBOL V3.1 parserEvent-based interface ( SAX - like ) inbound XML onlySubset of SAX function onlyWell-formedness checks but no processing of DTD (non-validating)No XML generator - can use by EXEC CICS CREATE DOCUMENTXML message size restricted to 32K - can be resolved using multipleECI calls (or direct access to CICS via CICS Web Interface)

Scenario 4 - 2002


35/39

BankExtend existing browser based online banking applications with new Web services

Enable corporate customers to access a range of banking transactions

Requirements:

Connectivity to existing CICS applications using CTG

Business logic in CICS, presentation logic in WebSphere

Very high security based on X.509 certificates

Initial deployment on pSeries, target deployment on zSeries

Railway operatorExtend existing browser based e-ticketing applications with new Web services

Interoperability with business partners (travel agencies, airline ...)

Requirements:

Connectivity to existing CICS applications using MQSeries

Guidance on developing J2EE compliant applications

Prototype of new application architecture based on J2EE and Web services

Deploy on zSeries

Fast response times (


36/39

HTTP

WebSphere

Bean COBOLWeb

service

CICS

SOAP envelope

Connector

User written

SOAP parserHTTP

SOAP envelope

CICSWeb

interfaceCOBOL

p

CICS

HTTP

WebSphere

EnterpriseService

COBOLWebservice

CICS

SOAP envelope

CCI

EJB

client

RMI/IIOP

Option 1

Simple Web service

developed by WSAD

Option 2

Enterprise service

created by WSAD-IE

Option 3

Simple Web service

created by WSAD

SOAP-enabled applicationdeployed in CICS

WSIF

(WSIF - Web Services Invocation Framework)

Scenario 4 - observations


37/39

WSAD and WSAD-IE provide great support for

developing Web servicesSimple Web services based on JavaBeans or Enterprise JavaBeans

Enterprise services which can be accessed as a Web service or froman EJB client

Enterprise services can be combined in a 'service flow' (see presentation'Exploring WebSphere Studio Application Developer Integration Edition')

What about performance ?

Guidelines exist but there is a lack of benchmark data

What about security ?End to end security required

HTTPS is supported

WS-Security 1.0 security technology proposalsto be published soon

Summary


38/39

Connecting WebSphere to CICSWhich connector

Development tools

Security

Workload Management

Availability

XML and CICS

Where to parse the XML

Performance

Enterprise JavaBeansWhen to use

Where to deploy

How to manage

Performance

Web Services

How to implement

PerformanceSecurity

Contact Information


39/39

Education workshopsIBMers through IBM Global Campus : http://w3.education.ibm.comCustomers, BPs through local IBM DirectInternet::http://www-5.ibm.com/services/learning/fr/ta-iris.nsf/External%5CX-23?OpenView&Start=1&Count=30&Expand=1#1

IBMers: http://w3.pssc.mop.ibm.com/

Design Center for e-business on DemandInternet : www.ibm.com/servers/design_center/IBMers : w3.pssc.mop.ibm.comemail : [email protected]

Want to know more or need to contact us ?

Documents

4 CICS Connecteurs Exp Fabrice JARASA