B2B Integration 10.4 | Administering and Monitoring B2B Transactions | Integration Server Administrator's Guide | Managing webMethods Messaging Triggers | Managing Document Retrieval | Suspending and Resuming Document Retrieval | About Suspending and Resuming Document Retrieval for a Specific Trigger | Suspending or Resuming Document Retrieval for a webMethods Messaging Trigger
 
Suspending or Resuming Document Retrieval for a webMethods Messaging Trigger
The following procedure explains how to suspend or resume document retrieval for an individual webMethods messaging trigger.
* To suspend or resume document retrieval for a webMethods messaging trigger
1. Open the Integration Server Administrator if it is not already open.
2. In the Settings menu of the Navigation panel, click Messaging.
3. Click webMethods Messaging Trigger Management.
4. Under Individual webMethods Messaging Trigger Controls, locate the row containing the trigger for which you want to suspend document retrieval.
5. In the Active column located under Document Retrieval, click Yes or No. (The Active column displays "Yes" if document retrieval is active for the trigger; "No" if document retrieval is suspended. An asterisk (*) appears next to the status if the document retrieval state is temporary.)
6. In the Retrieval State list, do the following:
Select
To
Active
Resume document retrieval for this trigger.
Suspended
Suspend document retrieval for this trigger.
7. If you want the state change to be permanent and maintained after Integration Server restarts, select the Apply Change Permanently check box. If you do not select this check box, Integration Server considers the change to be temporary.
8. If you want to apply the document retrieval change for this trigger to all the servers in a cluster, select the Apply Change Across Cluster check box.
This check box appears only if the current Integration Server belongs to a properly configured cluster and is configured to synchronize trigger changes across the cluster. For more information about configuring an Integration Server to synchronize trigger management changes across a cluster, see Cluster Synchronization for webMethods Messaging Trigger Management.
9. Click Save Changes.
Notes:
*Integration Server will not suspend or resume document retrieval for the specified webMethods messaging trigger if the trigger is locked by a user.
*If Integration Server cannot suspend (or resume) document retrieval locally, cluster synchronization cannot occur.
*When you resume document retrieval, Integration Server resumes retrieval for the webMethods messaging trigger at the percentage specified by the Queue Capacity Throttle.
*In a flow service, you can suspend or resume document retrieval for individual triggers by invoking the pub.trigger:suspendRetrieval service or the pub.trigger:resumeRetrievalservice, respectively. For more information about these services, see the webMethods Integration Server Built-In Services Reference .
*In a Java service, you can suspend or resume document retrieval by calling com.wm.app.b2b.server.dispatcher.trigger.TriggerFacade.setRetrievalSuspended(). For more information about this method, see the webMethods Integration Server Java API Reference for the com.wm.app.b2b.server.dispatcher.trigger.TriggerFacade class.
*You can filter the list of displayed triggers using the watt.server.trigger.managementUI.excludeList property. For more information about this property, see Server Configuration Parameters.
Copyright © 2016- 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release