Decreasing the Capacity of Trigger Queues
You can impact the amount of memory used for document retrieval by adjusting the capacity of all the webMethods messaging triggers that retrieve documents from the Broker or Universal Messaging. The scapacity determines the maximum number of documents that the trigger queues on Integration Server can contain.
You can use the Queue Capacity Throttle provided in Integration Server Administrator to decrease the capacity of all the trigger queues for webMethods messaging triggers that receive documents from a messaging provider. The throttle also reduces the refill levels of all webMethods messaging triggers that receive documents from the Broker. The refill level specifies the number of documents that remain in the trigger queue before Integration Server requests more documents. The Queue Capacity Throttle reduces the capacity and refill levels for all the trigger queues by the same percentage. For example, if you set the Queue Capacity Throttle to 50% of maximum, a trigger queue with a capacity of 10 and a refill level of 4 will have an adjusted capacity of 5 and an adjusted refill level of 2.
Note: webMethods messaging triggers that receive documents from Universal Messaging do not have a refill level.
By decreasing the capacity and refill levels, you can:
Reduce the amount of memory needed to retrieve documents from the messaging provider.
Reduced capacity and refill levels mean that Integration Server retrieves fewer documents for a webMethods messaging trigger at one time. Because Integration Server retrieves fewer documents, Integration Server uses less memory when retrieving documents.
Reduce the memory needed to store the documents while they await processing.
Note: Decreasing the capacity might increase the frequency with which Integration Server retrieves documents because Integration Server might empty the trigger queues to the adjusted refill level more quickly.