Changing Message Processing When webMethods Broker Is the Messaging Provider
After you perform capacity planning and testing for your integration solution, you might want to modify the processing mode for a webMethods messaging trigger. Keep the following points in mind before you change the processing mode for a webMethods messaging trigger that receives documents from webMethods Broker:
![*](chapterTOC_bullet.png)
When you change the processing mode for a
webMethods messaging trigger,
Integration Server recreates the associated trigger client queue on the
webMethods Broker.
Important:
Any documents that existed in the trigger client queue before you changed the message process mode will be lost.
![*](chapterTOC_bullet.png)
If you created the
webMethods messaging trigger on an
Integration Server connected to a configured
webMethods Broker, you can only change the processing mode if
Integration Server is currently connected to the
webMethods Broker.
![*](chapterTOC_bullet.png)
If you change the document processing mode when
Integration Server is not connected to the configured
webMethods Broker,
Designer displays a message stating that the operation cannot be completed.
Integration Server does not change the processing mode if the
webMethods Broker connection alias shares a client prefix.
Note:
A webMethods Broker connection alias shares a client prefix if the Client Prefix Is Shared property for the connection alias is set to Yes.