IBM Software Group

S36
JCA Connection between J2EE and CICS
Product Update and Strategy

Mark Cocker
CICS Technical Strategy and Planning, Hursley Lab, IBM United Kingdom Ltd.

Mark_Cocker@uk.ibm.com

© 2006 IBM Corporation

Agenda

• Connectors and CICS TG

• CICS TG v6 – new features
• CICS TG v6.0.1/6.0.2 – service updates
• CICS TG v6.1 – new features
• Trends and directions

Abstract
The CICS Transaction Gateway (CICS TG) is a market leading connector proven to be a high performing,
secure, scalable and tightly integrated method of e-business access to CICS. It benefits from ease of
installation and flexible configuration options, that requires minimal or no changes in CICS. It provides a
range of networking options and provides a choice of Java and non-Java client APIs. This session will
provide information on the usability, systems management and performance enhancements in the latest
version of the product as well as providing insight into future strategic directions.

© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 2
What is the CICS TG?

1. Plumbing - Connectivity into CICS

• Primary inbound connector to CICS
• COMMAREA (ECI) and 3270 (EPI) based connectors

2. Interfaces - Java and non-Java APIs

• JCA API is strategic and provides enhance QoS
• Base Java, C, COBOL and COM are stabilised

3. Integration - WebSphere and CICS and others

• All versions of CICS in support (10 currently )
• 3 versions of WAS on 7 platforms
• Java + 4 other languages (C, C++, COBOL, COM)
• 5 SNA servers (AIX, Windows, zLinux)

© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 3
CICS Transaction Gateway and Universal Clients

CICS Transaction Gateway v6.0

Priced per processor @ ~10K$ in PPA
Multi-user server gateway for Java clients
Includes CICS UC technology for non Java applications
Complements WebSphere App Server
Win32, AIX, Solaris, HP-UX, Linux on Intel/zSeries/POWER

Web Browser
CICS TG v6.0/v6.1 for z/OS
IPLA OTC product with sub-cap pricing
Multi-user server gateway
Desktop PC Flagship product
Web App Server

Supported CICS servers

CICS Universal Client v6.0 CICS TS for z/OS v2.2, v2.3, v3.1
Priced per seat @ 100$ CICS TS for OS/390 V1.3
Single-user/desktop only CICS TS for VSE v1.1.1, CICS/VSE v2.3
Support for C, C++, COBOL, COM TxSeries v5.0, v5.1, V6.0
No Java support CICS TS for Windows v5.0
Available on Win32, Linux, AIX CICS TS for iSeries (AS/400) v5.1, v5.2, v5.3

© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 4
CICS Transaction Gateway - Toplogies

WebSphere
Topology 1 Application Server
and CICS TG on a
distributed platform
Topology 2
zSeries
WebSphere
Application Server CICS TG
on a distributed
z/OS
platform

WebSphere
Application Server
CICS
Topology 3 and CICS TG
Network on zSeries
HTML

•The 3 principal topologies are described in the Whitepaper Integrating

WebSphere Application Server and CICS using the JCA, G224-7218
© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 5
CICS Transaction Gateway – Connector Positioning

•Preferred implementation for JCA

– Access to all CICS servers from WebSphere Application Server.

•Proven characteristics:
– High performing
– Secure
– Scalable

•Ease of installation and flexible configuration

– Minimal changes to CICS applications
– No components need to be deployed into CICS runtime
– Supports all CICS servers and connectivity methods

•Supports a range of Java and non Java clients

– Including C, C++ COBOL and COM

© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 6
Strategic options to access CICS

•Standard architectures provide comprehensive development tools and

runtime support in CICS

1 – SOAP (Simple Object Access Protocol)

2 – JCA (J2EE Connector Architecture) = CICS Transaction Gateway
3 – Enterprise JavaBeans (J2EE EJB)

– Standard transports are suitable for use by applications that require

greater control of the protocol and do not need the development tools
or qualities of service provided by the standard architectures.
4 – HTTP (HyperText Transfer Protocol)
5 – WebSphere MQ (MQ APIs or JMS - Java Messaging Service)
6 – TCP/IP sockets

Whitepaper: Delivering e-business access to CICS: strategic options, G224-73240

http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi

© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 7
CTG v6 – What’s in the box?

•JCA 1.5 and WebSphere v6 interoperability

•Performance/Scalability

•Systems Management

•Security

•Ease of Use

CTG/CUC v6.0 announced November 30 2004

Announce letter 204-283 Page 8
© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS
JCA 1.5 - WebSphere App. Server

•WebSphere App. Server v6 = JCA 1.5 = J2EE v1.4 spec level

•CICS TG v6 ECI and EPI Resource Adapters will support JCA 1.5 only
– i.e. CICS TG v6 RARs support WebSphere Application Server v6 only
– WebSphere v5/5.1 customers can use CICS TG v5.1 (JCA 1.0) RARs to
talk to a remote CICS TG v6 Gateway daemon
– CICS TG v5.1 RARS are available for download in Supportpac CC03

•JCA 1.5 provides

– J2EE 1.4 Application Server compliance
– Connection Optimizations

•Tooling integration:
– CICS Transaction Gateway and IMS resource adapters are provided
with the J2C tooling component in Rational Application Developer v6

© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 9
WebSphere and CICS TG interoperation
1. For WAS v5, the CICS TG v5.1 JCA 1.0 resource adapter can be used to
communicate with CICS TG v5.1 or later
WAS v5/v5.1
CICS TG v5.1

CICS ECI CICS

J2EE Transaction
Component resource adapter TCP/IP CICS
JCA v1.0 Gateway
V6.0

Note: Supportpac CC03 provides entitled download of JCA 1.0 RARs

2. In local mode the resource adapter must connect to a CICS TG at the

same level
WAS v6
CICS TG v6
CICS
J2EE CICS ECI Transaction
Component local CICS
resource adapter Gateway
JCA v1.5 V6.0

© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 10
JCA 1.5 Connection Optimisations

•Lazy Transaction Enlistment

– Optimizes transaction enlistment calls so that RA only participates

in a transaction if it is actually invoked
– Provides potential better performance if JCA applications are
used in an Enterprise Application
– Not applicable to WAS z/OS local mode (which uses RRS)

•Lazy Connection Association

– Improved connection pooling in WebSphere

– Allows get-use-cache model to be efficiently used with
WebSphere Connection Pool manager

– For more details refer to talk C33

© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 11
Performance - improvements

•CTG/CUC on multi-platforms
– Internal runtime processing improvement
– NPTL Linux threading model on SLES9 and RHEL3
•CTG z/OS
– Improved scalability with EXCI pipes
– Compiler optimizations
– EXCI null truncation optimization (up to ~200K instructions )
– zSeries crypto support for SSL handshakes via JSSE
– zAAP support
•Java/JCA client
– Optimized data handling when returning data to Java client that
contains trailing nulls
•JCA 1.5
– Architectural connection optimisations
• Lazy transaction enlistment
• Lazy connection association

© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 12
Performance – Windows/UNIX/Linux

•Improved internal runtime enhancements within Client daemon

•Applicable to all platforms (Windows/UNIX/Linux)
•Applicable to ECI and EPI applications
•Further improved in v6.0.1
•Gives >25% saving in CPU usage (v6.0.1)

ITR vs ECI COMMAREA size

CICS TG for AIX v5.1 vs v6

2500.0
(Potential throughput at 100% CPU)

2000.0

1500.0
ITR tps

CICS TG v6
CICS TG v5.1
1000.0

500.0

0.0
100 bytes 4K 8K 16K 32K
COMMAREA size (KB)

© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 13
Performance - Linux

•NPTL gives improved performance

over Linux Threads out of the box
(4-5%)
CICS TG ECI throughput in IA32

2000.0
•NPTL is more scalable at high
1800.0
thread utilisations (many 100s)
1600.0
Internal Transaction Rate (ITR)

1400.0 •RHEL 3, 4 and SLES 9 both support

1200.0 NPTL threading model
RHEL 3, NPTL
1000.0
RHEL 3, Linux Threads
800.0 •CICS TG supports:
600.0 – SLES 8 and SLES 9
400.0 – RHEL 3 and RHEL 4
200.0
– Linux/Intel and Linux on zSeries
0.0
ITR 4K ITR 32K
– Linux on POWER (v6.0.1)
COMMAREA

Benchmark: ECI workload into CICS TG/AIX and CICS TS v2

Test hardware: Intel P4, 2.8Ghz, 1CPU, 2GB RAM

© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 14
Performance – z/OS

Optimized code to null truncate

data returned from the EXCI

WebSphere CICS
CICS TG EXCI

32K COMMAREA 32K COMMAREA

CTG 4K 4K
J2EE 4K data 28K nulls 4K data 28K nulls
Java EXCI
component 32K
Client

•Many applications are written to be data size agnostic – so just flow 32K data areas into CICS
•CICS, the EXCI transport and the CICS TG have automatic optimisations to remove trailing nulls from an
ECI COMMAREA flowed into or out of CICS
•CICS TG v6 has optimised code within CICS TG Java/EXCI interface
•Maximum saving on a 32KB COMMAREA with minimal non-null data is ~220K instructions
– Equates to max 40% saving in CICS TG code

© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 15
Performance – z/OS

•General improvements
–Improved garbage collection in CICS TG Java code
–More highly optimized JNI (C) code
•Max saving of ~10K

•Support for zAAP offload in z/OS V1R6.

–Potential for ~40% offload of CICS TG instructions to
zAAP CP
–Actually savings will depend on usage of C functions
•Password authentication
•Writing to the JES log
•RRS (for transactional EXCI)

© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 16
Performance – z/OS zAAP
•zAAP - Java off-load
processors

– IBM Java SDK 1.4.2

MVS – z/OS V1R6
JES HFS
Java console
•CICS TG for z/OS
CTGBATCH
– Mix of Java, and native
Gateway JNI module code (C and assembler)

libCTGJNI
daemon MRO
Java TCP EXCI
client Protocol •Java:
handler RACF – Inbound socket handling
RRS – Thread handling
– Logging
CICS TG z/OS infrastructure
•Native:
– Pipe allocation, data
ƒ Aim: The intent of the zAAP is to provide better price marshalling
– Logging and I/O
performance (hardware and software) for Java
– CICS EXCI libraries
workloads running on z/OS – RACF
• ~40% offload to zAAP (IFA) in benchmarks for ECI – RRS
workload using Gateway daemon
© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 17
zAAP architecture
z/OS Partition
Executable on zAAP Executable on General Purpose CP

WebSphere Servant region CICS region

EXCI
JVM Resource
CTG
Adapter J
RACF
.so
N
(Native Code)
J2EE I Pgm
C asm
app CCI jni_ code
code

jvm
classes
N
J

.so
(JVM Native Code)

c code

ZP ZP ZP CP CP CP CP

For more detail on zAAP exploitation refer to

1. WSC White paper:
z/OS Performance: Capacity Planning Considerations for zAAP Processors
2. http://www.ibm.com/support/techdocs and search on zAAP
© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 18
Performance – Java client

•Client side CICS TG Java code optimisation

Java Gateway
CICS (ctglient.jar)
client tcp/ip daemon
•Provides benefit to CICS application
returning data shorter than the original
Java application COMMAREA length
WebSphere JCA application •Affects all platforms and JCA and or non JCA
Java application
WebSphere JCA application •Benefits WebSphere applications using CICS
TG in local or remote mode
CICS TG Java client performance
•Improved data handling when returning a
10

9
datastream containing trailing nulls
8 •Up to 12% CPU savings measured on
7
Windows, AIX
txn per sec/cpu

6
CTG v5.1
•Up to 150K instructions saving measured on
5
CTG v6.0
4 z/OS
3 •Note: Additional performance benefit also
2
gained if using the RAD J2C beans vs. the
1

0
WSAD-IE WSIF tooling (see talk C32)
100 100 8000 31950 31950

length of non null data in a 32K COMMAREA

© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 19
EXCI pipe scalability
•CTG v6 feature - EXCI Pipe usage
–Improved diagnostics for pipe information messages
•Messages on startup to inform of EXCI limit
•Messages at thresholds to warn as limit approached, and breached
(90%,100%)

–New environment variable (CTG_PIPE_REUSE=ONE)

•Improved reliability and scalability with multiple CICS TORs

•CICS TS v2.2 and 2.3 APAR PQ92943

–New user modifiable LOGONLIM in SYS.PARMLIB for each
MVS image
–Default is 100, maximum is 250 pipes per EXCI address
space

•CICS TS v2.3
–Improved performance of EXCI pipe de-allocate in CICS TS
v2.3 (~20%)
© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 20
 EXCI pipe scalability -2
Workers
CICS TG EXCI
1st request • Allocate
• Open
• DPL request
• Close
Next request
• Open CICS
• DPL request
• Close
Gateway
Termination • Deallocate

•Each allocated pipe has an affinity to the Java thread/USS TCB

•This gives high performance but additional requirement raised for

– Predictable usage pattern
– Better diagnostics
– More throughput per region

•CICS TS v1.3 limits max of 100 EXCI pipes per calling address space
•CICS TG v2.2 allows limit to be raised to 250 pipes
© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 21
EXCI pipe reuse
Sockets Connection Worker Pipes
Managers threads

Java client CM1 CICS A

Worker1

Worker2
Java client CM2 CICS B

CM3 Worker3
Java client
CICS C

Each allocate pipe will remain allocated to each worker thread unless
the variable CTG_PIPE_REUSE=ONE is set
© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 22
Systems management

•Quiesce support
– Normal and immediate shutdown options
– Normal shutdown allows running transactions to terminate

•Improved administration tool

– Integrated with dynamic trace and shutdown functions
– New ctgadmin command line interface

•Ability to run as a Windows service or UNIX daemon

– Standard UNIX script provided (ctgd)

•Improved file handler for Gateway daemon log

– Manages wrapping and max file size of Gateway daemon log

•APPC support on zSeries

– Improved connectivity for CTG on Linux on zSeries

© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 23
System management – z/OS

•SDSF administration interface

– New z/OS console administration interface
– Shutdown and trace admin functions available from z/OS console

•Logging to JES
– New CTGBATCH shell launcher supports logging to JES
(SYSOUT=*) or any DD.
– Easier to configure single address space
– Improved diagnostics when running CTGBATCH

•Improved support for multiple Gateway regions

– ctgenvvar configuration file does not need to be shared amongst all
Gateway regions
– ctgenvvar can be migrated to STDENV DD member

© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 24
Security - JSSE

•JSSE is now the strategic SSL implementation for

the CICS TG

•Following new function has been added in v6

– RACF keyring support on z/OS

– zSeries hardware crypto support on z/OS

– SSL Ciphersuite select option

– Improved diagnostics

Note: SSLight and SystemSSL no longer supported by CICS TG on any

platform (previously announced in CICS TG v5.1 announce letter)

© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 25
Security - JSSE
Gateway
daemon
JSSE Connection
managers
Java Protocol
handler CICS
Client
workers server
JSSE

•SSL support in CICS TG now implemented by Java Secure Sockets

Extension (JSSE)

•Provides following advantages:

– SSL support provided by JSSE in Java SDK, 1.4.2
– Wide range of bulk data ciphers (40, 128, 256-bit)
– SSL cipher suite in use can be controlled using new ciphersuiteselect parameter in CTG.INI
– Crypto support for handshakes on z/OS
– Support for range of keytools: iKeyman, keytool and RACF
– SSL v3 is supported (no support for TLS yet)
© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 26
Ease of use

•Simplified installation and migration

– SMP/E standard install on z/OS

– ISMP standard install on Unix/Windows platforms

•Miscellaneous usability enhancements

– Lower case configuration files (ctg.ini)

– Precompiled EAR samples for WAS

• Also supplied in CICS support pack CA5C for WAS v5.1/CTG v5.1

– CTG_JNI_TRACE_ON environment variable

• Controls activation of JNI trace at startup

– Rewritten Programming Guide

© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 27
Ease of use - Infocenter

•Highly searchable

•Zip file included on media

•Easy integration with other

IBM infocenters

•Both book and task views

•Plugs into any existing

eclipse viewer

•PDF documentation still

provided

View online http://publib.boulder.ibm.com/infocenter/cicstg60/index.jsp

© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 28
Removed components

System SSL and SSLight – Use JSSE support for SSL

•TCPAdmin Handler – Replaced by ctgadmin support
•HTTP/HTTPS network protocols – Required for applets only
•NPI – Redundant technology
•Out of process COM – In process still supported
•Old C/COBOL API versions – Header files removed for compiler
support only

•Following may be removed in a future version:

–Applets – Move to Servlet/J2EE solution
–Terminal Servlet – Use HATS or WD4Z SFM

© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 29
Supported software – CICS TG v6.0

•IBM SDK 1.4.2

•z/OS V1.4, V1.5, V1.6 and later, including z/OS.e

•AIX V5.1, v5.2, v5.3
•Solaris v8, v9, v10
•HPUX 11i, 11iv2
•Linux on Intel: RHEL 3 (U2), RHEL 4, SLES 8, SLES 9
•Linux on zSeries: RHEL 3, RHEL 4, SLES 8, SLES 9
•Linux on POWER: RHEL 3, RHEL 4, SLES 9
•Windows 2000, XP, 2003

© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 30
CTG v6.0.1- Service Update

•Linux on POWER now supported

•New platforms for CICS UC Client (AIX and Linux/POWER )

•Further performance enhancements for UNIX and Windows

•Productised service fixes

CTG/CUC v6.0.1/CUC announced June 14 2005

IBM announce letter 205-147

© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 31
CTG v6.0.2- Service Update

•New platforms for CICS UC (Solaris and HP-UX)

•Extended software support

– Citrix Metaframe support for Windows
– HP-UX 11iv2
– Solaris 10

•Server TCP/IP idle timeout

CTG/CUC v6.0.2 eGA April 24th 2006

•Productised service fixes
© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 32
CTG v6.1 for z/OS – 2PC global transactions

• Two phase commit (XA transactions)

• TCP/IP RAS enhancements

• Productised service fixes

•CICS TG v6.1 for z/OS announced October 4th 2005, announce letter 205-248
•GA date of November 11th

© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 33
 XA transaction support – Two phase commit

Unix/Windows z/OS LPAR

J2EE Application Server Global transaction

Web browser
JSP Java
servlet
Servlet Resource
Transaction Manager
Gateway
Gateway
Manager cicseciXA CICS A
EJB resource Daemon
Daemon
Session bean
JCA adapter
TCP EXCI
JDBC or
SSL CICS B
Datasource
Resource
RRMS
DB2 Resource Manager
Manager
Note:
• CTG v6.1 cicseciXA.rar must be deployed into WebSphere to exploit XA transactions
• J2EE application server (WebSphere) can run also on z/OS or z/OS.e
© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 34
XA support - new components

1. cicseciXA.rar – New XA capable resource adapter

2. XA support within Gateway daemon – needs to be enabled

3. CTGRRMS – New address space to handle APF

authorisation for RRS calls

4. ctgmaster – New Gateway master address space

• Owns RRS registration for the shared UR
• Controls transaction mapping table

© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 35
Migrating to XA support
1. Application does not use transactions
– EJB deployed with the transaction attribute NotSupported or simple servlet
– Can use cicseci.rar or cicseciXA.rar
– Gateway daemon does not need to be enabled for XA, or for CTGRRMS
2. Application uses transactions:
Recommened to install APAR APAR PK17426 (CICS TS V3.1) and APAR PK17427 (CICS
TS v2.x), to force rollback of units of work on an abend.

2A. Application needs to make multiple updates to the same CICS region as one unit-of-
work
• Use the CICS ECI resource adapter (cicseci.rar) and local transactions
• Will avoid the overhead of unnecessary XA flows
• Gateway daemon does not need to be enabled for XA, or for CTGRRMS

2B. Application needs to update 2 or more resource managers (i.e CICS, DB/2, IMS) as part
of a global transaction
• Use the XA resource adapter (cicseciXA.rar)
• Gateway daemon needs to be enabled for XA and CTGRRMS
• ctgmaster required if support for TCP/IP port sharing required
• If using the CTG in local mode with WAS v6 on z/OS, then either cicseci.rar or cicseciXA.rar can be
used as both support the RRS transaction support in WAS z/OS

© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 36
 Migrating to v6.1

WAS v6

CICS ECI
resource adapter
J2EE CICS TG v6.1 1pc CICS
Res-ref
Component Transaction
CICS
Gateway
CICS ECI XA V6.1
resource adapter 2pc (XA)
CICS TG v6.1

• If you wish to migrate applications over to XA support, you can deploy any
two resource adapters into WAS as long as both are at the same level

• Transactional characteristics of the application can then be modified by

modifying the resource reference to point to the new XA resource adapter

© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 37
TCP/IP RAS enhancements

• Load balancing for XA transactions

–Allows Gateway daemons using XA support to exploit with
TCP/IP port sharing

• IP bind support
–Allows Gateway to bind to a specific IP address

• IP subsystem reconnect
–Gateway reconnects to a failed/restarted TCP/IP stack

• SocketConnectionTimeout
–New property on ECIConnectionSpec in resource adapter
–Allows timeout to be set for establishing sockets

© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 38
CICS TG and JCA – Trends and directions

Interoperation/Standards:
•64-bit
•IP v6
•eWLM
•Other J2EE Application Servers
Architectural limits

•32KB relief ->JCA support for with containers/channels

•Improved RAS (WLM integration)
Systems Control

•Systems monitoring of Gateway daemon

•Improved QoS on z/OS

Further details in Statement of Direction: Planned enhancements to the CICS

family of products, IBM Announce letter 206-096, May 2006

© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 39
Extra information
•Whitepapers
– Integrating WebSphere Application Server and CICS using the JCA,
G224-7218 http://w.ww.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi

– Transactional integration of WebSphere Application Server and

CICS with the JCA
http://www.ibm.com/developerworks/websphere/techjournal/0408_wakelin/0408_wakelin.html

•CICS TG support page

– http://www.ibm.com/software/htp/cics/ctg/support /
•CICS TG on-line information centre
• http://publib.boulder.ibm.com/infocenter/cicstg60/index.jsp

•CICS TG support packs

• http://www.ibm.com/software/htp/cics/ctg/support/
– CC03 - CICS JCA 1.0 resource adapters for use with WAS v5
– CE51 - CICS Transaction Gateway Security Exit Samples
– CE52 - CCF compatibility JAR for CICS Transaction Gateway V6.0
– CC12 - CICS Transaction Gateway for z/OS environment health check

Redbooks
–Java Connectors for CICS, SG24-6401
–CICS TG v5, The WebSphere Connector for CICS, SG24-6133-01
–CICS TG v6.1, SG24-6171 (Now availabe in draft)
–Exploring WSAD-IE V5, SG24-6200-00

© IBM Corporation 2006 S36 JCA Connection between J2EE and CICS Page 40