Transaction Manager Proxying via Application Program

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In modern service-oriented architecture (SOA) models, transaction managers (TM) and resource managers (RM) are often separated into distinct entities, leading to the need for TM to maintain separate credentials and network connections for each RM, resulting in significant expense and overhead.

Innovation Solution

Implementing a proxying approach that allows the TM to call back to the RM via an application program, eliminating the need for TM to maintain authentication/authorization credentials for each RM and to establish direct connections.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If TM maintains separate credentials and network connections for each RM in a service-oriented architecture, then direct communication between TM and RM is enabled, but resource overhead and operational complexity increase significantly

Engineering Contradiction:
Improvecommunication reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The application program serves as an intermediary between the transaction manager and resource manager. Instead of the TM directly connecting to each RM, the TM communicates through the application program which then interacts with the RM. This mediator pattern eliminates the need for TM to maintain separate credentials and connections for each RM, reducing system complexity while maintaining communication reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The application program is designed to perform multiple functions: it acts as both the business logic layer and the communication intermediary. By making the application program universal and multi-functional, it can handle communications with multiple different RMs using a single set of credentials and connections, thereby reducing the overall number of connections and credentials needed in the system.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If TM maintains separate credentials for each RM, then authentication and authorization are ensured, but operational costs and maintenance overhead increase

Engineering Contradiction:
Improvesecurity reliabilityVSAvoidoperational overhead
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The application program acts as a security intermediary that holds the credentials to RM on behalf of the TM. This single set of credentials in the application program replaces the need for multiple credential sets that would otherwise be required in the TM, maintaining security authentication and authorization while significantly reducing the operational overhead of managing multiple credentials.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The credentials and connection management functions are merged into the application program rather than being distributed across multiple TM-RM connections. By consolidating credential storage and connection management in a single location (the application program), the system reduces the overhead of maintaining multiple separate credential sets while preserving security through the intermediary's controlled access.

Inventive Principle:
Principle #5Merging (Combining)

3Productivity

If direct connection between TM and RM is established, then transaction coordination is streamlined, but infrastructure cost and resource burden increase

Engineering Contradiction:
Improvetransaction processing efficiencyVSAvoidresource consumption
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The application program serves as a communication mediator that enables transaction coordination without requiring direct TM-RM connections. The TM sends transaction coordination messages to the application program, which then forwards them to the appropriate RM. This intermediary approach maintains transaction processing efficiency by preserving the coordination flow while eliminating the need for multiple direct physical connections, thereby reducing infrastructure costs and resource consumption.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12267403B2Method and system to implement proxying for operations through an application program for a transaction manager
Publication Date: 2025.04.01 ORACLE INT CORP
  • US12267403B2 patent drawing
  • US12267403B2 patent drawing
  • US12267403B2 patent drawing

AI summary

Disclosed is an improved approach to implement the XA architecture, which permits a TM to call back to a RM via an AP. This approach avoids the need for the TM to maintain authentication/authorization credentials for each RM that will be contacted by the TM. This approach therefore also eliminates the need to establish a direct connection between the TM and the RM. An approach is also provided to integrate a traditional XA application with an XA transaction.