Cloud Application Integration (On-Premises) : Service Development : Working with webMethods Messaging Triggers : Deleting webMethods Messaging Triggers
Deleting webMethods Messaging Triggers
 
Deleting webMethods Messaging Triggers in a Cluster or Non-Clustered Group
Keep the following points in mind when deleting a webMethods messaging trigger:
*When you delete a webMethods messaging trigger, Integration Server deletes the queue for the webMethods messaging trigger on Integration Server.
*If the messaging connection alias used by the publishable document type to which the trigger subscribes does not share a client prefix, deleting the webMethods messaging trigger causes the messaging provider to delete the associated provider object (webMethods Broker client queue or Universal Messaging named object on a channel).
*If the messaging connection alias used by the publishable document type to which the trigger subscribes shares a client prefix, deleting the webMethods messaging trigger does not cause the messaging provider to delete the associated provider object (webMethods Broker client queue or Universal Messaging named object on a channel).
*To delete a webMethods messaging trigger, you must lock it and have write access to it.
*You can also use the pub.trigger:deleteTrigger service to delete a webMethods messaging trigger. For more information about this service, see the webMethods Integration Server Built-In Services Reference.
To delete a webMethods messaging trigger
1. In the Package Navigator view of Designer, select the webMethods messaging trigger that you want to delete.
2. Click Edit > Delete.
3. In the Delete Confirmation dialog box, click OK.
Deleting webMethods Messaging Triggers in a Cluster or Non-Clustered Group
Copyright © 2015- 2017 Software AG, Darmstadt, Germany. (Innovation Release)

Product LogoContact Support   |   Community   |   Feedback