To provide processing in publishing order for a serial trigger in a cluster or a non-clustered group of Integration Server, Universal Messaging routes all of the documents to which a serial webMethods messaging trigger subscribes to the same Integration Server. Because a serial trigger processes only one document at a time, this routing approach ensures that documents from the same publisher are processed in the order in which the documents were published.

To indicate that all of the documents for a serial trigger be sent to the same Integration Server, Integration Server creates a priority named object on Universal Messaging that corresponds to the serial trigger,. In Universal Messaging Enterprise Manager, the named object for the trigger has the Subscription Priority check box selected. With a priority named object, multiple consumers can connect to the named object but only one consumer is active. The active consumer has priority over the other consumers, which remain in fail-over mode. If the active consumer disconnects, one of the fail-over consumers becomes the active consumer and begins receiving documents. When a particular webMethods messaging trigger runs on multiple Integration Servers, each instance of the trigger is a consumer. Each trigger instance can connect to the priority named object but only one trigger at a time processes messages.