Composite System Integration via Mediator Layer for Legacy Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Integrating new systems with different communication commands, variables, and methods into existing legacy systems is time-consuming and costly, hindering quick integration and upgrades in enterprise resource planning systems.
Innovation Solution
A composite system with multiple layers, including a portal, process logic, user interface, business logic, abstraction, and connectivity layers, enables communication with external systems without reconfiguring source code by using native commands, variables, and methods recognized by the external systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If legacy systems are reconfigured to communicate with new systems using different commands, variables, and methods, then system integration is achieved, but integration time and cost increase significantly
Solution Approach 1:
The patent introduces a mediator layer (adapter or interface layer) that sits between the legacy system and the new system. This intermediary translates communication protocols, commands, and data formats between the two systems, allowing them to interact without modifying the legacy system's source code. The mediator handles protocol conversion, data mapping, and method translation, enabling seamless integration while preserving the original legacy system architecture.
Solution Approach 2:
The patent segments the integration architecture into distinct layers: the legacy system layer, an intermediary adapter layer, and the new system layer. This segmentation allows each layer to be developed, maintained, and modified independently. The adapter layer can be updated or replaced without affecting the legacy system, reducing integration time and enabling easier future upgrades.
2Adaptability or versatility
If source code is reconfigured to enable communication between systems, then system compatibility is improved, but cost and complexity increase
Solution Approach 1:
The intermediary layer encapsulates all translation and adaptation logic, preventing the need to modify legacy system source code. This approach reduces complexity by concentrating integration logic in a dedicated component that can be configured through parameters or metadata rather than code changes, making the system easier to maintain and modify.
Solution Approach 2:
The patent creates virtual representations or models of legacy system interfaces within the intermediary layer. These copies allow the new system to interact with legacy functionality through standardized interfaces without direct access to or modification of the actual legacy source code, reducing complexity while maintaining compatibility.
3Adaptability or versatility
If legacy systems are upgraded to support new workflows, then functionality is improved, but cost and time requirements increase
Solution Approach 1:
The patent segments functionality into the legacy system (which remains unchanged) and a new overlay system (accessible through the intermediary). This allows new workflows and features to be added without upgrading or modifying the legacy system, significantly reducing upgrade costs while maintaining full functionality.
Solution Approach 2:
The intermediary layer is pre-configured with translation rules, data mappings, and protocol conversions needed to support new workflows. This preliminary setup allows new functionality to be deployed quickly without costly and time-consuming legacy system upgrades, as the adaptation infrastructure is already in place.
Data Source
AI summary
Systems and methods are provided for enabling communication between a composite system providing additional functionality not contained in existing legacy systems and other existing systems using different commands, variables, protocols, methods, or instructions, when data may be located on more than one system. In an embodiment, multiple software layers are used to independently manage different aspects of an application. A business logic layer may be used in an embodiment to facilitate reading/writing operations on data that may be stored locally and/or on external systems using different commands, variables, protocols, methods, or instructions. A backend abstraction layer may be used in an embodiment in conjunction with the business logic layer to facilitate communication with the external systems. A user interface layer may be used in an embodiment to manage a user interface, a portal layer to manage a user context, and a process logic layer to manage a workflow.