Browse Prior Art Database

Requestor initiated trigger events for Messaging and Queuing

IP.com Disclosure Number: IPCOM000015643D
Original Publication Date: 2002-Feb-15
Included in the Prior Art Database: 2003-Jun-20
Document File: 2 page(s) / 53K

Publishing Venue

IBM

Abstract

Disclosed is a method which allows an application to request data from other applications using triggering in a messaging environment. Explanation of technologies used

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 2

Requestor initiated trigger events for Messaging and Queuing

Disclosed is a method which allows an application to request data from other applications using triggering in a messaging environment. Explanation of technologies used

     A message queue interface, such as the Message Queue Interface, or MQI provided by IBM* Corporation, provides an asynchronous method of communication between programs. An application uses the medium of a queue to communicate with its partner program. These queues can be either local or remote to the application. If an application needs to communicate with another application, it simply PUTs a message to a queue associated with the required application. The application doing the PUT is then free to continue processing. It is not aware that any communications are taking place. Any communications and error recovery are handled by the queue manager.

     The partner application need not be available when the requesting application executes the PUT.

     Indeed, the same application can simply communicate with multiple applications by performing PUT operations to different queues. ('extract from Messaging and Queuing Using the MQI - McGraw Hill Series on Computer Communications').

     Such a message queue interface provides triggering functions, which can be used to automatically start an application which GETs messages from a queue. For the purpose of this disclosure, this is called a PUT based trigger, where by the trigger event is caused by an application putting messages to the
queue.

The Idea

     This disclosure introduces the idea of a GET based trigger. When an application opens a queue for input i.e. to do GET's, a trigger event is produced which can be used to initiate the putting applications.

Problems solved

1) A qmgr X has messages on a transmission queue, waiting to be delivered to a qmgr
Y. qmgr Y is not available. At some point later qmgr Y becomes available. An application on qmgr Y opens a queue for input. This would generate a trigger event, which would cause qmgr Y to start a requestor channel from qmgr X to qmgr Y. The messages would then be sent to qmgr Y down the channel, where the application can GET them.

     A real life example of this could be a publish - subscribe service. The publisher publishes messages, which the subscriber can retrieve at a time suitable to itself. Th...