Trading Networks 10.3 | Administering and Monitoring B2B Transactions | Integration Server Administrator's Guide | Managing webMethods Messaging Triggers | Managing Document Processing | Decreasing Document Processing for Concurrent Triggers
 
Decreasing Document Processing for Concurrent Triggers
 
Decreasing Execution Threads for Concurrent webMethods Messaging Triggers
You can reduce the amount of server resources consumed by document processing by decreasing the rate of processing for concurrent triggers. Specifically, you can reduce the maximum number of threads that can process documents for a concurrent trigger at one time.
Integration Server Administrator provides an Execution Threads Throttle that you can use to reduce the execution threads for all concurrent triggers by the same percentage. For example, if you set the Execution Threads Throttle to 50% of maximum, Integration Server reduces the maximum execution threads for all concurrent triggers by half. A concurrent trigger with a maximum execution threads value of 6, has an adjusted maximum execution threads value of 3.
By decreasing parallel processing for concurrent triggers, you can:
*Free up server threads and memory to perform other functions, such as answering HTTP requests or retrieving documents.
*Prevent concurrent triggers from monopolizing the threads allotted for document processing. The number of server threads that Integration Server dispatches to process documents for serial and concurrent triggers cannot exceed the value established by the maximum execution threads percentage. If you reduce the number of threads allowed for document processing, and concurrent triggers continue to consume the maximum execution threads possible (according to their configured settings), serial triggers must wait longer for server threads to become available. This is especially likely if Integration Server contains concurrent triggers that execute long-running services.
Note:
The Execution Threads Throttle only affects webMethods messaging triggers.