Service Development Help : Working with webMethods Messaging Triggers : Deleting webMethods Messaging Triggers : Deleting webMethods Messaging Triggers in a Cluster or Non-Clustered Group
Deleting webMethods Messaging Triggers in a Cluster or Non-Clustered Group
When a webMethods messaging trigger exists on multiple Integration Servers in a cluster or non-clustered group of Integration Servers, the subscriptions created by the webMethods messaging trigger remain active even if you delete the webMethods messaging trigger from one of the Integration Servers. When deleting webMethods messaging triggers from the servers in a cluster or non-clustered group, the associated provider object remains connected to the cluster or non-clustered group until you delete the webMethods messaging trigger on all of the servers. If you do not delete the webMethods messaging trigger on all of the servers, the provider object for the webMethods messaging trigger remains connected and the messaging provider continues to enqueue documents for the webMethods messaging trigger.
To delete a webMethods messaging trigger from a cluster or non-clustered group of Integration Servers, delete the webMethods messaging trigger from each Integration Server in the cluster, and then manually delete the provider object associated with webMethods messaging trigger from the messaging provider.
Note:  
In addition to the term “non-clustered group,” the terms “stateless cluster” and “external cluster” are sometimes used to describe the situation in which a group of Integration Servers function in a manner similar to a cluster but are not part of a configured cluster.
Modifying a webMethods Messaging Trigger in a Cluster or Non-Clustered Group
Disabling and Enabling a webMethods Messaging Trigger in a Cluster or Non-Clustered Group
Copyright © 2017 Software AG, Darmstadt, Germany. (Innovation Release)

Product LogoContact Support   |   Community   |   Feedback