OpenLegacy z/OS

OpenLegacy Modernization Guide

Legacy Application/Data AccessJava and Web

OpenLegacy is a legacy application/data access product by OpenLegacy. Explore technical details, modernization strategies, and migration paths below.

Product Overview

OpenLegacy is a platform for creating microservices from legacy systems such as CICS and IMS.

Key features include automated data transformation, support for various authentication methods like LDAP and SAML 2.0, and integration with CI/CD pipelines.

Modernization Strategies

Rehost

Timeline:
6-12 months

Lift-and-shift to cloud infrastructure with minimal code changes. Fast migration with lower risk.

Refactor (Recommended)

Timeline:
18-24 months

Optimize application architecture for cloud while preserving business logic. Best ROI long-term.

Replatform

Timeline:
3-5 years

Complete rewrite to cloud-native architecture with microservices and modern tech stack.

Frequently Asked Questions

General

What is OpenLegacy and what does it do?

OpenLegacy creates microservices from legacy systems like CICS and IMS. It uses a design-time workbench to define services and a runtime engine to execute them. The platform supports web services, RESTful APIs, and JSON.

How does OpenLegacy connect to and interact with legacy systems?

OpenLegacy connects to legacy systems using standard protocols like TCP/IP and SNA. It transforms legacy data formats into modern formats like JSON. The platform uses a metadata-driven approach to map legacy data structures to microservice interfaces.

What are the deployment options for OpenLegacy?

OpenLegacy supports various deployment options, including on-premises, cloud, and hybrid environments. It can be deployed on platforms like z/OS, Linux, and Windows. The platform integrates with containerization technologies like Docker and Kubernetes.

How do you create and configure microservices with OpenLegacy?

OpenLegacy uses a design-time workbench for service creation and configuration. The workbench provides a graphical interface for mapping legacy data structures to microservice interfaces. The platform also supports command-line interface (CLI) for administrative tasks.

Technical

What types of APIs does OpenLegacy expose?

OpenLegacy exposes RESTful APIs using standard HTTP methods like GET, POST, PUT, and DELETE. API endpoints follow a resource-based pattern, such as `/customers/{customerId}`. The platform supports JSON for request and response payloads.

What programming languages and SDKs are supported for integration?

OpenLegacy supports integration with Java, JavaScript, and other programming languages through its SDKs and APIs. Developers can use the SDKs to invoke microservices and handle data transformation. The platform also supports integration with API gateways and service meshes.

What configuration files or interfaces are used?

OpenLegacy uses configuration files in YAML or JSON format to define service metadata, connection parameters, and security settings. These files are typically stored in a repository and managed through a CI/CD pipeline. The platform also provides a web-based administration console for managing configuration parameters.

What are the main system components?

The main system components include the Design Tool, the Runtime Engine, and the Connector Framework. The Design Tool is used to create and configure microservices. The Runtime Engine executes the microservices. The Connector Framework provides connectivity to legacy systems.

Business Value

What is the business value of OpenLegacy?

OpenLegacy enables organizations to modernize legacy systems without replacing them. It reduces the cost and risk of modernization by creating microservices that expose legacy functionality as APIs. The platform also improves agility and time-to-market for new applications.

How does OpenLegacy help organizations unlock the value of their legacy systems?

OpenLegacy helps organizations unlock the value of their legacy data and applications. It enables them to create new digital experiences by exposing legacy functionality as APIs. The platform also supports integration with cloud-native technologies and architectures.

What are some common use cases for OpenLegacy?

OpenLegacy supports various use cases, including mobile enablement, API integration, and cloud migration. It can be used to create mobile apps that access legacy data and functionality. The platform also supports integration with API gateways and service meshes for managing APIs.

Security

What authentication methods are supported?

OpenLegacy supports authentication methods such as LDAP, SAML 2.0, and X.509 certificates. It integrates with enterprise identity providers for user authentication and authorization. The platform also supports multi-factor authentication for enhanced security.

What access control model is used?

OpenLegacy uses Role-Based Access Control (RBAC) to manage user permissions. It defines roles with specific privileges and assigns users to those roles. The platform also supports fine-grained access control based on attributes and policies.

What encryption is used and where?

OpenLegacy uses TLS encryption for communication between components. It also supports encryption of sensitive data at rest using AES-256 encryption. The platform adheres to industry standards and best practices for security.

What audit/logging capabilities exist?

OpenLegacy provides audit logging capabilities for tracking user activity and system events. It logs events such as login attempts, configuration changes, and data access. The platform also supports integration with security information and event management (SIEM) systems.

Operations

What monitoring capabilities exist?

OpenLegacy provides a web-based administration console for monitoring system health and performance. It displays metrics such as CPU usage, memory consumption, and network traffic. The platform also supports integration with monitoring tools like Prometheus and Grafana.

What logging capabilities exist?

OpenLegacy logs events to standard output and log files. It supports different logging levels, such as DEBUG, INFO, WARN, and ERROR. The platform also supports integration with centralized logging systems like Elasticsearch and Splunk.

How is OpenLegacy deployed and managed?

OpenLegacy can be deployed on various platforms, including z/OS, Linux, and Windows. It supports containerization technologies like Docker and Kubernetes for deployment and management. The platform also provides a command-line interface (CLI) for administrative tasks.

How does OpenLegacy support automation?

OpenLegacy supports automated deployment and configuration through CI/CD pipelines. It provides APIs and command-line tools for automating tasks such as service deployment, configuration management, and testing. The platform also integrates with popular CI/CD tools like Jenkins and GitLab.

Ready to Start Your Migration?

Download our comprehensive migration guide for OpenLegacy or calculate your ROI.

Calculate ROI