ODBC ACCESS TO EXTERNAL SERVICES

• US 20150358383A1
• Filed: 06/10/2014
• Published: 12/10/2015
• Est. Priority Date: 06/10/2014
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Nathan, Eyal, Khalatov, Dmitry
• Granted Patent: US 9,674,261 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2455 Query execution
• CPC Class Codes: G06F 16/955 using information identifiers, e.g. uniform resource locators [URL]
• CPC Class Codes: G06F 16/9558 Details of hyperlinks; Management of linked annotations
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

The present disclosure involves systems, software, and computer implemented methods for providing access to an external service using a SQL query. One example method includes identifying a request for an ODBC (Open DataBase Connectivity) connection. The request identifies the external service and the identified request is associated with a SQL (Structured Query Language) query. The ODBC connection is created. An HTTP (Hyper Text Transfer Protocol) request to be provided to the external service is generated. The HTTP request is generated based on the SQL query. The generated HTTP request is sent to the external service. An HTTP response is received from the external service in response to the HTTP request. A query result set table is populated based on the received HTTP response.

Claims

1. A method of providing access to an external service, comprising:

identifying a request for an ODBC (Open DataBase Connectivity) connection, the request identifying the external service and wherein the identified request is associated with a SQL (Structured Query Language) query;

creating the ODBC connection;

generating an HTTP (Hyper Text Transfer Protocol) request to be provided to the external service, wherein the HTTP request is generated based on the SQL query;

sending the generated HTTP request to the external service;

receiving an HTTP response from the external service in response to the HTTP request; and

populating a query result set table based on the received HTTP response.

2. The method of claim 1, further comprising storing data in the query result set table to a database system.

3. The method of claim 1, wherein the SQL query is generated in response to a trigger event associated with a database system and the trigger event occurs in response to a new entry being added to the database system, a modification of an entry in the database system, or a deletion of an entry in the database system.

4. The method of claim 1, wherein the request for the ODBC connection includes a connection string including one or more connection parameters for connecting to the external service, the connection parameters include a URL (Uniform Resource Locator) of the external service and authentication information for accessing the external service, and the generated HTTP request is based on the one or more connection parameters.

5. The method of claim 1, wherein the generated HTTP request is based on information identified in one or more predicates included in a WHERE clause of the SQL query, each of the one or more predicates includes a predefined column of a predefined table, an operator, and a request parameter value, each predefined column in the predefined table corresponds to either an HTTP request parameter or an HTTP response parameter, and each column included in the column list included in the SQL query corresponds to a predefined column included in the predefined table.

6. The method of claim 1, wherein populating the query result set table comprises mapping information included in the HTTP response to one or more columns included in the query result set table, wherein each of the one or more columns included in the query result set table corresponds to a predefined column in the predefined table and to a column included in a column list included in the SQL query.

7. The method of claim 1, wherein the query result set table is a runtime construct initially stored in memory.

8. A system comprising:

one or more computers; and

a computer-readable medium coupled to the one or more computers having instructions stored thereon which, when executed by the one or more computers, cause the one or more computers to perform operations comprising;

identifying a request for an ODBC (Open DataBase Connectivity) connection, the request identifying the external service and wherein the identified request is associated with a SQL (Structured Query Language) query;

creating the ODBC connection;

generating an HTTP (Hyper Text Transfer Protocol) request to be provided to the external service, wherein the HTTP request is generated based on the SQL query;

sending the generated HTTP request to the external service;

receiving an HTTP response from the external service in response to the HTTP request; and

populating a query result set table based on the received HTTP response.

9. The system of claim 8, the operations further comprising storing data in the query result set table to a database system.

10. The system of claim 8, wherein the SQL query is generated in response to a trigger event associated with a database system and the trigger event occurs in response to a new entry being added to the database system, a modification of an entry in the database system, or a deletion of an entry in the database system.

11. The system of claim 8, wherein the request for the ODBC connection includes a connection string including one or more connection parameters for connecting to the external service, the connection parameters include a URL (Uniform Resource Locator) of the external service and authentication information for accessing the external service, and the generated HTTP request is based on the one or more connection parameters.

12. The system of claim 8, wherein the generated HTTP request is based on information identified in one or more predicates included in a WHERE clause of the SQL query, each of the one or more predicates includes a predefined column of a predefined table, an operator, and a request parameter value, each predefined column in the predefined table corresponds to either an HTTP request parameter or an HTTP response parameter, and each column included in the column list included in the SQL query corresponds to a predefined column included in the predefined table.

13. The system of claim 8, wherein populating the query result set table comprises mapping information included in the HTTP response to one or more columns included in the query result set table, wherein each of the one or more columns included in the query result set table corresponds to a predefined column in the predefined table and to a column included in a column list included in the SQL query.

14. The system of claim 8, wherein the query result set table is a runtime construct initially stored in memory.

15. A computer program product encoded on a non-transitory storage medium, the product comprising non-transitory, computer readable instructions for causing one or more processors to perform operations comprising:

identifying a request for an ODBC (Open DataBase Connectivity) connection, the request identifying the external service and wherein the identified request is associated with a SQL (Structured Query Language) query;

creating the ODBC connection;

generating an HTTP (Hyper Text Transfer Protocol) request to be provided to the external service, wherein the HTTP request is generated based on the SQL query;

sending the generated HTTP request to the external service;

receiving an HTTP response from the external service in response to the HTTP request; and

populating a query result set table based on the received HTTP response.

16. The product of claim 15, wherein the SQL query is generated in response to a trigger event associated with a database system and the trigger event occurs in response to a new entry being added to the database system, a modification of an entry in the database system, or a deletion of an entry in the database system.

17. The product of claim 15, wherein the request for the ODBC connection includes a connection string including one or more connection parameters for connecting to the external service, the connection parameters include a URL (Uniform Resource Locator) of the external service and authentication information for accessing the external service, and the generated HTTP request is based on the one or more connection parameters.

18. The product of claim 15, wherein the generated HTTP request is based on information identified in one or more predicates included in a WHERE clause of the SQL query, each of the one or more predicates includes a predefined column of a predefined table, an operator, and a request parameter value, each predefined column in the predefined table corresponds to either an HTTP request parameter or an HTTP response parameter, and each column included in the column list included in the SQL query corresponds to a predefined column included in the predefined table.

19. The product of claim 15, wherein populating the query result set table comprises mapping information included in the HTTP response to one or more columns included in the query result set table, wherein each of the one or more columns included in the query result set table corresponds to a predefined column in the predefined table and to a column included in a column list included in the SQL query.

20. The product of claim 15, wherein the query result set table is a runtime construct initially stored in memory.