Trading Networks 10.3 | Administering and Monitoring B2B Transactions | Integration Server Administrator's Guide | Managing webMethods Messaging Triggers | Managing Document Retrieval | Increasing or Decreasing Threads for Document Retrieval from webMethods Broker
 
Increasing or Decreasing Threads for Document Retrieval from webMethods Broker
 
When to Increase or Decrease Threads for Retrieving Documents from webMethods Broker
During production and capacity planning, you can increase or decrease the number of threads used to retrieve documents from the Broker. By default, Integration Server can use up to 100% of the server thread pool to retrieve documents from Broker. Each webMethods messaging trigger uses a separate server thread to retrieve documents from the Broker. For example, if the maximum size of the server thread pool is 80 threads, and the server can use 100% of the server thread pool to retrieve documents, then up to 80 triggers can request more documents at one time.
You can limit the maximum number of threads used for document retrieval by specifying the percentage of the server thread pool that can be used to retrieve documents. The Integration Server uses the specified percentage to calculate the number of server threads that can be used to retrieve documents from the Broker.
For example, suppose that the maximum size of the server thread pool is 80 threads. If you specify a maximum document retrieval threads percentage of 10%, then the Integration Server can use only 8 threads to retrieve documents from Broker at one time. Because Integration Server uses a separate thread to retrieve documents for each webMethods messaging trigger, this means that Integration Server can retrieve documents for only 8 triggers that receive documents from the Broker at one time.
Reducing the percentage of the server thread pool used for document retrieval from the Broker can slow the rate of document retrieval because fewer triggers can retrieve documents simultaneously. It also ensures the availability of server threads for other tasks, such as answering HTTP requests, retrieving documents from Universal Messaging, or processing documents.
Increasing the percentage of the server thread pool available for retrieving documents from Broker can increase the arrival rate of documents because it allows more triggers to retrieve documents from the Broker at one time.
For more information about setting the number of server threads for document retrieval, see Limiting Server Threads for webMethods Messaging Triggers.
Note:
Threads allotted for document retrieval only impact webMethods messaging triggers that receiving documents from Broker. The threads you specify for document retrieval will not include threads used to retrieve documents from Universal Messaging