Connectors
Following is the list of core back-end connectors officially supported by OpenLegacy, as of January 2024. Hub availability is noted separately; not every IDE connector is enabled in Hub, and not every Hub connector has a classic IDE wizard. See Legacy connectors.
| Connector | Supported from IDE version | Supported in Hub | Description |
|---|---|---|---|
| Mainframe CICS | 3.5.0 | Yes | Proprietary CICS connector with a small footprint on the host: HTTP client plus a CICS adapter program behind HTTP Service and URImap. The adapter links to CICS programs with the provided parameters. Data type conversion is done on the connector side. Connection can be secured with SSL. |
| Mainframe IMS | 4.1.2 | Yes | IMS transaction invoke using the standard OpenLegacy IMS RPC solution (PL/I, COBOL). |
| Mainframe CTG | 4.2.0 | Yes | Integration with back-end CICS applications using IBM CICS Transaction Gateway. |
| Mainframe Dataset | Yes | Batch calls reading VSAM files from mainframe, based on JCL. | |
| Mainframe Natural | Yes | RPC calls to mainframe, based on Natural. | |
| IBM MQ | 4.2.3 | Yes | IBM MQ transactions delivered as digital services (PCML, COBOL). |
| Mainframe Screens | 3.5.0 | Yes | Stateful tn3270 session. SDK Java models (screen entities) mirror host screens and navigation. doAction / getEntity navigate, identify screens, and exchange fields plus the terminal action. See Screens SDK. |
| AS/400 RPC | 3.5.0 | Invoke IBM i programs (PGM) via a Java model of linkage/entry parameters. PCML (compiler XML) is the preferred description; COBOL source can also be parsed. | |
| AS/400 COBOL | Yes | RPC calls to IBM i based on COBOL. | |
| AS/400 PCML | Yes | RPC calls to IBM i based on PCML. | |
| AS/400 Data Queue | 4.6.12 | Yes | Push a message to a data queue, or wait for a response from a different queue. |
| AS/400 Screens | 3.5.0 | Yes | Stateful 5250 session; same screen-entity pattern as Mainframe Screens. See Screens SDK. |
| SAP | 3.5.0 | Yes | Consume SAP standard or custom BAPIs via SAP JCo 3.0. |
| T24 (Temenos) | 4.2.0 | Yes | Temenos T24 (TAFC and TAFJ) as digital services. |
| Oracle DB | 4.1.0 | Yes | Invoke Oracle stored procedures as SDK entities. |
| SQL SP | 4.1.0 | Yes | Parse stored-procedure SQL IN/OUT parameters. Output structures based on internal queries are not supported by the SQL parser. |
| DB2 AS400 DB | 4.2.3 | Yes | IBM i DB2 calls based on SQL queries. |
| Sybase SP | 4.6.2 | Yes | Sybase stored procedures as SDK entities. |
| MySQL SP | 4.1.0 | MySQL stored procedures as SDK entities. | |
| OData | 4.2.4 | No | OData v2 and v4. |
| SOAP | 3.5.0 | Yes | SOAP web services (XML over HTTP/SMTP). |
| JDBC | 3.5.0 | Yes | JPA/Hibernate CRUD with the same invoke style as other connectors. |
| REST | 3.5.0 | Yes | Consume existing REST APIs (JSON, OpenAPI, XML, XSD) to modify, orchestrate, or add caching. |
| Tuxedo | 3.5.0 | No | Tuxedo services via .jolt interface files (Jolt client 8.1). |
| Graphtalk | 4.5.1 | No | Generate Java entities from Graphtalk XML files. |
| File | 4.5.7 | Yes | One-way connector that produces XML or SWIFT payment files from XSD-driven models. |
| BRM | 4.6.0 | No | Oracle Communications BRM via Java PCM / FList. |
| Kafka | 4.6.5 | Yes | Kafka producer (push to a topic). Consume via an API/service project. |
| Mainframe JCL | 4.6.7 | No | Execute mainframe jobs and retrieve results via FTP; parse copybooks for record types (IDE). |
| CORBA IDL | Yes | RPC CORBA calls based on IDL. | |
| Files-SFTP | |||
| VSAM CICS | Yes | RPC calls reading VSAM files from CICS. | |
| Microfocus COBOL | Yes | RPC calls to Micro Focus based on COBOL. | |
| Active MQ | Yes | JMS with ActiveMQ. | |
| Heirloom CICS | Yes | Compatibility of Java APIs migrated from COBOL using Heirloom. | |
| ISO-8583 | Yes | TCP with card systems over ISO-8583. | |
| DB2 zOs DB | Yes | Mainframe DB2 stored procedures and SQL. | |
| Postgres SQL | Yes | PostgreSQL stored procedures and SQL. | |
| JDE | Yes | RPC calls to JD Edwards business functions on IBM i. |
Connectors are modular Java dependencies. Supporting a new connector may be as simple as adding a dependency and glue code; more complex cases need an analyzer.
Source: OpenLegacy Connectors (Confluence, January 2024)
IDE and Hub connector matrix: IBM Z, IBM i, databases, messaging, SOAP/REST, SAP, and others (as of January 2024).