Dynamic Transaction Coordinator for Hybrid Enterprise Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In a hybrid Enterprise Information System environment, integrating Java EE and non-Java EE applications in a cloud computing setting is complex due to the need for global transaction support and security across heterogeneous middleware environments, leading to increased latency and complexity in transaction coordination.
Innovation Solution
A method where a first computer generates a unique transaction identifier and associates a dynamic coordination flag, allowing any participating computer to act as the coordinator for transaction processing, enabling flexible coordination and reducing the need for substantial changes to existing systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional transaction coordination methods are used in hybrid EIS environments, then global transaction support is provided, but system complexity and latency increase significantly
Solution Approach 1:
The patent segments the transaction coordination function by introducing a coordinator component that can be dynamically assigned to different participants. This separates the coordination logic from the traditional centralized model, allowing the transaction system to be divided into independent coordinator and participant roles that can be distributed across different application servers, thereby reducing overall system complexity while maintaining global transaction support
Solution Approach 2:
The patent implements dynamic coordination by allowing the coordinator role to be flexibly assigned to any participant in the transaction based on runtime conditions. This dynamic assignment mechanism enables the system to adapt to different scenarios (Java EE to non-Java EE, same-vendor, cross-vendor) without requiring complex static configuration, thus reducing coordination complexity while preserving transaction reliability
2Reliability
If multiple participants are involved in global transactions, then comprehensive transaction support is achieved, but latency increases due to numerous coordination steps
Solution Approach 1:
The patent applies preliminary action by having the coordinator establish communication channels and exchange necessary information with all participants before the actual transaction execution begins. This pre-coordination phase prepares the transaction framework in advance, allowing the actual transaction processing to proceed with minimal additional coordination overhead, thus reducing latency while maintaining comprehensive multi-participant support
Solution Approach 2:
The patent introduces a coordinator as an intermediary component that manages communication between multiple participants. This intermediary consolidates the coordination logic, allowing participants to interact through a standardized interface rather than requiring direct peer-to-peer coordination, which reduces the number of coordination steps and associated latency while supporting comprehensive multi-participant transactions
3Adaptability or versatility
If Java EE and non-Java EE applications are integrated, then system versatility is improved, but transaction coordination complexity increases
Solution Approach 1:
The patent implements universality by designing the coordinator component to handle multiple types of transaction scenarios through a unified mechanism. The same coordinator can manage transactions between Java EE and non-Java EE applications, between same-vendor systems, and between cross-vendor systems, eliminating the need for separate coordination mechanisms for each scenario and thereby reducing complexity while maintaining heterogeneous environment integration
Solution Approach 2:
The patent uses parameter changes to adapt the coordination behavior to different environment configurations. By dynamically adjusting coordination parameters based on the types of applications involved (Java EE, non-Java EE, vendor-specific settings), the system can handle heterogeneous integrations with a single flexible mechanism rather than multiple rigid mechanisms, thus reducing complexity while preserving versatility
Data Source
AI summary
A first computer of a distributed computing system, which is an object-oriented enterprise based application server, receives a request for a transaction. The first computer generates a unique identifier for the transaction and associates an indicator with the transaction. The indicator indicates whether coordination of transaction processing can be performed by a second computer, of the distributed computing system, that is any application server apart from an object-oriented enterprise based application server. The first computer sends the unique identifier and the indicator to the second computer which enables the second computer to participate as the coordinator for the processing of that transaction if coordination of transaction processing is permitted to be performed by the second computer.