MSMQ Adapter 6.0 | webMethods MSMQ Adapter Documentation | webMethods MSMQ Adapter Installation and User’s Guide Documentation | Package Management | MSMQ Adapter in a Clustered Environment | Adapter Component Support in Clusters
 
Adapter Component Support in Clusters
The following MSMQ Adapter components are supported in a clustering environment; however, there may be some restrictions, as discussed below:
*Put services. Can be used in clusters regardless of the transaction type used by the associated adapter connection.
*Get services. Can be used in clusters regardless of the transaction type used by the associated adapter connection.
*Peek services. Can be used in clusters regardless of the transaction type used by the associated adapter connection. However, the machine on which Integration Server is located must be connected to the machine on which the queue is located.
*Listeners. When used with a transactional connection, listeners cannot be used in clusters. This is because the listener must reside on the same machine as the queue, and MSMQ does not support remote transactional read from remote queues.
When used with a non-transactional connection, listeners can be used in a cluster. Ensure that the machine on which Integration Server and MSMQ Adapter are installed and the machine on which the queue is located are on the same network.
Important:
Because MSMQ does not guarantee message ordering in non-transactional messaging, Software AG recommends that you do not deploy a listener that uses a non-transactional connection across a cluster. However, if ordering is not critical for your intended application, duplicate messages can be detected with the exactly-once processing facility in Integration Server. For additional information about duplicate detection and exactly-once processing, see the Publish-Subscribe Developer’s Guide for your release.
*Listener notifications. When synchronous or asynchronous listener notifications are used in a clustered environment, messages may be duplicated and/or received out of order. If necessary, you can use the exactly-once processing facility in Integration Server to detect duplicate messages. If you need to guarantee message order, the application processing the notification documents must handle any reordering of messages that is required. For additional information about duplicate detection and exactly-once processing, see the Publish-Subscribe Developer’s Guide for your release.