Integration Server 10.3 | Integration Server Administrator's Guide | Managing webMethods Messaging Triggers | Managing Document Processing | Suspending and Resuming Document Processing | About Suspending and Resuming Document Processing for Specific Triggers
 
About Suspending and Resuming Document Processing for Specific Triggers
 
Suspending or Resuming Document Processing for a Specific webMethods Messaging Trigger
Sometimes, instead of suspending or resuming document processing for all webMethods messaging triggers, you might want to suspend or resume processing for a specific trigger. Following are examples of situations where you might want to suspend document processing for specific triggers.
*When a back-end system becomes unresponsive or requires maintenance, you might want to suspend document processing for triggers that interact with that back-end system. If the back-end system is not available because of maintenance or failure, trigger services that interact with the system would probably not execute successfully. Suspending document processing for the associated triggers allows for more effective resource utilization because you keep resources that would have been used for unsuccessful document processing available for other tasks.
*After suspending document processing for all triggers, you might resume document processing for specific triggers. If Integration Server is operating under a heavy load, you might first suspend all document processing and then gradually resume document processing, starting with the triggers involved in critical processes.
*If Integration Server suspends document processing for a serial trigger because the associated trigger service ends in error, you need to resume document processing for the trigger. For more information about configuring a serial trigger to suspend retrieval and processing automatically after an error, see webMethods Service Development Help.