Product overview

OpenLegacy is an API integration and API management software platform that accelerates the delivery of your core applications as new digital services.

OpenLegacy specializes in building digital services (APIs) for legacy applications, decoupling monolithic applications into microservices, and providing API management solutions for the run-time environment.

The OpenLegacy product is, at its core, an Integrated Development Environment (OL IDE) that builds integration projects and microservice projects using the OpenLegacy Framework.

The OpenLegacy Framework is a Java-based framework that utilizes Java industry standards and OpenLegacy's proprietary set of connectors to enable rapid integration to legacy systems for the creation of digital services (APIs).

While the OpenLegacy Framework enables developers to build standard integration projects and microservices, the IDE is packed with a full set of smart tools to automatically generate integration projects, APIs, and the microservices with it.

The current product line is 5.2 (OpenLegacy Core 5.2.x).

OpenLegacy IDE

The acceleration in delivering new digital services by integrating with core applications is possible thanks to the IDE and its tools.

The smart tools provided by the IDE analyze and parse the core systems, and generate modern APIs for selected assets of the backend. The generated products of these tools are OpenLegacy projects: standard Java projects that use the OpenLegacy framework and runtime features.

See also: Service project, Legacy connectors, Screens SDK, RPC SDK.

OpenLegacy Project

These projects are ready for deployment to container technologies such as Docker and Cloud Foundry, to cloud hosting such as AWS and Azure, and to standard Linux/Windows servers. The generated project includes a set of runtime features out of the box.

Connectors

OpenLegacy offers built-in connectors for the most common legacy backends, such as mainframes, IBM i (AS/400), and more. Custom connectors can also be provided as needed. See Connectors and Legacy connectors.

Security

All OpenLegacy APIs are configured to be secured out of the box. The security specification defines authentication and authorization of both users and applications using the API.

It is possible to choose from various options regarding the source of the users and clients: in-memory, database, LDAP, Active Directory, and authentication with the legacy backend.

Caching

Caching can improve API performance when some of the data is not frequently updated. Caching can also minimize network loads by limiting calls to the backend, and thus reduce overall costs by reducing MIPS.

Caching is defined at the project level. If enabled, you can define which data to cache and which data should be retrieved (or written) to the legacy backend. One of the advantages of OpenLegacy caching is deep caching: SDK methods under a dynamic API response can be cached individually. Cache can also be modified in a running environment.

Microservices ecosystem

One of the key features of OpenLegacy projects is the ability to orchestrate multiple core applications in a single project into a new API. Multiple legacy systems can be orchestrated into a single project, or legacy systems can be connected and integrated with modern systems.

By default, the OpenLegacy Java project template contains the configurations needed to deploy each API project separately, communicate with microservices ecosystem components, scale out, and behave as a complete microservice. See API projects — microservices.

Management Console

The OpenLegacy Management Console allows management of application APIs in a post-deployment environment. Properties for development, testing, and production can be fine-tuned without restarting the server.

---

Source: OpenLegacy Product Overview (Confluence)