System and method for connecting to and controlling to disparate databases

• US 20030055826A1
• Filed: 09/14/2001
• Published: 03/20/2003
• Est. Priority Date: 09/14/2001
• Status: Abandoned Application

• Current Assignee: Kevin Graham
• Original Assignee: Kevin Graham
• Inventors: Graham, Kevin
• Application Number:
  US09/951,889
• Publication Number:
  US 20030055826A1
• Time in Patent Office: Days
• US Class Current: 707/10
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

Systems and methods for facilitating communications with and control of disparate databases via an electronic data network, such as the Internet and WWW. The systems and methods include a database interface system for interfacing client applications to a database. The database interface system includes a data source driver and an interface facility. The data source driver is related to the database and is configured to allow operative access to the database via an electronic data network. The interface facility is coupled to the electronic data network and is configured to accept a message from a client coupled to an electronic data network and configured to send and receive messages containing a character sting (e.g., a request for data, etc.) to access the database via the database source driver based on the character string within the message, to perform a database operation in the database based on the character string, and to return a message to the client corresponding to the executed database operation.

Claims

1. A database interface system for interfacing client applications to a database via an electronic data network, comprising:

a data source driver corresponding to said database that is configured to allow operative access to said database;

an database interface facility coupled to said electronic data network and configured to accept a request message from a client containing a character string, to access said database via said database source driver based on said character string, to perform a database operation in said database based on said string, and to return a results message to said client based on said database operation, said client configured to send and to receive messages via said electronic data network.

3. The system according to claim 1, wherein said data source drive comprises a database driver compatible with said database.

4. The system according to claim 1, wherein said client and said database interface facility are JAVA programs and said messages are sent via JAVA RMI.

5. The system according to claim 1, wherein said data source drive contains a JDBC driver.

6. The system according to claim 1, wherein database interface facility generates a SQL statement based on said character string and said client.

7. The system according to claim 1, wherein said database interface facility maintains a constant connection to said database via said data source driver.

8. The system according to claim 1, wherein said character string includes a request for data from said database.

9. The system according to claim 1, wherein said character string includes a request for a batch update to said database.

10. The system according to claim 1, wherein said character string includes a request for a batch update to said database.

11. The system according to claim 1, wherein said results message includes an error returned from said database.

12. The system according to claim 1, wherein said results message includes the number of rows returned from said database.

13. The system according to claim 12, wherein said client, said database interface facility, said statement interpreter, and said results interpreter are JAVA programs and said messages are sent via JAVA RMI.

14. The system according to claim 12, wherein said transaction proxy use at least one JDBC driver.

15. The system according to claim 12, wherein said database interface facility is further configured to create and terminate additional transaction proxies as requests are made by said client.

16. The system according to claim 12, wherein said transaction proxy maintains a constant connection to said database.

17. The system according to claim 12, wherein said valid database command is SQL.

18. The system according to claim 12, wherein said result contains an error.

19. The system according to claim 12, wherein said result contains rows of data.

20. The system according to claim 12, wherein said statement interpreter is further configured to access a second database in order to convert said request into at least one valid database command.

21. The system according to claim 12, wherein said results interpreter is further configured to access a second database in order to convert said result into a formatted results message corresponding to a format relating to said client.

12-1. A database interface system for interfacing client applications to a plurality of databases comprising:

a client coupled to an electronic data network and configured to send and receive messages and to request a database operation;

a database interface facility configured to receive said request from said client via said electronic data network, to assign a transaction proxy to said client based on said request, to send and receive messages via said electronic data network, said transaction proxy being configured to receive send and receive messages via said electronic data network, and to connect to at least one database of said plurality of databases and perform a database operation and receive a result from said database;

a statement interpreter configured to receive said request from said transaction proxy, to convert said request into at least one valid database command based on said request, and to return said converted message to said transaction proxy; and

a results interpreter configured to receive said result from said transaction proxy, to convert said result based on said request and said client, and to return said converted result to said transaction proxy.

22. A method for accessing a disparate database and performing a database operation comprising the steps of:

at a client, making a database operation request and passing it to a database interface facility;

at said database interface facility, receiving said request and converting said request into at least one valid database command based on said client and said request;

at said database interface facility, access a database based on said request and said client, and executing said at least on valid database command;

at said database interface facility, capturing results from said database based on said at least one executed database command;

at said database interface facility, converting said results to a formatted message based on said request and said client;

at said database interface facility, returning said formatted message to said client.

23. The method according to claim 22, wherein said client and said database interface facility are JAVA programs and said messages are sent via JAVA RMI.

24. The method according to claim 22, wherein said database interface facility maintains a constant connection to said database.

25. The method according to claim 22, wherein said database interface facility is converts said request based on the IP address of said client.

26. The method according to claim 22, wherein said database interface facility accesses a second database to perform said conversions.

27. The method according to claim 22, wherein said at least one valid database command is a SQL statement.

28. The method according to claim 22, wherein said results contains an error.

29. The method according to claim 22 wherein said request is a request to update data in said database, further comprising the step of:

at said database interface facility, committing said update after executing said at least one valid database command.

30. The method according to claim 22, wherein said database interface facility is further configured to perform a batch process based on said request.