TRANSACTIONAL MESSAGING SUPPORT IN CONNECTED MESSAGING NETWORKS

• US 20120173647A1
• Filed: 03/09/2012
• Published: 07/05/2012
• Est. Priority Date: 11/24/2010
• Status: Active Grant

• Current Assignee: Snap, Inc.
• Original Assignee: International Business Machines Corporation
• Inventors: Levell, Jonathan, Peel, Matthew David
• Granted Patent: US 10,061,608 B2
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: G06F 2209/544 Remote
• CPC Class Codes: G06F 2209/547 Messaging middleware
• CPC Class Codes: G06F 9/466 Transaction processing
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues

Abstract

A method and system are provided for transactional messaging support in connected messaging networks. A first messaging network is provided which does not support transactional processing and a second messaging network is provided which does support transactional processing. A proxy application is provided between the first and second messaging networks. The proxy application receives messages from a first application on the first messaging network, the messages including instructions regarding transactional processing of the messages, and forwards the messages to the second messaging network using a transactional processing supported by the second messaging network.

Claims

1. A method for transactional messaging support in connected messaging networks with a first messaging network which does not support transactional processing and a second messaging network which does support transactional processing;

the method comprising;

providing a proxy application between the first and second messaging networks, wherein the proxy application;

receives messages from a first application on the first messaging network, the messages including instructions regarding transactional processing of the messages; and

forwards the messages to the second messaging network using a transactional processing supported by the second messaging network.

2. The method as claimed in claim 1, wherein the proxy application:

returns messages to the first application informing on the outcome of the transaction.

3. The method as claimed in claim 1 or claim 2, wherein the proxy application:

converts messages to include additional functionality supported by the second messaging network.

4. The method as claimed in claim 3, wherein the additional functionality includes:

converting a publish/subscribe message to a point to point message.

5. The method as claimed in claim 3, wherein the additional functionality includes:

converting a point to point message to a publish/subscribe message.

6. The method as claimed in claim 3, wherein the additional functionality includes:

converting multiple short messages to a single long message.

7. The method as claimed in claim 3, wherein the additional functionality includes:

converting a message to a multicast message.

8. The method as claimed in any one of the preceding claims, wherein the instructions regarding transactional processing of the messages includes exposing a beginning and an end of a batch of messages so that the first application has control.

9. The method as claimed in any one of the preceding claims, wherein the instructions are provided in a header of a message sent or received by the first application.

10. The method as claimed in any one of the preceding claims, wherein the instructions are provided in the topic of a message sent or received by the first application.

11. The method as claimed in any one of the preceding claims, wherein the proxy application subscribes to messages on a topic on which commands from the first application are published.

12. The method as claimed in any one of the preceding claims, wherein the first messaging network is a lightweight telemetry transfer network and is connected to the second messaging network via a messaging broker.

13-27. -27. (canceled)