Building Your Event-Driven Architecture : Service Development Help : Working with webMethods Messaging Triggers : About Capacity and Refill Level for the webMethods Messaging Trigger Queue : Setting Capacity and Refill Level for a webMethods Messaging Trigger
Setting Capacity and Refill Level for a webMethods Messaging Trigger
To set trigger queue capacity and refill level
1. In the Package Navigator view of Designer, open the webMethods messaging trigger for which you want to specify the webMethods messaging trigger queue capacity.
2. In the Properties view, under Trigger queue, in the Capacity property, specify the maximum number of documents that the trigger queue can contain. The default is 10.
3. In the Refill level property, specify the number of unprocessed documents that must remain in this webMethods messaging trigger queue before Integration Server retrieves more documents for the queue from the Broker. The default is 4.
The Refill level value must be less than or equal to the Capacity value.
Note:  
The Refill level property applies to webMethods messaging triggers that receive documents from the Broker only. The Refill level property does not apply to webMethods messaging triggers that receive documents from Universal Messaging.
4. Click File > Save to save the webMethods messaging trigger.
Notes:
*The server administrator can use the Integration Server Administrator to gradually decrease the capacity and refill levels of all webMethods messaging trigger queues. The server administrator can also use the Integration Server Administrator to change the Capacity or Refill level values for a webMethods messaging trigger. For more information, see webMethods Integration Server Administrator’s Guide.
*You can specify whether Integration Server should reject locally published documents when the queue for the subscribing webMethods messaging trigger is at maximum capacity. For more information about this feature, see the description for the watt.server.publish.local.rejectOOS parameter in webMethods Integration Server Administrator’s Guide.
Copyright © 2016 - 2016 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback