Priority messaging only applies to documents that are published to the Broker and Universal Messaging. It does not apply to locally published documents.

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. That is, Integration Server ignores the value of the Priority property if the webMethods messaging trigger subscribes to one or more publishable document types associated with a Universal Messaging connection alias.

When you enable or disable priority messaging for a webMethods messaging trigger that receives documents from Broker, Integration Server disconnects the trigger client on the Broker and recreates the associated webMethods messaging trigger client queue. Any documents that existed in the webMethods messaging trigger client queue before you enabled or disabled priority messaging will be lost. For this reason, you may want to ensure the webMethods messaging trigger queue on Integration Server is empty before enabling or disabling priority messaging.

Priority messaging may consume Broker resources and can introduce latency into document processing by webMethods messaging triggers. For more information about how priority messaging may impact performance, refer to the webMethods Broker Java Client API Reference.