Methods and apparatus for enterprise application integration
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.
1. A method for enterprise application integration comprising:
executing code to program a computer system into a machine for:
downloading code that is executable by the computer system for effecting information transfers between a first database and a second database;
executing the downloaded code with the computer system to program the computer system for:
transferring information between the first database and the second database, and transferring information between the first database and the second database comprises at least one of:
receiving a request for information stored in the first database using a first protocol and transmitting the request for information received from the first database to the second database using a second protocol; and
receiving a request for information stored in the second database using the second protocol and transmitting the request for information received from the second database to the first database using the first protocol.
2. The method according to claim 1 , wherein transferring information between the first database and the second database further comprises:
executing queries against that database from which information is received.
3. The method of claim 1 wherein transferring information between the first database and the second database comprises:
executing the downloaded code to translate between an application program interface (API-1DB) of the first database to the second protocol to receive the information from the first database and to transmit the information to the second database; and
executing the downloaded code to translate between an application program interface (API-2DB) of the second database to the first protocol to receive the information from the second database and to transmit the information to the first database.
4. The method of claim 1 wherein receiving a request for information stored in the first database using a first protocol and transmitting the information received from the first database to the second database using a second protocol comprises:
receiving and transmitting resource definition format triplets (“RDF triplets”), respectively.
5. The method of claim 4 wherein receiving a request for information stored in the first database using a first protocol and transmitting the information received from the first database to the second database using a second protocol comprises:
receiving and transmitting an RDF triplet whose subject comprises any of a literal value, reference value, and uniform identification number (‘“URI”).
6. The method of claim 5 wherein receiving a request for information stored in the first database using a first protocol and transmitting the information received from the first database to the second database using a second protocol comprises:
receiving and transmitting an RDF triplet whose subject reflects transactional information.
7. The method of claim 6 wherein receiving a request for information stored in the first database using a first protocol and transmitting the information received from the first database to the second database using a second protocol comprises:
receiving and transmitting an RDF triplet whose predicate comprises a URI, such that related data being transferred between the first and second databases is represented by URIs in a hierarchical ordering.
8. The method of claim 6 wherein receiving a request for information stored in the first database using a first protocol and transmitting the information received from the first database to the second database using a second protocol comprises:
receiving and transmitting an RDF triplet through whose object each related predicate and subject can be referenced.
9. The method of claim 6 wherein receiving a request for information stored in the first database using a first protocol and transmitting the information received from the first database to the second database using a second protocol comprises:
receiving and transmitting an RDF triplet whose object is any of a literal or an identifier.
10. The method of claim 6 wherein receiving a request for information stored in the first database using a first protocol and transmitting the information received from the first database to the second database using a second protocol comprises:
receiving and transmitting an RDF triplet representing any of marketing information or an e-commerce or other transaction.
11. The method of claim 1 wherein transferring information between the first database and the second database further comprises:
applying a first query to the first database using an application program interface (“API-DB1”) to the second database;
receiving a request for information stored in the first database using the API-DB1 in response to the applied first query;
applying a second query to the second database using an application program interface (“API-DB2”) to the second database; and
receiving a request for information stored in the second database using the API-DB2 in response to the applied second query.