Concept & Architecture

OpenLegacy creates REST APIs and SOAP services for a variety of backends, quickly, simply and flexibly.

Open

First, OpenLegacy provides a collection of connectors that allow communicating and working with the backend using a simple Java SDK.
This Java API comprises of a combination of connectors and Java models (also called entities), describing backend resources relevant for the operation. For example, an entity can describe the input and output parameters of a legacy program, so that using a connector to this legacy system, we can invoke the program, knowing what to send and what we expect to receive, in a single line of Java code.
To create these entities, OpenLegacy provides automatic tools to analyze and generate them automatically from the legacy resource, whether it is legacy source code, a trail file describing terminal screens, or even a direct connection to the database.

After creating one or more Java SDKs for the relevant backends, we can create the external API (REST API or SOAP services).
OpenLegacy provides tools to automatically create these APIs, in either a Contract First approach (top-down) or a Contract Last approach (bottom up), using the existing models from the internal Java API.
Either way, the API can be modified and customized, using graphical editors or by modifying the generated Java code directly.

The result is a Java project that can be deployed to any supported Java Web Server with a fully working API, including an API catalog and test page allowing the API to be documented, tested and delivered.

Finally, OpenLegacy generates the API in a project template containing all the necessary configurations and components to function as a small microservice in a larger microservices ecosystem.
By doing so, it supports higher-level management tools that allow the API to be easily secured, analyzed, and optimized.

Open