Synchronizing the webMethods Messaging Trigger and Durable Subscription on Universal Messaging
A webMethods messaging trigger and the associated durable subscription on Universal Messaging can get out of sync. For example, when you change the processing mode for a webMethods messaging trigger a webMethods messaging trigger that uses a Universal Messaging connection alias that shares a client prefix, Integration Server does not delete and recreate the durable subscription that corresponds to the trigger on Universal Messaging. As a result, the trigger on Integration Server is out of sync with the durable subscription on Universal Messaging. To synchronize the webMethods messaging trigger and the associated durable subscription, you must delete and recreate the durable subscription.
Note:
A
webMethods messaging trigger with a serial processing mode corresponds to a
serial durable subscription on
Universal Messaging. A
webMethods messaging trigger with a concurrent processing mode corresponds to a
shared durable subscription on
Universal Messaging. For information about the type of durable subscription on
Universal Messaging to which a serial trigger created on versions of
Integration Server prior to 10.3 corresponds, see
Serial Triggers Migrated to
Integration Server 10.3 or Later from Earlier Versions 
To synchronize the
webMethods messaging trigger and the durable subscription on
Universal Messaging
Do one of the following: If the
webMethods messaging trigger resides on the only
Integration Server connected to
Universal Messaging and the
Client Prefix Is Shared property for the
Universal Messaging connection alias is set to
No, start the trigger to delete and recreate the corresponding durable subscription. You can start a trigger by disabling and then enabling the
Universal Messaging connection alias used by the trigger.
Note:Integration Server starts triggers upon server restart.
If more than one
Integration Server connects to
Universal Messaging or the
Client Prefix Is Shared property for the
Universal Messaging connection alias is set to
Yes, you must use
Universal Messaging Enterprise Manager to delete the durable subscription. Make sure to delete the durable subscription when the durable subscription is fully drained and no new documents will be sent to it. You many need to quiesce document publishers before deleting the durable subscription. Then create the durable subscription for the trigger by disabling and then enabling the
Universal Messaging connection alias used by the trigger.