STANDARDIZED DATABASE CONNECTIVITY SUPPORT FOR AN EVENT PROCESSING SERVER

• US 20110023055A1
• Filed: 07/21/2009
• Published: 01/27/2011
• Est. Priority Date: 07/21/2009
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Bishnoi, Sandeep, Thatte, Mohit, Mishra, Shailendra, Jain, Namit, Srinivasan, Anand
• Granted Patent: US 8,387,076 B2
• Time in Patent Office: Days
• US Class Current: 719/328
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications

Abstract

Techniques for facilitating communication between one or more client applications and an event processing server. In one set of embodiments, a framework is provided that enables a client application to communicate with an event processing server via a standard database connectivity API, such as Java Database Connectivity (JDBC).

Claims

1. A method for facilitating communication between a client application configured to run on a first system and an event processing server configured to run on a second system, the method comprising:

running, on the first system, a database connectivity adapter implementing a database connectivity Application Programming Interface (API), wherein the database connectivity adapter is configured to facilitate communication between the client application and the event processing server via the database connectivity API by;

receiving, in response to an invocation of the database connectivity API by the client application, a query language statement to be executed by the event processing server;

parsing the query language statement to determine a type of the statement;

processing the query language statement based on its type; and

invoking a procedure exposed by the event processing server for executing the query language statement.

2. The method of claim 1 wherein the database connectivity API is Java Database Connectivity (JDBC).

3. The method of claim 1 wherein the query language statement is an Continuous Query Language (CQL) statement.

4. The method of claim 3 wherein the query language statement is a CQL statement for creating an event stream, a CQL statement for selecting data from an event stream, or a CQL statement for inserting data into an event stream.

5. The method of claim 1 wherein parsing the query language statement to determine a type of the statement comprises determining whether the query language statement is a data modification language (DML) statement.

6. The method of claim 5 wherein if the query language statement is a DML statement, processing the query language statement based on its type comprises converting one or more data values included in the query language statement into a data representation native to the event processing server.

7. The method of claim 6 wherein converting one or more data values included in the query language statement into a data representation native to the event processing server comprises:

determining attribute datatypes for an event stream being modified by the query language statement;

comparing the attribute datatypes to datatypes of the one or more data values; and

if the attribute datatypes and the datatypes of the one or more data values are different but compatible, converting the datatypes of the one or more data values into the attribute datatypes.

8. The method of claim 6 wherein if the query language statement is a DML statement, invoking a procedure exposed by the event processing server for executing the query language statement comprises invoking a procedure exposed by the event processing server for executing DML statements, wherein the procedure takes as an input parameter the data representation of the one or more data values native to the event processing server.

9. The method of claim 1 wherein parsing the query language statement to determine a type of the statement comprises determining whether the query language statement is a data definition language (DDL) statement.

10. The method of claim 9 wherein if the query language statement is a DDL statement, invoking a procedure exposed by the event processing server for executing the query language statement comprises invoking a procedure exposed by the event processing server for executing DDL statements, wherein the procedure takes as an input parameter the query language statement.

11. The method of claim 10 wherein the procedure exposed by the event processing server for executing DDL statements is configured to:

parse the query language statement to determine a DDL type of the query language statement;

based on the parsing, perform one or more validations with respect to the query language statement; and

invoke another procedure of the event processing server to execute the query language statement.

12. The method of claim 1 wherein invoking a procedure exposed by the event processing server for executing the query language statement comprises:

obtaining a reference to a remote object exposed by the event processing server via a remote invocation interface; and

invoking a method of the remote object.

13. The method of claim 12 wherein the remote invocation interface is Java Remote Method Invocation (RMI).

14. The method of claim 1 wherein the client application is a data source configured to generate an event stream.

15. The method of claim 1 wherein the client application is a data integrator configured to aggregate event streams from a plurality of different data sources.

16. A system comprising:

a processing component configured to;

run a client application adapted to interact with an event processing server configured to run on a remote system; and

run a database connectivity adapter implementing a database connectivity API, wherein the database connectivity adapter is configured to facilitate communication between the client application and the event processing server via the database connectivity API by;

receiving, in response to an invocation of the database connectivity API by the client application, a query language statement to be executed by the event processing server;

parsing the query language statement to determine a type of the statement;

processing the query language statement based on its type; and

invoking a procedure exposed by the event processing server for executing the query language statement.

17. A system comprising:

a database configured to store data for one or more event streams; and

a server computer communicatively coupled with the database, the server computer being configured to;

run an event processing server in communication with one or more client applications running on one or more remote systems, wherein the event processing server is configured to expose a first procedure callable by the one or more client applications for executing a DML statement at the event processing server, and expose a second procedure callable by the one or more client applications for executing a DDL statement at the event processing server.

18. The system of claim 17 wherein the first procedure is configured to insert one or more data values into an event stream, and wherein the first procedure takes as an input parameter a representation of the one or more data values that is native to the event processing server.

19. The system of claim 17 where the second procedure takes as an input parameter a string representation of the DDL statement.

20. A machine-readable medium having stored thereon program code which, when executed by a processing component of a computer system, causes the processing component to facilitate communication between a client application configured to run on a first system and an event processing server configured to run on a second system, the program code comprising:

code for a database connectivity adapter configured to run on the first system, wherein the database connectivity adapter implements a database connectivity API, and wherein the database connectivity adapter is configured to facilitate communication between the client application and the event processing server via the database connectivity API by;

receiving, in response to an invocation of the database connectivity API by the client application, a query language statement to be executed by the event processing server;

parsing the query language statement to determine a type of the statement;

processing the query language statement based on its type; and

invoking a procedure exposed by the event processing server for executing the query language statement.