Synchronizing the webMethods Messaging Trigger and Named Object on Universal Messaging

Running Business Processes and Composite Applications : webMethods Integration Server Administrator’s Guide : Managing webMethods Messaging Triggers : Serial Triggers Migrated to Integration Server 9.9 or Later from 9.8 or Earlier : Synchronizing the webMethods Messaging Trigger and Named Object on Universal Messaging

A webMethods messaging trigger and the associated named object 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 named object that corresponds to the trigger on Universal Messaging. As a result, the trigger on Integration Server is out of sync with the named object on Universal Messaging. To synchronize the webMethods messaging trigger and the associated named object, you must delete and recreate the named object.

Note:

A webMethods messaging trigger with a serial processing mode corresponds to a priority named object on Universal Messaging. A webMethods messaging trigger with a concurrent processing mode corresponds to a shared named object on Universal Messaging.

To synchronize the webMethods messaging trigger and the named object 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 Shared Client Prefix property for the Universal Messagingconnection alias is set to No, start the trigger to delete and recreate the corresponding named object. You can start a trigger by disabling and then enabling the Universal Messagingconnection 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 Shared Client Prefix property for the Universal Messaging connection alias is set to Yes, you must use Universal Messaging Enterprise Manager to delete the named object. Make sure to delete the named object when the named object is fully drained and no new documents will be sent to it. You many need to quiesce document publishers before deleting the named object. Then create the named object for the trigger by disabling and then enabling the Universal Messaging connection alias used by the trigger.

Contact Support | Community | Feedback