Two IS servers hosting the MQ adapter are clustered talking to a single MQ queue. How do we configure the MQ Adapter listener in this situation to avoid duplicate document processing? Do we configure a single listener on a single IS server and a notification on each IS server in the cluster?

How does a single listener on one IS server pass on the data to the two notifications, one on each IS server?

Thanks,
Srinivas Yeruva

Any comments on the usage of MQ Adapter 6.0 in IS cluster 6.0.1 in the context of aysnchronous notifications will be appreciated.

Thanks,
Srinivas

We have done a similar implementation in one of our projects using the webMethods JMS Adapter and I presume that it can be extended to the MQ Adapter as well.When you create an Adapter notification for the MQ Adapter to listen for incoming messages in the MQ queue, an Adapter listener service and a publishable document is created. The adapter listener service can be seen from the webMethods Administrator console under the MQAdapter connection/polling notifications (For JMS Adapter it was JMSAdapter connection/polling notifications). JMS Adapter 6.1 guide says that the JMS notifications are not cluster enabled.To avoid duplicate document processing enable the Adapter listener on only one of the IS servers in the cluster. If you have a broker configured, the document(s) are published to the broker and the messages can the received and processed by any one or both of the servers in the cluster. You have to have a subscribing service and a trigger on both of the IS servers in the cluster to process the received document. If the broker is not configured the documents are published to only the IS server in the cluster where the Adapter listener is enabled and all the documents will be processed by that IS server itself.

Thanks for your response. I was wondering if there is a way to avoid the single point of failure(Listener configuration on a single server in the cluster). Any ideas would be most appreciated.

Thanks,
Srinivas Yeruva