Migrating from the CICS Connector for CICS TS to the CCI Connector for CICS TS

If you have existing applications that use the CICS® Connector for CICS TS, you must upgrade them to use the CCI Connector for CICS TS instead.

Table 1 summarizes the upgrade choices for CICS Java components that use either the CICS Connector for CICS TS or the CCI Connector for CICS TS, and states a preferred solution for each case.
Table 1. Suggested upgrade path for CICS Java components that use the CICS CCF or CCI connectors
Connector used by current program Connector interface used by current program Status in CICS TS 3.1 Suggested upgrade strategy
CICS Connector for CICS TS CICS Transaction Gateway API (ECIRequest) Not supported The CICS Transaction Gateway API is no longer supported. Re-engineer to use the CCI Connector for CICS TS. Program the connector either directly or by means of a rapid application development (RAD) tool that supports it.
CICS Connector for CICS TS CCF, programmed either directly or with VAJ Enterprise Access Builder or similar Not supported CCF is replaced by CCI. Re-engineer to use the CCI Connector for CICS TS, which performs better than the CICS Connector for CICS TS and uses an industry-standard interface. Program the connector either directly or by means of a RAD tool that supports it.
Note: It is possible to program the CCI Connector for CICS TS using VAJ Enterprise Access Builder, but this is not recommended because VAJ/EAB is no longer supported.
CCI Connector for CICS TS CCI, programmed directly Supported CCI can be used indefinitely. Programming the CCI directly gives the best performance.
CCI Connector for CICS TS CCI, programmed with VAJ Enterprise Access Builder or similar Supported To continue using VAJ/EAB, changes must be made to the application.