About Priority Message Processing

Priority messaging determines the order in which a webMethods messaging trigger receives and subsequently processes the documents from the messaging provider. How priority messaging works depends on the messaging provider from which the trigger receives documents.

When priority messaging is enabled for a webMethods messaging trigger that receives documents from webMethods Broker, webMethods Broker places documents in the trigger client queue using the following criteria:

Message priority. webMethods Broker inserts documents with the highest priority at the top of the client queue. A value of 0 is the lowest processing priority; a value of 9 indicates expedited processing.

Message publication time. webMethods Broker orders documents with the same priority in the client queue according to the time at which the document was published. Within documents of the same priority, webMethods Broker inserts the most recently published document after the earlier documents. This ensures that the webMethods messaging trigger receives and processes the documents with the same priority in publication order.

Integration Server receives and processes the documents following the order in which the documents appear in the client queue on the webMethods Broker.

When priority messaging is enabled for a webMethods messaging trigger that receives documents from a Universal Messaging server, Universal Messaging and Integration Server adapt to expedite processing of higher priority documents over lower priority documents.

Note:
Priority messaging applies only to documents that are routed through the webMethods Broker and Universal Messaging. Priority messaging does not apply to locally published documents.

To use priority messaging, you configure both the publishing side and the subscribing side.

On the publishing side, set a message priority level in the document envelope. The priority level indicates how quickly the document should be processed once it is published. A value of 0 is the lowest processing priority; a value of 9 indicates expedited processing. The default priority is 4.

On the subscribing side, enable priority messaging for the webMethods messaging trigger. This is necessary only for triggers that receive documents from webMethods Broker.

Note:
All webMethods messaging triggers that receive documents from Universal Messaging receive and process documents in priority fashion. Priority messaging cannot be disabled for webMethods messaging triggers that receive documents from Universal Messaging.