Proxy Transactional Context for Software Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Integrating software solution units, such as on-premise and on-demand solutions, poses a challenge as storing data from one unit in another disrupts the transactional context, potentially altering or losing data.
Innovation Solution
The integration of software solution units is achieved through the generation of a proxy transactional context, which allows for the mixing of transactional data without disrupting the original context, using techniques like remote function calls and proxy data objects to maintain data integrity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If data from one software solution unit is stored in another software solution unit to improve integration and data sharing, then the efficiency and effectiveness of supply chains is improved, but the transactional context of the source software solution unit is disrupted, potentially causing data to be altered or lost
Solution Approach 1:
The patent introduces a proxy transactional context as an intermediary mechanism between the source and target software solution units. This proxy context acts as a mediator that receives data from the source unit, maintains its transactional context intact, and then transfers the data to the target unit. The proxy transactional context includes proxy business objects that mirror the original business objects, allowing data to be shared without directly disrupting the source unit's transactional context.
Solution Approach 2:
The patent segments the data transfer process into distinct components: the original transactional context, the proxy transactional context, and the target context. By dividing the integration process into these separate segments, each with its own transactional context, the system allows data sharing while preserving the integrity of each segment's original context. The proxy business objects are separate from but linked to the original business objects.
2Adaptability or versatility
If software solution units are integrated to enable data sharing and improve business application effectiveness, then the adaptability and versatility of the system is improved, but the complexity of managing transactional contexts across different units increases
Solution Approach 1:
The patent creates proxy business objects that are copies or representations of the original business objects. These proxy objects replicate the structure and data of the originals but exist within the proxy transactional context. This copying approach allows the system to work with multiple representations of the same data without the complexity of managing direct references across different transactional contexts.
Solution Approach 2:
The proxy transactional context serves as an intermediary layer that simplifies the integration process. Instead of directly managing complex relationships between multiple transactional contexts, the system uses the proxy context as a standardized interface. This intermediary abstracts the complexity, making the integration process more manageable while maintaining adaptability.
Data Source
AI summary
In one embodiment, a proxy transactional context corresponding to a transactional context of a first software solution unit is generated. Further, a business object of a second software solution unit corresponding to the proxy transactional context is retrieved. Furthermore, the assignment of the retrieved business object to a business object of the first software solution unit is defined and the defined assignment is stored in the proxy data object. The proxy transactional context may be accessed using a remote function call and upon executing the proxy transactional context, the program returns to the transactional context. Thereby, the first software solution unit is integrated with the second software solution unit without disrupting the transactional context of the first software solution unit.