Software AG Products 10.7 | Administering Integration Server | Managing webMethods Messaging Triggers | Managing Document Retrieval | Decreasing the Capacity of Trigger Queues | Decreasing the Capacity and Refill Level for webMethods Messaging Triggers
 
Decreasing the Capacity and Refill Level for webMethods Messaging Triggers
Use the following procedure to use the Queue Capacity Throttle to decrease the capacity and refill levels for the queues of all webMethods messaging triggers.
Note:
The Queue Capacity Throttle does not affect the refill level of webMethods messaging triggers that receive documents from Universal Messaging because these triggers do not have a refill level.
*To decrease the capacity and refill level of trigger queues
1. Open the Integration Server Administrator if it is not already open.
2. Go to Settings > Messaging.
3. Click webMethods Messaging Trigger Management, and then click Edit Global webMethods Messaging Trigger Controls.
4. Under Document Retrieval, in the Queue Capacity Throttle field, select the percentage of configured capacity at which you want all trigger queues to operate. The Integration Server automatically adjusts the refill levels by the same percentage.
5. If you want to apply the queue capacity throttle change to all the servers in a cluster, select the Apply Change Across Cluster check box.
This check box appears only if the current Integration Server belongs to a properly configured cluster and is configured to synchronize webMethods messaging trigger changes across the cluster. For more information about configuring an Integration Server to synchronize trigger management changes across a cluster, see Cluster Synchronization for webMethods Messaging Trigger Management.
6. Click Save Changes.
Notes:
*The Queue Capacity Throttle only affects the refill level of webMethods messaging triggers that receive documents from Broker. webMethods messaging triggers that receive documents from Universal Messaging do not have a refill level.
*The Queue Capacity Throttle setting is maintained across server restarts and package reloads.
*If the percentage by which you reduce capacity does not resolve to a whole number, Integration Server rounds up or rounds down to the nearest whole number. However, if rounding down would reduce the value to 0, Integration Server rounds up to 1. For example, if you set the Queue Capacity Throttle to 10% of maximum, a trigger queue with a capacity of 15 and refill level of 4 will have an adjusted capacity of 2 and an adjusted refill level of 1 (Integration Server rounds the calculated adjusted capacity of 1.5 up to 2 and rounds the calculated adjusted refill level of 0.4 up to 1).
*When you reduce the Queue Capacity Throttle and save your changes, Integration Server does not immediately reduce the number of documents in a trigger queue. Instead, Integration Server continues to process documents in the trigger queue until it reaches the adjusted refill level. Then, Integration Server retrieves enough documents to fill the trigger queue to the adjusted capacity. For example, if you set Queue Capacity Throttle to 50%, a trigger queue with a capacity of 8 and a refill level of 2 will have an adjusted capacity of 4 and an adjusted refill level of 1. The Integration Server processes documents in the trigger queue until it reaches the adjusted refill level of only 1 document. Then, Integration Server retrieves up to 3 documents to increase the number of documents in the queue to 4 (the adjusted capacity).
*If you reduce the capacity to a low percentage for an extended period of time, the document might expire on the messaging provider. For each publishable document type, you can specify a Time to live property. This property specifies how long a document can remain on the messaging provider before the messaging provider discards it. For more information about publishable document types, see webMethods Service Development Help.
*If you use the Queue Capacity Throttle as part of your capacity planning process and you determine that the configured values for trigger capacity and refill level need to change, you can use the Integration Server Administrator or Software AG Designer to set the new capacity and refill level values for each webMethods messaging trigger. For more information about setting the capacity and refill level for a trigger, see Modifying webMethods Messaging Trigger Properties.