Using JMS With Inq

The Java Message Service can be used to allow Inq servers to cooperate with

• one another
• existing parts of an enterprise system via a message broker that has a JMS implementation.

Inq supports all the functionality of the JMS Api. Please see the JMS Mini Guide, which describes how JMS messaging integrates with the Inq process and transaction environment.

Inq's JMS functionality has been tested against GlassFish Open Message Queue. All the example Java programs that Open Message Queue comes with have been implemented in Inq:

Code can be found in examples/jms:

AckEquivExample.inq
AsynchQueueExample.inq
AsynchTopicExample.inq
DurableSubscriberExample.inq
MessageFormats.inq
MessageHeadersTopic.inq
ObjectMessages.inq
QueueBrowser.inq
SampleUtilities.inq
SenderToQueue.inq
SynchQueueExample.inq
SynchTopicExample.inq
TopicSelectors.inq
TransactedExample.inq
XMLTopicExample.inq

The petstore blueprint application combines queue and topic usage with XML handling. Code can be found in app/examples/petstore.

JMS functionality is available in all Inq modes of execution, however for client/server the most common case is that the server manages interaction with the JMS environment and Inq's own client/server event flows maintain client state.