Adapter for JMS 6.1 SP1 | webMethods Adapter for JMS Documentation | webMethods Adapter for JMS Installation and User’s Documentation | About the Adapter for JMS | Adapter Notifications
 
Adapter Notifications
 
Considerations When Using MessageListener Notifications
Exactly Once Notifications
MessageListener Notification Run-Time Processing
Using MessageListener Notifications
The Adapter for JMS provides a notification called MessageListener, which monitors a specified JMS destination (queue or topic) and notifies the adapter when a message arrives at that destination.
You can configure the notification to either publish the notification's associated publishable document or you can configure the notification to invoke a flow or Java service using the data from the notification.
If the notification publishes the document, you can use an Integration Server trigger to monitor for a given publishable document associated with a notification. When Integration Server receives this publishable document, it invokes a flow or Java service that is registered with the trigger. The flow or Java service then reacts to the data changes contained in the notification's publishable document. For more details about Integration Server publishable documents, see the Publish-Subscribe Developer’s Guide for your release.
Note:
If you need to use a Client ID for the notifications, it is better to specify it along with the other notification parameters using Designer, and not while creating the connection factory or the Adapter for JMS connections. When the Client ID is specified in the connection factory or JMS connections, only one connection can be created through this connection factory or connection. This limits the Adapter for JMS from leveraging the connection pool.
For instructions for configuring MessageListener notifications, see Configuring MessageListener Notifications.