Building Your Event-Driven Architecture : Integration Server Administrator’s Guide : Managing webMethods Messaging Triggers : Managing Document Processing : Suspending and Resuming Document Processing : About Suspending and Resuming Document Processing for all Triggers
About Suspending and Resuming Document Processing for all Triggers
 
Suspending or Resuming Document Processing for All webMethods Messaging Triggers
When you suspend document processing for all webMethods messaging triggers, Integration Server stops dispatching server threads to process documents received by webMethods messaging triggers. Server resources, such as threads and memory, that might have been used for document processing will be available for other tasks. Document processing remains suspended until you specifically resume it.
Suspending document processing for all webMethods messaging triggers is a quick way to make server resources available. This can be especially helpful in a situation in which Integration Server is functioning under heavy load and additional resources need to be available immediately.
Suspending or resuming document processing can be a temporary or permanent change. (Integration Server considers a document processing change to be permanent if you selected the Apply Change Permanently check box when you made the change.) If the change is temporary, Integration Server reverts to the permanent document processing state when Integration Server restarts or you reload a package. When you reload a package, Integration Server reverts only the triggers contained in that package to the permanent document processing state. For example, suppose that you temporarily suspend document processing for all triggers. If you reload the package OrderProcessing, Integration Server resumes document processing for the triggers in the OrderProcessing package only.
Tip:  
On the Settings > Messaging > webMethods Messaging Trigger Management page, under Document Processing, Integration Server Administrator indicates a temporary document processing change by displaying an asterisk (*) next to the trigger status in the Active column.
When you are ready to resume document processing, you might want to resume it gradually. For example, you might set the Execution Threads Throttle to a low percentage, resume document processing for all triggers, and then gradually move the Execution Threads Throttle up to 100%. Alternatively, you might selectively resume individual triggers. For example, you might want to resume document processing for those triggers that are part of a critical or high priority process.
Copyright © 2016 - 2016 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback