Serial Triggers Migrated to Integration Server 9.9 or Later from 9.8 or Earlier

Prior to Integration Server 9.9, when using Universal Messaging as the messaging provider, a webMethods messaging trigger with serial processing corresponded to a shared named object on Universal Messaging. As of Integration Server 9.9, a webMethods messaging trigger with serial processing corresponds to a priority named object on Universal Messaging. All webMethods messaging triggers created on Integration Server 9.9 or later will correspond to a priority named object. However, migrated serial triggers will still correspond to a shared named object. The trigger and named object will be out of sync. To synchronize the migrated serial trigger and the named object, you must do one of the following:

If you are using a fresh install of Universal Messaging 9.9 or later (that is, the Universal Messaging server was not migrated), when you start Integration Server, synchronize the publishable document types with the provider using Designer or the built-in service pub.publish:syncToProvider. Synchronizing the publishable document types causes Integration Server to reload the webMethods messaging triggers. Integration Servercreates a priority named object for each serial trigger.

If you are using an installation of Universal Messaging 9.9 or later that was migrated from an earlier version, you must delete and recreate the named object. For more information about deleting and recreating a named object associated with a trigger, see Synchronizing the webMethods Messaging Trigger and Named Object on Universal Messaging .