Integration Server 11.1 | Publish-Subscribe Developer’s Guide | Working with IBM webMethods Messaging Triggers | Modifying IBM webMethods Messaging Trigger
 
Modifying IBM webMethods Messaging Trigger
 
Modifying IBM webMethods Messaging Trigger in a Cluster or Non-Clustered Group
After you create IBM webMethods messaging trigger, you can modify it by changing or renaming the condition, specifying different publishable document types, specifying different trigger services, or changing IBM webMethods messaging trigger properties. To modify IBM webMethods messaging trigger, you need to lock the IBM webMethods messaging trigger and have write access to the IBM webMethods messaging trigger.
If your integration solution includes a messaging provider (IBM webMethods Broker or Universal Messaging), the messaging provider needs to be available when editing IBM webMethods messaging trigger. Editing IBM webMethods messaging trigger when the messaging provider is unavailable can cause the IBM webMethods messaging trigger to become out of sync with the associated object on the provider. Do not edit any of the following IBM webMethods messaging trigger components when the messaging provider used by the publishable document types in the trigger are not available.
*Any publishable document types specified in the IBM webMethods messaging trigger. That is, do not change the subscriptions established by the IBM webMethods messaging trigger.
*Any filters specified in the IBM webMethods messaging trigger.
*The IBM webMethods messaging trigger state (enabled or disabled).
*The document processing mode (serial or concurrent processing).
*Priority messaging state (enabled or disabled). This applies to IBM webMethods messaging triggers that receive documents from the IBM webMethods Broker only.
If you edit any of these IBM webMethods messaging trigger components when messaging provider is unavailable and save the changes, the IBM webMethods messaging trigger will become out of sync with its associated object on the messaging provider. You will need to synchronize the IBM webMethods messaging trigger with its associated provider object when the messaging provider becomes available. To synchronize, use Designer to disable the IBM webMethods messaging trigger, re-enable the IBM webMethods messaging trigger, and save. This effectively recreates the object on the messaging provider that is associated with the IBM webMethods messaging trigger. Alternatively, you can disable and then enable the messaging connection alias used by the trigger. However, this restarts all the triggers that use the messaging connection alias and may consume more time and resources.
Note:
If you changed the message processing mode for IBM webMethods messaging trigger that uses a Universal Messaging connection alias with a shared client prefix, you might need to use IBM webMethods Universal Messaging Enterprise Manager to delete and recreate the durable subscription. For more information, see Synchronizing the IBM webMethods Messaging Trigger and Durable Subscription on Universal Messaging .