9.0, 9.5, 9.6, 9.7, or 9.8 Upgrade: Synchronize and Update Serial webMethods Messaging Triggers
If you are using the new Integration Server with Universal Messaging, each webMethods Messaging trigger with serial processing must have a corresponding priority named object on Universal Messaging. However, each serial trigger you migrated from your old Integration Server corresponds to a shared named object on Universal Messaging. Create the corresponding priority named object by doing one of the following:
If the
Universal Messaging is a fresh installation (that is, it was not migrated from an earlier release), synchronize the publishable document types with the provider using
Software AG Designer or the built-in service pub.publish:syncToProvider.
If the
Universal Messaging was migrated from an earlier release, this
Integration Server is the only
Integration Server that connects to
Universal Messaging, and the Shared Client Prefix property for the
Universal Messaging connection alias is set to No, disable and enable the
Universal Messaging connection alias used by the trigger.
If the
Universal Messaging was migrated from an earlier release, and this
Integration Server is not the only
Integration Server that connects to
Universal Messaging or the Shared Client Prefix property is set to Yes, wait till the named object is fully drained and no new documents will be sent to it, and then use
Universal Messaging Enterprise Manager to delete the named object. You may need to quiesce document publishers before deleting the named object. Then disable and enable the
Universal Messaging connection alias used by the trigger.
