Hybrid Integration 10.2 | Integrating On-Premises Applications | Document Conventions | Working with webMethods Messaging Triggers | Modifying a webMethods Messaging Trigger
 
Modifying a webMethods Messaging Trigger
 
Modifying a webMethods Messaging Trigger in a Cluster or Non-Clustered Group
After you create a webMethods messaging trigger, you can modify it by changing or renaming the condition, specifying different publishable document types, specifying different trigger services, or changing webMethods messaging trigger properties. To modify a webMethods messaging trigger, you need to lock the webMethods messaging trigger and have write access to the webMethods messaging trigger.
If your integration solution includes a messaging provider (webMethods Broker or Universal Messaging), the messaging provider needs to be available when editing a webMethods messaging trigger. Editing a webMethods messaging trigger when the messaging provider is unavailable can cause the webMethods messaging trigger to become out of sync with the associated object on the provider. Do not edit any of the following 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 webMethods messaging trigger. That is, do not change the subscriptions established by the webMethods messaging trigger.
*Any filters specified in the webMethods messaging trigger.
*The webMethods messaging trigger state (enabled or disabled).
*The document processing mode (serial or concurrent processing).
*Priority messaging state (enabled or disabled). This applies to webMethods messaging triggers that receive documents from the webMethods Broker only.
If you edit any of these webMethods messaging trigger components when messaging provider is unavailable and save the changes, the webMethods messaging trigger will become out of sync with its associated object on the messaging provider. You will need to synchronize the webMethods messaging trigger with its associated provider object when the messaging provider becomes available. To synchronize, use Designer to disable the webMethods messaging trigger, re-enable the webMethods messaging trigger, and save. This effectively recreates the object on the messaging provider that is associated with the 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 a webMethods messaging trigger that uses a Universal Messaging connection alias with a shared client prefix, you might need to use Universal Messaging Enterprise Manager to delete and recreate the named object. For more information, see Synchronizing the webMethods Messaging Trigger and Named Object on Universal Messaging .

Copyright © 2015- 2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release