Methods and apparatus for enterprise application integration

• US 10,255,303 B1
• Filed: 12/09/2016
• Issued: 04/09/2019
• Est. Priority Date: 05/15/2001
• Status: Expired due to Term

• Current Assignee: Object Store Incorporated
• Original Assignee: Object Store Incorporated
• Inventors: Britton, Colin P., Azmi, Amir, Kumar, Ashok, Kaufman, Noah W., Bajpai, Chandra, Angelo, Robert F.
• Primary Examiner(s): Corrielus, Jean M
• Application Number:
  US15/374,286
• Time in Patent Office: 851 Days
• Field of Search: 707610, 707758
• CPC Class Codes: G06F 16/213 with details for schema evolution support
• CPC Class Codes: G06F 16/214 Database migration support
• CPC Class Codes: G06F 16/2462 Approximate or statistical queries
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: G06F 16/972 Access to data in other repository systems, e.g. legacy data or dynamic Web page generation
• CPC Class Codes: Y10S 707/99938 Concurrency, e.g. lock management in shared database
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface

Abstract

A method for enterprise application integration that uses “connectors” that can be instantiated via downloading (e.g., using Java® or other such technologies) to provide interfaces to respective disparate database systems. The databases systems may comprise any variety of now or heretofore known systems, e.g. SAP, Oracle, and so forth. The connectors can, for example, translate between a native language (or API) of the respective database systems and an internal language/protocol of the enterprise application integration system. To this end, the connectors can utilize a scripting language to access the respective database systems. Data retrieved from the database systems can be stored in a central data store in the form of RDF triplets, from which directed graphs can be generated for to generate presentations consolidated from the multiple database systems.

Claims

1. A digital data processing system for enterprise application integration including effecting information transfers between a first database and a second database, the system comprising:

a processor;

a non-transitory memory coupled to the processor, the memory having code stored therein that is executable by the computer system to;

download code for effecting the information transfers between the first database and the second database, wherein the second database is coupled to a framework server;

instantiating a software connector from the code to provide a translating interface between the first database and the second database;

transfer the information between the first database and the second database, wherein to transfer the information comprises to;

receive a request for first information stored in the first database using a first protocol, wherein the first protocol is a native language of the first database; and

execute the first software connector to translate between an application program interface (“

API-DB1”

) of the first database and a native protocol of the second database to transmit the first information from the first database to the second database using a native protocol of the second database, wherein to translate the first software connector performs a transformation according to a script, then transforms the first information into a semantic form suitable for the first database to catalog, assigns a unique universal identification number for later conversion into a uniform resource locator, routes the first information to a serializer to transform the first information into hypertext transfer protocol for transfer to the second database;

receive a request for second information stored in the second database using the native protocol; and

execute the first software connector to translate between the native protocol of the second database to the (“

API-DB1”

) of the first database to transmit the second information from the second database to the first database.

2. The system according to claim 1, wherein to transfer the information between the first database and the second database further comprises to:

execute queries against the database from which information is received.

3. The system of claim 1 wherein the semantic form comprises resource definition format triplets (“

RDF triplets”

).

4. The system of claim 3 wherein a subject of the RDF triplet comprises a member of a group consisting of a literal value, reference value, or uniform identification number (“

URI”

).

5. The system of claim 3 wherein a subject of the RDF triplet reflects transactional information.

6. The system of claim 5 wherein a predicate of the RDF triplet comprises a uniform identification number (“

URI”

), such that related data being transferred between the first and second databases is represented by URIs in a hierarchical ordering.

7. The system of claim 5 wherein an object and each related predicate and subject of the RDF triplet can be referenced.

8. The system of claim 5, wherein an object of the RDF triplet is a member of a group consisting of a literal or an identifier.

9. The system of claim 5 wherein the RDF triplet represents a member of a group consisting of marketing information or an e-commerce or other transaction.

10. The system of claim 5 wherein to transfer information between the first database and the second database further comprises to:

apply a first query to the first database using the application program interface (“

API-DB1”

) to the second database;

receive a request for the first information stored in the first database using the API-DB1 in response to the applied first query;

apply a second query to the second database using an application program interface (“

API-DB2”

) to the second database; and

receive a request for information stored in the second database using the API-DB2 in response to the applied second query.