Cloud Program Generation via API Wrappers for Legacy Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
It is challenging to execute on-premises machine-executable programs remotely due to their configuration for local execution, making it difficult to migrate these programs to cloud environments without significant modifications or compromises in IT landscapes.
Innovation Solution
A system and method that generates cloud-associated programs by receiving executable code, generating function code to define field categories, populating data, and creating an API to allow cloud-based applications to access and execute the data, enabling remote execution of on-premises program functions through automated source code generation and API utilization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If on-premises machine-executable programs are executed locally, then they can maintain their existing functionality and configuration, but they cannot be accessed or executed remotely in cloud environments
Solution Approach 1:
The patent introduces an intermediary system that acts as a bridge between on-premises programs and cloud environments. This intermediary generates wrapper code and API interfaces that enable remote access to local programs without modifying the core program logic, thus maintaining functionality while enabling cloud compatibility.
Solution Approach 2:
The system segments the program execution environment into distinct layers: the original on-premises program remains intact, while separate wrapper code, API interfaces, and data mapping layers are introduced. This segmentation allows the program to maintain its local execution integrity while gaining remote accessibility through the added layers.
2Adaptability or versatility
If on-premises programs are modified to execute remotely, then cloud access is enabled, but the existing program configuration and IT landscape may be compromised
Solution Approach 1:
Instead of modifying the original on-premises program, the system creates a copy or wrapper layer that interfaces with the program. This wrapper contains the remote execution logic and cloud compatibility code, while the original program remains unchanged, preserving IT landscape integrity while enabling remote access.
Solution Approach 2:
The system performs preliminary actions by generating wrapper code, API definitions, and data mapping configurations before remote execution is needed. This preparatory work establishes the cloud interface layer in advance, allowing the original program to remain untouched while pre-configuring all necessary remote access mechanisms.
3Adaptability or versatility
If manual conversion of on-premises programs to cloud-native formats is performed, then cloud compatibility is achieved, but significant time and effort are required
Solution Approach 1:
The system enables self-service conversion by automatically analyzing the on-premises program code, generating appropriate wrapper code, creating API interfaces, and configuring data mappings without requiring manual programming effort. The conversion process serves itself through automated code generation and configuration, dramatically reducing conversion time while maintaining compatibility.
Solution Approach 2:
The system changes parameters by automatically detecting program characteristics, data structures, and execution patterns, then adjusting the generated wrapper code and API configurations to match these parameters. This automated parameter adaptation enables rapid conversion to cloud-native formats without manual reconfiguration of each program's specific characteristics.
4Ease of operation
If on-premises programs are migrated to cloud environments with full modifications, then remote access is enabled, but the complexity of the migration process increases significantly
Solution Approach 1:
The system introduces a universal wrapper framework that can interface with multiple different on-premises program types through a common API structure. This multi-functional approach allows the same cloud interface layer to serve various legacy programs, reducing migration complexity by avoiding the need to create custom integration solutions for each program.
Data Source
AI summary
A method includes receiving, via a processor, first programming code associated with a legacy report that includes user-configurable data. Based on the first programming code, second programming code associated with a first function that outputs an indication of the user-configurable data is generated, as is third programming code associated with a second function that is configured to (1) receive a user input from a cloud-based application and (2) send the user-configurable data to the cloud-based application. Entity data is generated based on the second programming code, query data is generated based on the third programming code, and service data is generated based on the second programming code and the third programming code. The processor then generates fourth programming code that is associated with the cloud-based application and is configured to generate a cloud-based report that includes the user-configurable data.


