WebSphere MQ Adapter 6.5 | webMethods WebSphere MQ Adapter Documentation | webMethods WebSphere MQ Adapter Installation and User’s Guide Documentation | Adapter Notifications | Listener Notifications | Behavior of Listener Notifications
 
Behavior of Listener Notifications
WebSphere MQ Adapter handles messages depending on how you have configured listeners and listener notifications in your system. For example, messages behave differently when the following combinations are set up in your WebSphere MQ Adapter:
*Transactional or non-transactional listeners
The transactionality of a listener depends on the transactionality of the connection. For example, when you associate a non-transactional connection with a listener, then the listener is non-transactional.
*Transactional or non-transactional asynchronous notifications
The transactionality of an asynchronous notification depends on the transactionality of a listener. For example, when you associate a non-transactional listener with an asynchronous notification, then the asynchronous notification is non-transactional.
*Transactional or non-transactional synchronous notifications
The transactionality of a synchronous notification depends on the transactionality of a listener. For example, when you associate a non-transactional listener with a synchronous notification, then the synchronous notification is non-transactional.
If the listener and either asynchronous or synchronous notification have the following behavior,
Then the WebSphere MQ Adapter...
*The filter criteria of a non-transactional listener matches a message's property fields,
AND
*The filter criteria of a non-transactional asynchronous notification does not match a message's property fields,
...throws the message away.
*The filter criteria of a non-transactional listener matches a message's property fields,
AND
*The filter criteria of a non-transactional synchronous notification does not match a message's property fields,
...throws the message away.
*The filter criteria of transactional listener matches a message's property fields,
AND
*The filter criteria of a transactional asynchronous notification does not match does not match a message's property fields,
...rolls the message to the dead letter queue.
*The filter criteria of a transactional listener matches a message's property fields,
AND
*The filter criteria of a transactional synchronous notification does not match a message's property fields,
...rolls the message to the dead letter queue.