BROKER-BASED MESSAGING THROUGH SQL

• US 20170329945A1
• Filed: 05/31/2016
• Published: 11/16/2017
• Est. Priority Date: 05/11/2016
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Sabiwalsky, Dirk, Schuhart, Henrike, Scheiber, Christoph, Fichter, Timur
• Granted Patent: US 10,372,887 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 16/2455 Query execution
• CPC Class Codes: G06F 21/31 User authentication
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/0884 by delegation of authentication, e.g. a proxy authenticates an entity to be authenticated on behalf of this entity vis-à-vis an authentication entity
• CPC Class Codes: H04L 67/562 Brokering proxy services

Abstract

The disclosure generally describes methods, software, and systems, including a method for publishing messages through a messaging client of a database server. A message to be published to one or more message brokers is received at a server and from a database client. The message is in the form of a SQL statement. The received message is processed at the server. Message broker configurations associated with the received message are determined. The message is published to the one or more message brokers by invoking a messaging client at the server and using at least the message broker configurations.

Claims

1. A computer-implemented method comprising:

receiving, at a server and from a database client, a message in the form of a SQL statement to be published to one or more message brokers;

processing, at the server, the received message;

determining message broker configurations associated with the received message; and

publishing, by invoking a messaging client at the server, the message to the one or more message brokers using at least the message broker configurations.

2. The computer-implemented method of claim 1, wherein the SQL statement is a call statement including a schema name, a message broker identifier, a topic, a quality of service, and the message.

3. The computer-implemented method of claim 2, wherein the quality of service is a code that indicates that the message is to be published at least once, at most once, or exactly once.

4. The computer-implemented method of claim 1, further comprising:

receiving, at the server and from the database client, user credentials for authentication, by the database server, with the message broker prior to publishing the message; and

before publishing the message, authenticating with the message broker using the received credentials.

5. The computer-implemented method of claim 4, wherein receiving the user credentials includes receiving, from the database client, credential creation statements identifying a user identifier and a password for the user.

6. The computer-implemented method of claim 4, wherein the user credentials are received with the message.

7. The computer-implemented method of claim 1, wherein the message further identifies the message broker, and wherein publishing the message includes accessing user credentials in a credential store.

8. The computer-implemented method of claim 1, wherein publishing the message does not require that the message be sent, to the message broker, from an application layer outside of the database server.

9. The computer-implemented method of claim 1, wherein the message includes one or more of a text message and one or more data elements from database tables.

10. The computer-implemented method of claim 1, further comprising:

receiving, at the server and from the database client, a definition of a message broker destination; and

before publishing the message, retrieving information associated with the message broker for use in publishing the message, wherein the definition of the message broker destination includes a schema name, an identifier for a particular message broker, a distribution type, and a connection string identifying a host, a port, and connection parameters for connecting to a particular message broker.

11. The computer-implemented method of claim 1, wherein publishing the message includes using a previously-stored message broker configuration or using a new message broker configuration received from the database client with the message to be published.

12. The computer-implemented method of claim 1, further comprising:

executing database triggers in the database server upon a change in a database;

generating, using trigger information from the triggers, a trigger-initiated message to be published; and

publishing, by invoking the messaging client at the server, the trigger-initiated message to the one or more message brokers using at least the message broker configurations and the trigger information.

13. A system comprising:

memory storing user preferences, user contexts and optimized queues; and

a server performing operations comprising;

receiving, at the server and from a database client, a message in the form of a SQL statement to be published to one or more message brokers;

processing, at the server, the received message;

determining message broker configurations associated with the received message; and

publishing, by invoking a messaging client at the server, the message to the one or more message brokers using at least the message broker configurations.

14. The system of claim 13, wherein the SQL statement is a call statement including a schema name, a message broker identifier, a topic, a quality of service, and the message.

15. The system of claim 14, wherein the quality of service is a code that indicates that the message is to be published at least once, at most once, or exactly once.

16. The system of claim 13, the operations further comprising:

receiving, at the server and from the database client, user credentials for authentication, by the database server, with the message broker prior to publishing the message; and

before publishing the message, authenticating with the message broker using the received credentials.

17. A non-transitory computer-readable media encoded with a computer program, the program comprising instructions that when executed by one or more computers cause the one or more computers to perform operations comprising:

receiving, at a server and from a database client, a message in the form of a SQL statement to be published to one or more message brokers;

processing, at the server, the received message;

determining message broker configurations associated with the received message; and

publishing, by invoking a messaging client at the server, the message to the one or more message brokers using at least the message broker configurations.

18. The non-transitory computer-readable media of claim 17, wherein the SQL statement is a call statement including a schema name, a message broker identifier, a topic, a quality of service, and the message.

19. The non-transitory computer-readable media of claim 18, wherein the quality of service is a code that indicates that the message is to be published at least once, at most once, or exactly once.

20. The non-transitory computer-readable media of claim 17, the operations further comprising:

receiving, at the server and from the database client, user credentials for authentication, by the database server, with the message broker prior to publishing the message; and

before publishing the message, authenticating with the message broker using the received credentials.