Integration Extensions for Dynamic Application Data Exchange
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional integration of computer programs is complex and labor-intensive due to specific nuances in existing integration capabilities, making it difficult to facilitate seamless data exchange between applications.
Innovation Solution
A central integration platform with connectors that utilize process extension APIs to generate data by abstracting complex integration logic, and system extension APIs to provide discovery data, enabling dynamic integration and extending native API capabilities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If conventional integration capabilities are used, then data exchange between applications can be achieved, but the integration process becomes complex and labor-intensive
Solution Approach 1:
The patent introduces a connector as an intermediary component that mediates between applications and the data lake. The connector includes system extension APIs that provide discovery data about available resources and process extension APIs that enable data operations. This intermediary layer abstracts the complexity of direct application-to-application integration, allowing applications to interact with the data lake through standardized interfaces rather than requiring complex point-to-point integration logic.
Solution Approach 2:
The connector is designed as a universal integration component that can serve multiple applications and data sources simultaneously. The system extension APIs provide general discovery capabilities that work across different applications, while process extension APIs offer standardized data operations that can be applied to various data types and sources. This multi-functional design eliminates the need for duplicate integration logic for each application pair.
2Adaptability or versatility
If integration logic is implemented for each application pair, then specific integration requirements are met, but duplicate logic must be implemented across multiple applications
Solution Approach 1:
The patent extracts common integration logic from individual application implementations and consolidates it into the connector component. The system extension APIs extract discovery functionality, while process extension APIs extract data operation functionality. This extraction allows the same integration logic to be reused across multiple applications without duplication, improving productivity while maintaining adaptability through the standardized API interfaces.
Solution Approach 2:
The connector performs preliminary actions by providing discovery data through system extension APIs before actual data operations are needed. This discovery data includes information about available resources, data schemas, and supported operations. By performing this preliminary setup and information gathering centrally in the connector, the system avoids repeating these actions in each application, thereby improving integration efficiency while maintaining flexibility.
3Productivity
If native APIs are used directly, then application-specific functionality is accessed, but integration becomes labor-intensive and complex
Solution Approach 1:
The process extension APIs serve as an intermediary layer between applications and native APIs. Instead of applications directly calling native APIs of other applications (which would require complex integration logic), the process extension APIs provide standardized data operations that internally utilize the appropriate native APIs. This mediator layer simplifies the ease of operation while maintaining productivity by efficiently leveraging the underlying native API capabilities.
Data Source
AI summary
Systems and methods for integration of applications are provided. A request for data associated with a second application is received from a first application. The data associated with the second application is generated using one or more process extension APIs. The one or more process extension APIs generate the data using one or more native APIs of the second application. The data is transmitted to the first application.