Removal of J2C from IBD v10
This document discusses the removal of outdated J2C connectors from IBM Business Developer (IBD). Currently, IBD leverages J2C connectors to interface with CICS, IMS, and iSeries systems, with connection details stored in WebSphere. These connectors, specifically for CICS and IMS, are shipped as resource adapters in the IBD installation directory.
Current State of J2C Connectors in IBD
J2C Connectors for CICS, IMS, and iSeries
IBD uses J2C connectors to interact with various legacy mainframe systems like CICS, IMS, and iSeries. The connection details for these systems are stored within WebSphere, facilitating communication between the Java-based IBD applications and these older systems.
CICS and IMS Connectors
These connectors are packaged as resource adapters and are included in the IBD installation directory. However, they are based on outdated technology and have not been maintained or updated for newer versions of WebSphere or IBD.
iSeries Connectors
Unlike CICS and IMS, there is no official resource adapter for iSeries (AS/400) in the IBD installation. Instead, customers are required to set up their own integration using available tools, such as IBM Host On-Demand (HOD) or custom solutions.
Discontinuation of J2C in IBDv10
Customers are advised to source and manage the J2C connectors from their own CICS Transaction Gateway (CTG) or IMS installation. This allows them to use the latest versions of the connectors that are compatible with their specific WebSphere or IBM middleware environment.
Locating J2C Connectors For CTG
Refer to the IBM support document https://www.ibm.com/support/pages/node/6217349
Locating J2C Connectors For IMS
Refer to the IBM support document