Book a demo
Glowing cyan connector hub with source shapes and outgoing endpoint channels

OL Integration

Legacy logic to APIs and events

Turn the programs, transactions, screens, and data that run your business into tested APIs and events, published as REST, Kafka, IBM MQ, SOAP, and more.

Talk to us Explore the product

How it works

Connect, design, then publish

01Connect

Backend operations become tested assets

Create a module for a connector, bind a connection, and add assets from the live system or from source: a COBOL program, a stored procedure, a BAPI, a REST operation, or a 3270 or 5250 screen. Each asset is versioned and testable.

02Design

A contract and flows on top

Build the contract from assets, an imported OpenAPI or WSDL, or a recorded terminal trail, and let AI add readable names and descriptions. Orchestrate the backend calls on a visual flow canvas.

03Publish and operate

One design, many endpoints

Generate the same contract as OpenAPI, Kafka, serverless, SOAP, IBM MQ, file, or DB poller endpoints, test it in Test Center or CI, deploy it, and watch it in Grafana dashboards.

Key features

From a backend operation to a running, monitored service

01 / IBM Z

Mainframe connectors

CICS through the OpenLegacy adapter or CICS Transaction Gateway, IMS, Natural, DB2 for z/OS, VSAM, 3270 screens, Micro Focus COBOL, and Heirloom CICS.

02 / IBM I

IBM i connectors

Program calls from RPG, COBOL, or PCML, 5250 screens, data queues, DB2 for i, and JD Edwards business functions.

03 / ENTERPRISE

SAP, Oracle, and SOAP

SAP BAPIs through JCo, Oracle stored procedures over JDBC, and existing SOAP services imported from WSDL.

04 / ASSETS

Versioned, testable assets

Each backend operation is an asset with typed input and output trees. Methods pin an asset version and are upgraded deliberately when it changes.

05 / CONTRACT

Contract-first, friendly APIs

Design the contract as the API, then enrich it with AI: readable names, descriptions, and auto-mapping that people and agents can use.

06 / RPC FLOWS

Visual flow orchestration

Invoke program, database, SOAP, REST, and messaging assets with mapping, conditions, for-each, parallel paths, and reusable subflows.

07 / SCREENS

Terminal journeys as methods

Automate 3270 and 5250 journeys: identify the screen, send a key, capture fields, branch, and reuse login or navigation as a subflow.

08 / ENDPOINTS

Multi-technology endpoints

One contract generated as OpenAPI, Kafka, serverless, SOAP, IBM MQ, file, or DB poller, with each technology's settings kept when you switch.

Video / Contract with AI

Create a project and an auto-generated contract

A CICS accounts module holds RPC assets for create, read, update, delete, and list. The module is added to a new accounts API project, and Create Contract generates it automatically, with AI enriching the descriptions and input and output metadata before the contract is created.

Contract-first and friendly APIs Request a demo

Events from the source

Database pollers and IBM i change data capture

A DB poller runs a SQL query on Oracle, SQL Server, DB2 for z/OS, or DB2 for i on a schedule and sends each new or flagged row through a flow. IBM i CDC reads the journal for selected tables, by table or by committed transaction, and turns each insert, update, and delete into JSON a flow can send to Kafka, REST, or another step.

IBM i change data capture

AI and MCP

The same operations, as agent tools

AI generates enriched contracts, suggests field names and descriptions, auto-maps contracts to assets, and assists in the Designer. Published APIs can be installed in OL Gene as agent tools, so AI agents and MCP clients call the same governed operations under organization credentials.

See OL Gene

Video / Generate the service

Publish contract methods and generate a no-code REST service

The CICS accounts contract lists list, get, create, update, and delete methods. The methods are published from the contract task list, Generate Service selects the container REST generator, and the solution page explains deploying the contract as an OpenAPI REST service.

Multi-technology endpoints RPC flow methods

Test and automate

Test plans in Hub or CI, and a CLI for the pipeline

Test Center runs ordered plans built from saved flow test cases, from the Hub UI or from CI, and keeps the history of every run. The ol CLI creates modules, pushes metadata, tests assets, generates services, and deploys from scripts, so the path from a legacy asset to a running service can be repeated without the UI.

CLI for automation

Operate

Grafana dashboards for deployed APIs

Runtime metrics and logs for deployed APIs appear in Grafana, embedded in Hub and scoped by tenant, project, environment, and instance, so teams can check whether a published API is healthy in test and production from the same runtime view.

Runtime dashboards

Video / Testing

Test a contract method with cases and assertions

Selecting the list-accounts method runs a flow test and shows the JSON response. A named test case is saved with its input JSON and optional variables, and an HTTP 200 status assertion is added so the case can be replayed from Test Cases.

Test Center Asset management

At a glance

Design once, publish the way each consumer needs

7

Endpoint technologies

OpenAPI, Kafka, serverless, SOAP, IBM MQ, file or SFTP, and DB poller.

2

Flow types

RPC flows for program and data calls, Screens flows for 3270 and 5250 journeys.

4

DB poller sources

Oracle, SQL Server, DB2 for z/OS, and DB2 for i.

2

Ways to run tests

From the Hub UI or from CI with the ol CLI, with history kept for both.

ECOSYSTEM
Connectors for the systems you already run

Legacy and on-prem backends on one side, APIs, events, and agents on the other.

CICS / CTG
IMS
DB2 / VSAM
IBM i (RPG / PCML)
3270 / 5250
SAP BAPI
Oracle
SOAP / WSDL
IBM MQ
Kafka
Grafana
OL Gene

FAQ

Common questions

Which backends can OL Integration connect to?

IBM Z (CICS, IMS, Natural, DB2, VSAM, 3270 screens, Micro Focus COBOL, Heirloom CICS), IBM i (RPG, COBOL, PCML, 5250 screens, data queues, DB2 for i, JD Edwards), SAP, Oracle, SOAP, and other connectors including IBM MQ, Kafka, ActiveMQ, REST and OData, JDBC, files and SFTP, ISO-8583, Temenos T24, Tuxedo, and CORBA.

Can one integration be published in more than one way?

Yes. You design the contract and flows once, then generate them as OpenAPI, Kafka, serverless, SOAP, IBM MQ, file, or DB poller endpoints. Each technology keeps its own settings when you switch.

What happens when a backend program changes?

Editing an asset creates a new version. Methods stay pinned to the version they use until you upgrade them, and Hub offers to move methods forward after the save.

Can AI agents use the APIs?

Yes. Published APIs can be installed in OL Gene as agent tools, so AI agents and MCP clients call the same governed operations under organization credentials.

Can we automate it in CI/CD?

Yes. The ol CLI creates modules, pushes metadata, tests assets, generates services, and deploys, and Test Center plans can be run from CI.

Videos

Tell us about yourself

You've been browsing the catalog. Leave your details to keep exploring.

Privacy policy