Serial Triggers Migrated to Integration Server 10.3 or Later from Earlier Versions
As of Integration Server version 10.3, when using Universal Messaging as the messaging provider, a webMethods messaging trigger with serial processing corresponds to a serial durable subscription on Universal Messaging. For Integration Server version 9.9 to 10.2, a webMethods messaging trigger with serial processing corresponded to a priority durable subscription on Universal Messaging. Prior toIntegration Server 9.9, a webMethods messaging trigger with serial processing corresponded to a shared named object on Universal Messaging.
All serial webMethods messaging triggers created on Integration Server 10.3 or later will correspond to a serial durable subscription. However, serial triggers migrated from Integration Server versions 9.9 to 10.2 will still correspond to a priority named object (durable subscription). Serial triggers migrated from an Integration Server prior to version 9.9 will still correspond to a shared named object (durable subscription). As a result, the serial trigger and the durable subscription will be out of sync. To synchronize the migrated serial trigger and the durable subscription, you must do one of the following:
If you are using a fresh install of
Universal Messaging 10.3 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 Server creates a serial durable subscription for each serial trigger.