Messaging Capture Adaptor for Heterogeneous Database Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems lack a real-time means to integrate data transactions from one system to another, especially when the target system is unknown or needs transaction recovery, as there is no means to restore consumed messages, leading to integration challenges across heterogeneous databases.
Innovation Solution
A system and method for real-time conversion of JMS message data into database transactions, which are stored as persistent trail files and can be applied to multiple heterogeneous databases, using a messaging capture adaptor that connects to messaging systems, parses data formats like XML, fixed width, and delimited data, and supports transactional semantics without requiring custom code.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If custom software code is developed to read data from message queue and apply it to the second system, then data integration between heterogeneous systems is achieved, but device complexity and development time increase significantly
Solution Approach 1:
The patent introduces a messaging capture adaptor as an intermediary component that sits between the message queue and the target database system. This adaptor automatically captures messages from the queue, converts them into database transactions, and applies them to the target system without requiring custom integration code. The adaptor serves as a universal mediator that handles the complexity of heterogeneous system integration internally, exposing a simple interface to users.
Solution Approach 2:
The messaging capture adaptor is designed as a universal component that can work with multiple different message queue systems and multiple different target database systems through configuration rather than custom coding. It provides multi-functional capabilities including message capture, format conversion, transaction creation, and error handling in a single standardized component that serves various integration scenarios.
2Productivity
If messages are consumed from the message queue, then data processing occurs in real-time, but the ability to recover or retransmit transactions is lost
Solution Approach 1:
The system performs preliminary action by capturing and converting messages to database transactions before the messages are consumed from the queue. The messaging capture adaptor intercepts messages while they are still in the queue, converts them to transaction format, and stores them in a persistent trail file. This preliminary conversion ensures that even after message consumption, the transaction data remains recoverable from the trail file for retransmission if needed.
Solution Approach 2:
The system implements a mechanism where message data is recovered and preserved in an alternative form. When messages are consumed from the queue, their content has been previously captured and converted to transactions stored in the trail file. If recovery is needed, the system can re-read the original messages from the queue (if not yet consumed) or reconstruct transactions from the trail file, enabling recovery without retaining the original message objects.
3Reliability
If data is converted to database transactions and stored in persistent trail files, then transaction recovery and retransmission are enabled, but storage requirements and processing overhead increase
Solution Approach 1:
The system creates a copy of the message data in a different format rather than storing the original messages. The messaging capture adaptor converts message content into database transaction representations and stores these copies in the trail file. This copying approach enables recovery capability while using storage efficiently, as the transaction format is typically more compact and standardized than raw message formats. The trail file contains only the essential transaction data needed for reapplication, not the complete message payload.
Data Source
AI summary
A system and method for performing real-time conversion of data which is present in the form of messages on JMS-compliant or other messaging systems into database transactions; which can then subsequently be applied to multiple heterogeneous databases or other systems. In accordance with an embodiment, the invention provides a means by which data can be read from messages in a messaging system, and converted to a set of database operations that are then stored as a persistent trail file. The operations can then be routed via a network and applied to target systems as required, for example to maintain a replicated set of information at one or more different or heterogeneous systems. The data in the message can be formatted in a variety of ways, for example, as fixed width, delimited, or XML data, and the system can be configured to convert this data as appropriate.