Disabling and Enabling a webMethods Messaging Trigger
You can use the Enabled property to disable or enable a webMethods messaging trigger. When you disable a webMethods messaging trigger, Integration Server disconnects the trigger client on the webMethods Broker. The webMethods Broker removes the document subscriptions created by the trigger client. The webMethods Broker does not place published documents in client queues for disabled webMethods messaging triggers. When you enable a disabled webMethods messaging trigger, Integration Server connects the trigger client to the webMethods Broker and re-establishes the document subscriptions on the webMethods Broker.
Note: | You can also suspend document retrieval and document processing for a webMethods messaging trigger. Unlike disabling a webMethods messaging trigger, suspending retrieval and processing does not destroy the client queue. The webMethods Broker continues to enqueue documents for suspended webMethods messaging triggers. However, Integration Server does not retrieve or process documents for suspended webMethods messaging triggers. For more information about suspending webMethods messaging triggers, see webMethods Integration Server Administrator’s Guide. |
You cannot disable a webMethods messaging trigger during trigger service execution.
To disable or enable a webMethods messaging trigger
1. In the Package Navigator view of Designer, open the webMethods messaging trigger that you want to disable or enable.
2. In the Properties view, under General, set Enabled to one of the following:
Select... | To... |
False | Disable the webMethods messaging trigger. |
True | Enable the webMethods messaging trigger. |
3. Click File > Save.
You can enable only valid
webMethods messaging triggers. If the
webMethods messaging trigger is not valid,
Designer displays an error message when you save the
webMethods messaging trigger prompting you to cancel the save or continue the save with a disabled
webMethods messaging trigger. For more information about requirements for a valid
webMethods messaging trigger, see
webMethods Messaging Trigger Requirements.
Related Topics