Start Today

← Documentation

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.

ConnectorSupported from IDE versionSupported in HubDescription
Mainframe CICS3.5.0YesProprietary 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 IMS4.1.2YesIMS transaction invoke using the standard OpenLegacy IMS RPC solution (PL/I, COBOL).
Mainframe CTG4.2.0YesIntegration with back-end CICS applications using IBM CICS Transaction Gateway.
Mainframe Dataset YesBatch calls reading VSAM files from mainframe, based on JCL.
Mainframe Natural YesRPC calls to mainframe, based on Natural.
IBM MQ4.2.3YesIBM MQ transactions delivered as digital services (PCML, COBOL).
Mainframe Screens3.5.0YesStateful 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 RPC3.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 YesRPC calls to IBM i based on COBOL.
AS/400 PCML YesRPC calls to IBM i based on PCML.
AS/400 Data Queue4.6.12YesPush a message to a data queue, or wait for a response from a different queue.
AS/400 Screens3.5.0YesStateful 5250 session; same screen-entity pattern as Mainframe Screens. See Screens SDK.
SAP3.5.0YesConsume SAP standard or custom BAPIs via SAP JCo 3.0.
T24 (Temenos)4.2.0YesTemenos T24 (TAFC and TAFJ) as digital services.
Oracle DB4.1.0YesInvoke Oracle stored procedures as SDK entities.
SQL SP4.1.0YesParse stored-procedure SQL IN/OUT parameters. Output structures based on internal queries are not supported by the SQL parser.
DB2 AS400 DB4.2.3YesIBM i DB2 calls based on SQL queries.
Sybase SP4.6.2YesSybase stored procedures as SDK entities.
MySQL SP4.1.0 MySQL stored procedures as SDK entities.
OData4.2.4NoOData v2 and v4.
SOAP3.5.0YesSOAP web services (XML over HTTP/SMTP).
JDBC3.5.0YesJPA/Hibernate CRUD with the same invoke style as other connectors.
REST3.5.0YesConsume existing REST APIs (JSON, OpenAPI, XML, XSD) to modify, orchestrate, or add caching.
Tuxedo3.5.0NoTuxedo services via .jolt interface files (Jolt client 8.1).
Graphtalk4.5.1NoGenerate Java entities from Graphtalk XML files.
File4.5.7YesOne-way connector that produces XML or SWIFT payment files from XSD-driven models.
BRM4.6.0NoOracle Communications BRM via Java PCM / FList.
Kafka4.6.5YesKafka producer (push to a topic). Consume via an API/service project.
Mainframe JCL4.6.7NoExecute mainframe jobs and retrieve results via FTP; parse copybooks for record types (IDE).
CORBA IDL YesRPC CORBA calls based on IDL.
Files-SFTP
VSAM CICS YesRPC calls reading VSAM files from CICS.
Microfocus COBOL YesRPC calls to Micro Focus based on COBOL.
Active MQ YesJMS with ActiveMQ.
Heirloom CICS YesCompatibility of Java APIs migrated from COBOL using Heirloom.
ISO-8583 YesTCP with card systems over ISO-8583.
DB2 zOs DB YesMainframe DB2 stored procedures and SQL.
Postgres SQL YesPostgreSQL stored procedures and SQL.
JDE YesRPC 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).

Read more