IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

JMS properties for application communication models

JMS clients can operate with both publish/subscribe and point-to-point messages. The publish/subscribe and point-to-point application communication models use virtual channels called destinations. In the publish/subscribe model, the destinations are topics. For the point-to-point model, the destinations are known as queues.

The following application communication model properties can be configured for JMSInput, JMSReceive and JMSOutput nodes:

Property	Description
Connection Factory Name	A string name that is passed to JNDI to look up the administered connection factory object. The connection factory object is used to create a connection to the JMS destination. For a client operating as a publish/subscribe client, the connection factory name is for a TopicConnectionFactory. For a client operating as a point-to-point client, the connection factory name is for a QueueConnectionFactory.
Subscription Topic	The string name that is passed to JNDI to look up the JMS topic destination. The topic is used to create a JMS session when the node is being used to process publish/subscribe messages.
Durable Subscription ID	This is a JMSInput node property only. It is a string identifier that is specified if the node is to subscribe to a durable subscription topic. A durable subscription is one that outlasts the client's connection to a message server. When a durable subscriber is disconnected from the server, the server stores messages that are published. Therefore, when the durable subscriber reconnects, the message server sends all the unexpired messages. Durable subscriptions cannot be unsubscribed from a message flow. A separate administration task unsubscribes a previously registered durable subscription. Some JMS providers supply an administration tool to perform this action.
Source Queue	The string name that is passed to JNDI to look up the JMS queue destination. The queue is used to create a JMS session when the node is being used to process point-to-point messages.

The Subscription Topic and Source Queue properties are mutually exclusive because they configure the node to work with either the publish/subscribe message model or the point-to-point message model.

The JMSReceive node operates only with point-to-point messages.

A Durable subscription ID is not valid without a Subscriber Topic property.

ac24873_.htm |

Last updated Friday, 21 July 2017