Integration Framework Handling Future Effective Dates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing integration technologies lack flexibility and guidance in developing and maintaining point-to-point integrations between applications, leading to high development and maintenance costs, with no facility to manage licensing and activation of integration software, and do not handle data with future effective dates effectively.
Innovation Solution
A computer system is programmed to prepare and transmit initial messages omitting data with future effective dates, storing this data until the specified date, then automatically generating and transmitting new messages when the data becomes effective, using an integration framework that checks for and processes effective dates to ensure timely publication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If point-to-point integration software is used to transfer data between applications, then data exchange between applications is achieved, but development and maintenance costs increase due to lack of flexibility and guidance
Solution Approach 1:
The patent introduces an integration framework that acts as an intermediary between applications and point-to-point integration software. This framework provides standardized interfaces, management capabilities, and guidance mechanisms that simplify integration development while reducing the complexity of managing multiple point-to-point integrations. The framework mediates the interaction between applications and integration software, offering a layered architecture that abstracts complexity.
Solution Approach 2:
The integration framework is designed to be universal, supporting multiple integration scenarios and applications through a common platform. It provides multi-functional capabilities including integration development guidance, deployment management, licensing control, and maintenance support, replacing the need for separate specialized tools for each integration task.
2Reliability
If manual point-to-point integration setup is used, then data transfer between specific applications is achieved, but maintenance costs increase due to frequent changes required
Solution Approach 1:
The integration framework introduces dynamic configuration capabilities that allow integration settings to be modified without requiring manual code changes or system reconfiguration. The framework supports runtime adjustments, version control, and automated deployment of integration changes, making the system adaptable to frequent business requirements changes while maintaining stability.
Solution Approach 2:
The framework provides preliminary action mechanisms including pre-configured integration templates, automated validation rules, and change management workflows that prepare and guide maintenance activities before they are executed. This reduces the complexity of maintenance by having structures and processes in place beforehand.
3Ease of operation
If static user interface is used for integration management, then system control is achieved, but flexibility for dynamic changes is reduced
Solution Approach 1:
The user interface is transformed from static to dynamic, allowing real-time monitoring and configuration of integration processes. The interface adapts to user needs and system state, providing contextual information and enabling runtime modifications to integration settings without requiring system shutdown or manual intervention.
Solution Approach 2:
The interface adds temporal and interactive dimensions to integration management, transitioning from a fixed, predetermined control mechanism to a flexible, real-time control system that responds to user actions and system events dynamically.
4Speed
If synchronous messaging is used for real-time integration, then real-time data exchange is achieved, but processing speed decreases due to waiting for responses
Solution Approach 1:
The framework implements periodic polling mechanisms combined with event-driven architecture, where the system periodically checks for messages and events rather than continuously waiting for responses. This allows the system to maintain real-time responsiveness while reducing idle waiting time by switching to asynchronous processing when appropriate.
Solution Approach 2:
The integration framework acts as a mediator that manages message routing and response coordination, enabling the system to optimize between synchronous and asynchronous messaging based on the specific integration scenario, thereby reducing unnecessary waiting time while maintaining real-time capabilities where needed.
Data Source
AI summary
A computer receives records to be published to a target application, including at least one record identified as not effective until a specified date in future. The target application is unable to delay processing of the identified record(s) until after the specified date. Hence, the computer is programmed, e.g. by a software developer extending predefined classes, to initially prepare and transmit to the target application, an outgoing message based on records that are not future dated, while omitting a new record to be effective in future. The computer stores the omitted data in a store of data to be published in future. The computer is pre-programmed to automatically respond to a date for data in the store becoming current, by preparing and transmitting a new version of the outgoing message, based on to-be-published data from the store, and based on a current version of previously published data if needed.