Method and system to communicate messages in a computer network

• US 8,606,859 B2
• Filed: 10/17/2003
• Issued: 12/10/2013
• Est. Priority Date: 10/17/2002
• Status: Active Grant

• Current Assignee: Cloud Software Group
• Original Assignee: TIBCO Software Incorporated (Cloud Software Group)
• Inventors: Collison, Derek
• Primary Examiner(s): STRANGE, AARON N
• Application Number:
  US10/687,951
• Publication Number:
  US 20040139166A1
• Time in Patent Office: 3,707 Days
• Field of Search: 709204-207, 709/238
• US Class Current: 709/206
• CPC Class Codes: G06F 2209/544 Remote
• 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
• CPC Class Codes: H04L 67/2895 Intermediate processing functionally located close to the data provider application, e.g. reverse proxies
• CPC Class Codes: H04L 67/55 Push-based network services
• 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/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/566 Grouping or aggregating service requests, e.g. for unified processing
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

A method includes communicating in a computer network a first message in a publish-subscribe arrangement or a queuing arrangement, and communicating a second message in a publish-subscribe arrangement or a queuing arrangement. The second message may be derived from the first message. The publish-subscribe arrangement may include a topic to which at least one of the first and second messages is sent, and the queuing arrangement may include a queue to which at least one of the first and second messages is sent. The second message may be derived from the first message by bridging a source and a target destination. The invention extends to a machine-readable medium embodying a sequence of instructions that, when executed by a machine, cause the machine to execute the method.

Claims

1. A method of communicating a message in a computer network, the method comprising:

delivering, in parallel, the message from a sender application via both a first messaging paradigm and a second messaging paradigm, wherein the message is bridged prior to being processed via either first messaging paradigm or the second messaging paradigm, and wherein the message reaches both at least one original destination and at least one bridged destination;

processing the message according to the first messaging paradigm, wherein the processing the message according to the first messaging paradigm comprises routing the message to the at least one original destination; and

processing, on a parallel path, the message according to the second messaging paradigm, wherein the processing the message according to the second messaging paradigm comprises routing the message to the at least one bridged destination associated with the at least one original destination, and wherein a bridge associates a first of the at least one original destinations with a first of the at least one bridged destination.

2. The method of claim 1, wherein the bridge is a software bridge.

3. The method of claim 1, wherein the at least one original destination comprises a plurality of original destinations, and the software bridge associates the plurality of original destinations with the first bridged destination.

4. The method of claim 1, wherein the at least one bridged destination comprises a plurality of bridged destinations, and wherein the software bridge associates the first original destination with the plurality of bridged destinations.

5. The method of claim 1, wherein a plurality of messages are routed to the first original destination, and the software bridge selects the message from the plurality of messages.

6. The method of claim 5, wherein the processing the message according to the second messaging paradigm further comprises determining that the first bridged destination is permitted to receive the message.

7. The method of claim 1, wherein a configuration file comprises the software bridge.

8. The method of claim 1, wherein an administrator console comprises the software bridge.

9. The method of claim 1, wherein the first messaging paradigm and the second messaging paradigm utilize Java messaging.

10. A non-transitory machine-readable medium embodying a sequence of instructions that, when executed by a computer, causes the computer to perform operations comprising:

delivering in parallel the message from a sender application via both a first messaging paradigm and a second messaging paradigm, wherein the message is bridged prior to being processed via either the first messaging paradigm or the second messaging paradigm, and wherein the message reaches both at least one original destination and at least one bridged destination;

processing the message according to the first messaging paradigm, wherein the processing the message according to the first messaging paradigm comprises routing the message to at least one original destination; and

processing, on a parallel path, the message according to the second messaging paradigm, wherein the processing the message according to the second messaging paradigm comprises routing the message to at least one bridged destination associated with the at least one original destination, and wherein a bridge associates a first of the at least one original destinations with a first of the at least one bridged destination.

11. The non-transitory machine-readable medium of claim 10, wherein the first messaging paradigm comprises a topic-based publish-subscribe messaging paradigm, the sender application comprises a publishing application, the message is associated with a topic, and the processing the message according to the first messaging paradigm comprises routing the message to a publish module.

12. The non-transitory machine-readable medium of claim 11, the operations further comprising:

aborting delivery of the message unless the at least one original destination and the at least one bridged destination are configured to receive the message.

13. The non-transitory machine-readable medium of claim 11, wherein the processing the message according to the first messaging paradigm further comprises delivering the message to a number of subscriber applications that are registered to receive messages associated with the topic.

14. The non-transitory machine-readable medium of claim 11, wherein the second messaging paradigm comprises a queuing messaging paradigm.

15. The non-transitory machine-readable medium of claim 10, wherein the number of subscriber applications is zero.

16. The non-transitory machine-readable medium of claim 10, wherein the first messaging paradigm comprises a queuing messaging paradigm and the processing the message according to the first messaging paradigm comprises routing the message to a queue module.

17. The non-transitory machine-readable medium of claim 16, wherein the processing the message according to the first messaging paradigm further comprises delivering the message to a queue consumer.

18. The non-transitory machine-readable medium of claim 16, wherein the second messaging paradigm is a topic-based publish-subscribe messaging paradigm.

19. A system to communicate a message in a computer network, the system comprising:

a processor;

a memory element; and

a server configured to perform operations, the operations comprising;

delivering in parallel with a bridge the message from a sender application via both a first messaging paradigm and a second messaging paradigm, wherein the message is bridged prior to being processed via either first messaging paradigm or the second messaging paradigm, and wherein the message reaches both at least one original destination and at least one bridged destination;

processing the message according to the first messaging paradigm, wherein the processing the message according to the first messaging paradigm comprises routing the message to at least one original destination; and

processing, on a parallel path, the message according to the second messaging paradigm, wherein the processing the message according to the second messaging paradigm comprises routing the message to at least one bridged destination associated with the at least one original destination, and wherein a bridge associates a first of the at least one original destinations with a first of the at least one bridged destination.

20. The system of claim 19, wherein the bridge is a software bridge.

21. The system of claim 20, wherein the first messaging paradigm comprises a topic-based publish-subscribe messaging paradigm, and the second messaging paradigm comprises a queuing messaging paradigm.