In just minutes, you can automatically extract strong-type metadata from any core system to create a standard Java API that includes the business logic.
Types of Core (Legacy) Connectors - The Java API is a single line of code combining the connector and Java models (also called entities). An entity can describe the input and output parameters of core (legacy) systems such as applications, mainframe/midrange servers, databases and SOA/ESB services. Entities can invoke the program, knowing what to send and what we expect to receive.
Connector Automation - You can analyze and generate entities automatically from the target system, whether it is legacy source code, a trail file describing screens, or even a direct connection to the database.
Using built-in templates and wizards, automatically extend back-end entity objects into web or mobile applications, REST APIs or SOA web services.
API Modeling & Configuration - Automatically create the external API in a contract first approach (top down) or using the existing models from the internal Java API. The API can be customized with graphical editors or modified directly. This Java project can be deployed as a fully working API to any supported Java Web Services. The API includes an API catalog and test page allowing the API to be documented, tested and delivered.
Eclipse-based IDE - Available as a plug-in or stand-alone installation, not only does our IDE provide a graphical interface to create and configure APIs, but it also generates Java code behind the scenes. No special skills or training are required and it’s easy to alter or add to your code for more complex or custom projects.
Orchestration - in addition to basic projects where there is one front-end and one back-end, you can orchestrate integrations to any number of back-ends. Unlike traditional approaches, our API software uses dependency-based orchestration allowing much greater flexibility and simplicity in implementation.
Inject multiple layers of security and accelerate performance. If needed, edit the metadata to create a custom solution.
Secure Architecture - Since artifacts are Java, they inherently feature strong-type security so no software-based validation layers are needed. By comparison, other vendor approaches use SOAP to REST, resulting in JSON - a weak-type protocol.
Secure Identity - OAuth2 separates the roles of the client and resource owner, thus allowing secure token-based, profile-defined access to resources. A built-in data-masking wizard, can mask any core (legacy) data source to provide only specific data needed for a specific service. Other data will not be exposed. Identity management authentication supports OLAP but also can connect to an LDAP directory.
Performance - Unlike other approaches, we’re architected for speed. OpenLegacy’s architecture flattens the entire integration process and provides a self-contained, automatically generated micro-application that encapsulates everything needed for the service. Back-end caching allows multiple APIs to benefit from a single caching source. Also the underlying Java API layer enables internal orchestration to occur quickly and easily.
One-click deployment means the API can easily be consumed and re-used by any java developer for any digital service. Innovate anytime, anywhere.
Flexible Deployment Options - including on-premise, Cloud, or any J2EE server or Docker container. Deploy to a developer portal using Swagger.
Run-time Platform - The OpenLegacy APi software server is installed locally and provides the LightWAR infrastructure required to run the new API projects efficiently, plus the Management Console provides real-time performance monitoring and analytics.
Hybrid Cloud Integration - Designed to connect anything, anywhere. Front-end SOAP and REST services generated from your legacy, on-premise systems are seamlessly integrated with cloud-based applications. Leverage existing data and functionality within new business models (SaaS, PaaS, BYOD, Bid Data, etc.) at a fraction of the cost and time required to develop new systems.
Microservices - OpenLegacy provides an automated and standard way to functionally decouple a monolithic core application through the OpenLegacy Microservices Edition. Unlike other approaches, you can consume legacy applications as a data-store without touching the system.
Our API software helps you keep your pace with built-in JUnit testing and continued testing in run-time.
Continuous Improvement - Automatically perform testing in both build-time and run-time for quality assurance and continuous improvement before, during and after deployment. This is especially important for core (legacy) system APIs supporting mission critical processes and millions of transactions.
Easily manage your APIs, monitoring who is using them, how they are used and where they are used.
Management Console - Invoked from the OpenLegacy server as part of run-time functionality, the console enables real-time monitoring of the performance and behavior of the project.
Monitoring - Console tabs cover: Users, Roles and Role Reports, API Management, API Usage, Services Usage, RESTful Services, Properties, Logs and Caching.
Analytics - Follow the entire ‘back and forth’ journey of each message, from endpoints to back-end. Observe internal and external usage, including the number of calls, duration, date etc.
Of course, diagrams can often oversimplify a process. However, this is pretty much how easy it is to use our API software. And we have quick and easy Services engagements that help with the Discovery process required before the API can be created.