WebSphere MQ Adapter 6.5 | webMethods WebSphere MQ Adapter Documentation | webMethods WebSphere MQ Adapter Installation and User’s Guide Documentation | Package Management | WebSphere MQ Adapter in a Clustered Environment | Clustering Considerations and Requirements | Using the Exactly Once Notification Feature in a Clustered Environment
Using the Exactly Once Notification Feature in a Clustered Environment
In order for the exactly once notification to work correctly for an asynchronous notifications using a transactional listener, review the following considerations:
*Specify a unique value for the MsgID property field
*Make sure that the listener does not filter on the MsgID value
It is assumed that the application that processes the resultant notification documents will perform any necessary reordering. The order of the resultant notification documents is not guaranteed in a clustered environment of Integration Server.
*To use the exactly once notification feature for a transactional asynchronous listener notification
1. Install WebSphere MQ Adapter on all machines in the cluster. For detailed instructions on how to install this adapter, see Installing, Upgrading, and Uninstalling WebSphere MQ Adapter.
2. Install Integration Server. For complete installation instructions, see the Installing webMethods Products On Premises for your release.
3. Create separate packages for the connections, services, flows, listeners, triggers, notifications on one of the machines in the cluster for deployment to the other machines.
4. Verify that the PublishDocument is publishable and is defined to the Broker in the PublishDocument properties. For detailed instructions on how to test a publishable document type, see Testing Publishable Document Types.
5. Configure a trigger to use with the transactional asynchronous notification. For detailed instructions on how to configure a trigger, see the Publish-Subscribe Developer’s Guide for your release.
6. When you configure the trigger for the transactional asynchronous notification using Designer, make sure that you set the Exactly once trigger properties as follows:
*Detect duplicates = True
*Use history = True
7. Deploy the packages with the adapter connections, adapter services, adapter flow services, adapter listener, listener notifications, and triggers on the other machines in the cluster.