When IBM webMethods messaging trigger exists on multiple Integration Servers in a cluster or in a non-clustered group, the subscriptions created by the IBM webMethods messaging trigger remain active even if you disable the IBM webMethods messaging trigger from one of the Integration Servers. This is because the client created for the IBM webMethods messaging trigger on the IBM webMethods Broker is shared. The client on the IBM webMethods Broker becomes disconnected when you disable the IBM webMethods messaging trigger on all the servers in the cluster or non-clustered group of servers. Even when the shared IBM webMethods messaging trigger client becomes disconnected, the subscriptions established by the IBM webMethods messaging trigger remain active. The IBM webMethods Broker continues to enqueue documents for the IBM webMethods messaging trigger. When you re-enable the IBM webMethods messaging trigger on any server in the cluster or non-clustered group, all the queued documents that did not expire will be processed.

To disable IBM webMethods messaging trigger in a cluster or non-clustered group of Integration Servers, disable the IBM webMethods messaging trigger on each Integration Server, and then manually remove the document subscriptions created by the IBM webMethods messaging trigger from the IBM webMethods Broker.