Your knowledge of your integration solution is the best tool for determining when to increase and decrease thread usage for retrieving documents from Broker. For example, if you know that Integration Server regularly receives a high number of HTTP requests during a certain time period, you might want to decrease thread usage for retrieving documents right before the HTTP requests usually begin, then increase threads for retrieving documents after the frequency of HTTP requests slows down. Alternatively, if you know that Integration Server receives a high volume of incoming documents at the same time each day, you might want to increase the number of threads available for retrieving documents during that time period.

You can also determine when to increase or decrease threads for retrieving documents from Broker by monitoring the number of available server threads. To assist with this, you can establish a warning threshold that instructs Integration Server to alert you when the percentage of available threads drops below a specified level. Specifically, Integration Server creates a journal log entry stating "Available Thread Warning Threshold Exceeded." When you receive this message in the journal log, you can decrease threads for document retrieval to make server threads available to perform other functions. For more information about setting an available threads warning threshold, see Managing the Server Thread Pool.

Another method of determining when to alter the number of server threads allotted for retrieving documents from Broker is to monitor the current number of threads retrieving documents from the Broker. Integration Server Administrator displays this value in the Current Threads field under Document Retrieval on the Settings > Messaging > webMethods Messaging Trigger Management page. The Current Threads field under Document Retrieval does not include threads used to retrieve documents from Universal Messaging.