Changing Message Processing When 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 Broker:
![*](bullet.gif)
When you change the processing mode for a
webMethods messaging trigger,
Integration Server recreates the associated trigger client queue on the
Broker.
Important: | Any documents that existed in the trigger client queue before you changed the message process mode will be lost. |
![*](bullet.gif)
If you created the
webMethods messaging trigger on an
Integration Server connected to a configured
Broker, you can only change the processing mode if
Integration Server is currently connected to the
Broker.
![*](bullet.gif)
If you change the document processing mode when
Integration Server is not connected to the configured
Broker,
Designer displays a message stating that the operation cannot be completed.
Integration Server does not change the processing mode if the
Broker connection alias shares a client prefix.
Note: | A Broker connection alias shares a client prefix if the Shared Client Prefix property for the connection alias is set to Yes. |