IBM CICS Transaction Gateway Connector Release Notes

September 2017


The IBM CICS Transaction Gateway (IBM CTG) connector provides integration with back-end CICS applications using the CICS Transaction Gateway. For Java platforms, CTG implements the JCA resource adapter to connect Java applications to the CICS system. This connector provides access between Mule applications and the CTG.

Version 1.0.0 - September 28, 2017




Mule Runtime


IBM CICS TG (for Multiplatforms and for z/OS)

9.1 and 9.2


9.1 and 9.2


  • The remote CICS TG must be at the same or a higher release level as the version of the JCA resource adapter.

  • The JCA resource adapter must match the CICS TG platform. For example, if you have CICS TG for Multiplatforms, you cannot connect to it from a CICS TG for the z/OS resource adapter.

Required JAR files to configure this connector:

  • ccf2.jar (CICS Common Connector Framework)

  • cicsjee.jar (CICS JEE)

  • ctgclient.jar (CTG Client Library)

  • ctgserver.jar (CTG Server Library)

  • geronimo-j2ee-connector_1.6_spec-1.0.jar (JCA 1.6 specification)


  • JCA 1.6 is needed as a required library to overcome conflicts with JCA 1.5 shipped with the Mule Runtime.


  • Authentication - The connector uses the IPIC (IP interconnectivity) protocol to establish communication with CICS regions over TCP/IP. This type of connection also supports SSL authentication.

  • Execution of CICS Programs - The connector allows users to invoke CICS programs:

    • Using Channels and Containers.

    • Using a COMMAREA. Data transfers are limited to 32 KB.

  • Transactions - The connector leverages XA Transactions by means of Mule’s Transactional scope and the Bitronix Transaction Manager components.

  • DataSense - The connector supports adding metadata using through the Custom Metadata Tab option. Using the copybook feature, you can import a schema that describes the data structure going in and out of CTG for use with DataWeave.

Fixed in this Release

  • None.

Known Issues

  • Although the inclusion of JCA 1.6 as a required library is meant to solve compatibility conflicts with the JCA 1.5 shipped with the Mule Runtime, it is yet unknown if this will cause side effects.

See Also