Unlock the Power of Low Code and Full Code Automation

Unlock the Power of Low Code and Full Code Automation

Table of Contents:

  1. Introduction
  2. Scenario 1: Low Code Banking Service 2.1 Cleaning up the Environment 2.2 Creating a Module 2.3 Testing Connections to the Backend System 2.4 Adding Assets to the Module 2.5 Testing the Assets 2.6 Pushing the Module to the Open Legacy Hub 2.7 Creating a Project 2.8 Generating a Low Code Service 2.9 Adding Entry Points 2.10 Running the Generated Application
  3. Scenario 2: Full Code Insurance Service 3.1 Cleaning up the Environment 3.2 Creating a Module 3.3 Testing Connections to the Backend System 3.4 Adding Assets to the Module 3.5 Testing the Assets 3.6 Pushing the Module to the Open Legacy Hub 3.7 Creating a Project 3.8 Generating a Full Code Service 3.9 Running the Generated Application
  4. Conclusion

Introduction

In this article, we will explore how to generate two services from Oracle stored procedures and queries using automation scripts in Open Legacy. These services will be Java Spring Boot applications, with one of them being low code and the other being full code. We will discuss the differences between them and demonstrate the steps involved in generating both services. So let's dive in and see how Open Legacy simplifies the process of creating REST APIs for your legacy systems.

Scenario 1: Low Code Banking Service

2.1 Cleaning up the Environment

Before we begin generating the low code banking service, it is essential to clean up the environment by deleting any existing records and modules in the Open Legacy Hub. This best practice ensures a clean slate for our automation scripts.

2.2 Creating a Module

In the Open Legacy Hub, a module is a collection of assets associated with a specific backend platform, connector, and business domain. We will Create a module called "Account Oracle" for our low code banking service, which will use the built-in Open Legacy connector to Oracle.

2.3 Testing Connections to the Backend System

Once the module is created, we need to test the connections to the backend system. This step ensures that the connectivity is established and allows us to proceed with adding assets to the module. We provide the Relevant credentials such as the driver class name, URL, username, and password to establish the connection.

2.4 Adding Assets to the Module

Assets in Open Legacy refer to the internal representation of operations in the backend system. In our case, we will add several CRUD operations for banking accounts to the "Account Oracle" module. These operations include updating, deleting, and retrieving accounts Based on specific criteria.

2.5 Testing the Assets

Before proceeding further, we need to test the assets we added to the module. We can define input parameters using a JSON file containing account information. The successful response to these tests provides us with valuable insights into the functionality of the generated services.

2.6 Pushing the Module to the Open Legacy Hub

Once the assets are created and tested successfully, we can push the "Account Oracle" module to the Open Legacy Hub. This ensures that the module is stored securely and ready for use in the subsequent steps.

2.7 Creating a Project

In the Open Legacy Hub, a project is a collection of modules related to the overall purpose of the project. We create a project referencing the "Account Oracle" module we just created. This project defines the business logic exposed as methods of a contract and is independent of any specific software development language or technology.

2.8 Generating a Low Code Service

With the project created, we can now generate a low code service based on the project. The service implements the business logic contained in the project and is generated using the appropriate generator, in this case, "Spring Java REST." This generator is specifically designed to create a Java Spring Boot REST low code application.

2.9 Adding Entry Points

To add specific business logic in the flow of the generated methods, we can use entry points. These entry points allow developers to incorporate additional logic before or after a specific event occurs within the service. They provide flexibility and customization options to enhance the functionality of the service.

2.10 Running the Generated Application

Using Gradle, we can run the generated low code application locally on port 8081. This allows us to validate the functionality of the service and ensures that it is working as expected. By exploring the Open Legacy Hub interface, we can see the modules and assets associated with our low code banking service.

Scenario 2: Full Code Insurance Service

3.1 Cleaning up the Environment

Just like in the previous scenario, we start by cleaning up the environment to ensure a fresh start. This involves deleting any existing records and modules related to the full code insurance service.

3.2 Creating a Module

We create a new module called "Policy Oracle" associated with the Open Legacy Oracle connector. This module will contain the assets representing CRUD operations for insurance policies in the backend system.

3.3 Testing Connections to the Backend System

To ensure connectivity to the backend system, we test the connections using the appropriate connection details. This step is crucial in establishing the foundation for adding and testing assets in the module.

3.4 Adding Assets to the Module

Similar to the low code banking service, we add assets representing CRUD operations for insurance policies to the "Policy Oracle" module. These assets are based on Oracle stored procedures and queries and enable us to Interact with the backend system efficiently.

3.5 Testing the Assets

To validate the functionality of the assets, we perform tests on each asset, providing the necessary input parameters in a JSON format. These tests cover a range of scenarios and ensure that the assets are working as expected.

3.6 Pushing the Module to the Open Legacy Hub

After the assets have been created and tested, we push the "Policy Oracle" module to the Open Legacy Hub. This ensures that the module is securely stored and accessible for further use in the generation of the full code insurance service.

3.7 Creating a Project

Similar to the low code banking service, we create a project that references the "Policy Oracle" module. This project contains the business logic for the insurance service and serves as a foundation for the subsequent steps.

3.8 Generating a Full Code Service

Using the appropriate generator, "Spring Java REST Full Code," we generate a full code service based on the project. This generator allows us to obtain a Java Spring Boot application with full code capabilities, giving developers the flexibility to implement custom business logic as needed.

3.9 Running the Generated Application

Once the full code service is generated, we can build and install the application using Maven commands. Running the application locally on the default port 8080 allows us to test its functionality and ensure that it meets our requirements. We explore the Swagger OpenAPI page to view the exposed methods and their corresponding assets.

Conclusion

In this article, we have explored how Open Legacy enables the generation of low code and full code services from Oracle stored procedures and queries. By leveraging automation scripts and predefined connectors, developers can streamline the process of creating REST APIs for legacy systems. Whether it's a banking system or an insurance system, Open Legacy provides a robust solution for modernizing legacy applications and unlocking their potential in the digital era. Choose the approach that best suits your requirements and start accelerating your digital transformation Journey with Open Legacy.


Highlights:

  • Open Legacy simplifies the process of generating services from Oracle stored procedures and queries.
  • Two scenarios: low code banking service and full code insurance service.
  • Modules and assets in Open Legacy provide a structure for organizing and managing backend operations.
  • Testing connections and assets ensures reliable and efficient interaction with the backend systems.
  • Entry points and customization options allow developers to add specific business logic to the generated services.
  • Gradle and Maven commands facilitate the building, installation, and running of the generated applications.
  • Open Legacy offers a powerful solution for modernizing legacy systems and accelerating digital transformation.

FAQ:

Q: What is Open Legacy? A: Open Legacy is a platform that enables the generation of REST APIs from legacy systems.

Q: What is a module in Open Legacy? A: A module in Open Legacy is a collection of assets associated with a specific backend platform, connector, and business domain.

Q: What is a low code service? A: A low code service is a service generated by Open Legacy that requires minimal coding effort and allows for rapid development.

Q: What is a full code service? A: A full code service is a service generated by Open Legacy that provides developers with the flexibility to implement custom business logic.

Q: Can I customize the generated services? A: Yes, Open Legacy allows developers to add specific business logic and customize the generated services according to their requirements.

Q: What programming languages are supported by Open Legacy? A: Open Legacy supports Java and Spring Boot for generating REST APIs from legacy systems.

Q: Does Open Legacy support other legacy systems apart from Oracle? A: Yes, Open Legacy provides predefined and tested connectors for various platforms and technologies, including mainframes, databases, and SAP.

Q: How does Open Legacy facilitate the modernization of legacy applications? A: Open Legacy simplifies the process of exposing legacy system functionality via REST APIs, enabling seamless integration with modern applications and systems.

Most people like

Find AI tools in Toolify

Join TOOLIFY to find the ai tools

Get started

Sign Up
App rating
4.9
AI Tools
20k+
Trusted Users
5000+
No complicated
No difficulty
Free forever
Browse More Content