Products / OL Integration
OL Integration
Turn mainframe, IBM i, and on-prem programs, transactions, screens, and databases into tested APIs and events: connect, design contracts and flows, generate, deploy, and monitor without changing the host.
OL Integration turns business logic that already runs on mainframe, IBM i, and long-running on-prem systems into typed APIs and events, without changing the host. Teams connect a backend, capture its programs, transactions, screens, and database operations as tested assets, design a contract and flows on top of them, then generate, deploy, and monitor the resulting service. The same design can be published as REST, Kafka, IBM MQ, SOAP, serverless, or file endpoints.
Key Features
-
API
Asset ManagementDiscover, version, and test connector assets inside a module. An asset is the metadata for one legacy operation that a method invokes.
-
API
CLI for AutomationAutomate Hub with the `ol` CLI: create modules, push/pull metadata, test assets, generate services, and deploy from CI.
-
AI
Contract-First & Friendly APIsDesign the Hub contract as the API, then add readable names, descriptions, and examples so people and agents can call it.
-
API
Database pollerPoll Oracle, SQL Server, DB2 for z/OS, or IBM i DB400 on a schedule, send each result row through a method flow, and optionally update or clear rows afterward.
-
API
IBM i (AS/400) connectorsPublish IBM i programs, 5250 screens, data queues, DB2 for i, and JD Edwards functions as APIs.
-
API
IBM i Change Data CaptureRead IBM i journal entries for selected DB2 tables and run a method flow for each insert, update, and delete.
What it enables
OL Integration turns business logic that already runs on mainframe, IBM i, and long-running on-prem systems into typed APIs and events, without changing the host. Teams connect a backend, capture its programs, transactions, screens, and database operations as tested assets, design a contract and flows on top of them, then generate, deploy, and monitor the resulting service. The same design can be published as REST, Kafka, IBM MQ, SOAP, serverless, or file endpoints.
Part of the OpenLegacy platform
Run it from one governed plane
Govern, deploy, and operate this product with the rest of the suite — managed or on-prem.