Bibliographic Details
| Title: |
SYSTEM AND METHOD FOR CONVERSION OF JMS MESSAGE DATA INTO DATABASE TRANSACTIONS FOR APPLICATION TO MULTIPLE HETEROGENEOUS DATABASES |
| Document Number: |
20120023116 |
| Publication Date: |
January 26, 2012 |
| Appl. No: |
13/076253 |
| Application Filed: |
March 30, 2011 |
| Abstract: |
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 (for example, as an Oracle GoldenGate trail file). The operations, as recorded in the trail file, 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. In accordance with an embodiment, the data can be read in real-time from the messaging system, and written out as quickly as it can be consumed to the persistent trail files. In scenarios where there is no current means of integration of two systems, the invention can be used as a bridge if, for example, the source system is modified or configured to write data changes to a messaging system, and Oracle GoldenGate is used as a means of delivery to the target system. |
| Inventors: |
Wilkes, Stephen (Santa Clara, CA, US); Nielsen, Michael Scott (San Francisco, CA, US); Pora, Codin (San Francisco, CA, US) |
| Assignees: |
ORACLE INTERNATIONAL CORPORATION (REDWOOD SHORES, CA, US) |
| Claim: |
1. A system for performing real-time conversion of data present in the form of messages into database transactions which can subsequently be applied to a database, comprising: a messaging capture adaptor, which processes data received in the form of messages on a message queue at a first or source system, and communicates with an extract process to generate a trail file containing the processed data, for use in applying the processed data to a target database or second system. |
| Claim: |
2. The system of claim 1, wherein the message queue is a Java Message Service (JMS) queue and the messages are JMS messages. |
| Claim: |
3. The system of claim 1, wherein the extract process is an Oracle GoldenGate extract process, and the trail file is an Oracle GoldenGate trail file. |
| Claim: |
4. The system of claim 1, wherein the messaging capture adaptor can be provided as a plug-in to the extract process, and includes a set of properties, rules and other messaging connectivity information that define how messages should be parsed and mapped to records in the target database or second system, to create the trail file. |
| Claim: |
5. The system of claim 4, wherein the messaging capture adaptor comprises a messaging connectivity component that includes the messaging connectivity information, a data parsing component, and a vendor access module or communications component or interface. |
| Claim: |
6. The system of claim 1, wherein the messaging capture adaptor operates to request messages from a designated queue by starting a local messaging service transaction if not already started, reading a message off the designated queue, and if a message exists, then returning the contents of the message and any message header properties to the messaging capture adaptor. |
| Claim: |
7. The system of claim 6, wherein, when the messaging capture adaptor has successfully parsed the message, has output an entire transaction to the trail, and ensured the transaction has been flushed to disk, the local messaging service transaction is committed, removing the messages from the queue or topic. |
| Claim: |
8. The system of claim 1, wherein the messaging capture adaptor includes a parser for any one or more of fixed width message parsing, delimited message parsing, or XML message parsing. |
| Claim: |
9. A method for performing real-time conversion of data present in the form of messages into database transactions which can subsequently be applied to a database, comprising the steps of: providing a messaging capture adaptor, which processes data received in the form of messages on a message queue at a first or source system, and communicates with an extract process to generate a trail file containing the processed data, for use in applying the processed data to a target database or second system. |
| Claim: |
10. The method of claim 9, wherein the message queue is a Java Message Service (JMS) queue and the messages are JMS messages. |
| Claim: |
11. The method of claim 9, wherein the extract process is an Oracle GoldenGate extract process, and the trail file is an Oracle GoldenGate trail file. |
| Claim: |
12. The method of claim 9, wherein the messaging capture adaptor can be provided as a plug-in to the extract process, and includes a set of properties, rules and other messaging connectivity information that define how messages should be parsed and mapped to records in the target database or second system, to create the trail file. |
| Claim: |
13. The method of claim 12, wherein the messaging capture adaptor comprises a messaging connectivity component that includes the messaging connectivity information, a data parsing component, and a vendor access module or communications component or interface. |
| Claim: |
14. The method of claim 9, wherein the messaging capture adaptor operates to request messages from a designated queue by starting a local messaging service transaction if not already started, reading a message off the designated queue, and if a message exists, then returning the contents of the message and any message header properties to the messaging capture adaptor. |
| Claim: |
15. The method of claim 14, wherein, when the messaging capture adaptor has successfully parsed the message, has output an entire transaction to the trail, and ensured the transaction has been flushed to disk, the local messaging service transaction is committed, removing the messages from the queue or topic. |
| Claim: |
16. The method of claim 9, wherein the messaging capture adaptor includes a parser for any one or more of fixed width message parsing, delimited message parsing, or XML message parsing. |
| Claim: |
17. A non-transitory computer readable medium, including instructions stored thereon which when read and executed by a computer cause the computer to perform the steps comprising: providing a messaging capture adaptor, which processes data received in the form of messages on a message queue at a first or source system, and communicates with an extract process to generate a trail file containing the processed data, for use in applying the processed data to a target database or second system. |
| Current U.S. Class: |
707/756 |
| Current International Class: |
06 |
| Accession Number: |
edspap.20120023116 |
| Database: |
USPTO Patent Applications |
