What Integration Studio Is
(and Why It’s Different)
Integration Studio is the design-time and execution engine of OpenLegacy Hub. It
models legacy assets—programs, screens, jobs, and data—and exposes them as
modern, cloud-ready services without brittle middleware or hand-coded glue.
Metadata-driven engine
Everything you build is defined as JSON metadata, making generation and deployment fast, consistent, and CI/CD-friendly.
Middleware-free connectivity
Connect directly to mainframe, IBM i, and other legacy systems, avoiding ESB / iPaaS lock-in.
CI/CD-ready
Repeatable and governed pipeline for enterprise delivery.
No/low/full-code flexibility
Use visual flows for speed, low-code orchestration where it fits, or full-code for complex logic.
Instead of forcing you into one way of working, Integration
Studio keeps your options open.
What You Can Build
with Integration Studio
Integration Studio gives you a single place to build, secure, and deliver
modernization-ready services from legacy programs, screens, and data.
Modern APIs & Services
- REST, SOAP, Kafka, MQ, gRPC, event streams.
- From CICS/IMS transactions, COBOL/RPG programs, 3270/5250 screens, and legacy databases
Deploy Anywhere
- On-prem, hybrid, and multi-cloud
- Kubernetes/OpenShift, serverless, or traditional app servers
- Aligns to your CI/CD pipelines (GitHub, GitLab, Jenkins, Azure DevOps).
Your Way of Working
- No-code and low-code flows for speed
- Full-code projects in Java, Node.js (and other JVM-friendly stacks)
- Contract-first, bottom-up, or auto-generated OpenAPI/AsyncAPI.
Governed & Secure by Design
- OAuth2/OIDC, mTLS, RBAC, audit logs, PII masking
- Standardized naming, versioning, and schema policies across teams.
How Integration Studio Works
A simple, repeatable pipeline that turns legacy logic into modernization-ready
services—aligned with your tools, patterns, and standards.
Connect & Discover
Securely connect to mainframe, IBM i, packaged apps, files, MQ, and databases.
Parse programs, screens, and schemas; auto-create normalized interfaces (metadata).
Preview which inputs, outputs, and dependencies you want to expose.
Model & Generate (No-/Low-/Full-Code)
Map fields and operations, apply transformations and error handling in a visual designer.
Generate services/APIs in your chosen protocol (REST, SOAP, events, gRPC, MQ) and contract style (contract-first, bottom-up, or auto-generated).
Choose your runtime (e.g., Java, .NET/C#, Node.js, Python) and reuse templates to enforce standards.
Compose & Secure
Orchestrate multiple calls into flows; add business rules and data enrichment.
Apply security: OAuth2/OIDC, mTLS, RBAC, PII masking, audit logging.
Validate with built-in tests, mocks, and sandbox calls before rollout.
Package & Deliver
Output deployment-ready artifacts: OpenAPI/AsyncAPI, containers, Helm/YAML, serverless bundles, or gateway configs.
Drop into CI/CD, promote through environments, and integrate with APIM, gateways, iPaaS, and event platforms.
Observe usage and health; iterate services without touching the legacy code.
Pattern-Aware by Design.
From Integration to Migration
Integration Studio isn’t “just integration.” It’s built to implement OpenLegacy’s modernization patterns
— so the services you generate today become the bridge for safe, phased migration tomorrow.
With Integration Studio you can:
Internal Decoupling
Replace program-to-program calls with APIs so refactored modules (e.g., Java/.NET services) can still call COBOL/RPG programs—and vice versa.
External Decoupling
Front MQ, CTG, IMS Connect, and other gateways with API adapters, so legacy channels keep working while back-end logic moves to the cloud.
Data Layer Decoupling
Extract embedded SQL, route calls through standard data APIs, and gradually move data from DB2/VSAM to modern databases.
Together with Modernization Planner, Integration Studio powers the “Integration Factory” in a dual -
factory model—building the safe integration and decoupling layer that lets your “Migration Factory”
rehost, refactor, or rewrite at its own pace, with full coexistence between legacy and cloud.
Where Integration Studio
Delivers the Most Value
API-Enable Core Transactions
Expose CICS/IMS, COBOL, and RPG transactions as REST/gRPC services for mobile apps, partner portals, and open banking/open insurance initiatives.
Stream Legacy Data into Analytics & AI
Combine Integration Studio with CDC/ETL utilities to push mainframe and IBM i data into Kafka, cloud data lakes, and AI platforms—without shutting down existing systems.
Safe Migration Support (Phased Modernization)
Implement internal and external decoupling patterns so refactored or rehosted modules can continue to communicate with what remains on the mainframe or IBM i—no big-bang cutover required.
Modern Developer Experience for Legacy Backends
Give modern dev teams a familiar, CI/CD-friendly way to work with legacy systems—versioned projects, test automation, and API contracts instead of green-screen integrations.
Integration Studio Within
the OpenLegacy Hub Suite
OpenLegacy Hub
Is the Legacy Modernization Platform that delivers structured, risk-free, phased modernization.
Modernization Planner
Visualizes dependencies, identifies decoupling points, and structures modernization into phased waves.
Integration Studio
Builds and runs the integration and decoupling layer—modernization-ready services that keep legacy and cloud working together throughout the journey.
Ready to Turn Legacy into
Modernization-Ready
Services?
Integration Studio gives your teams a safe, automated way to expose legacy systems as secure, cloud-ready services—while laying the groundwork for phased modernization and migration.
