Integration Server Administrator's Guide : Managing webMethods Messaging Triggers : Modifying webMethods Messaging Trigger Properties
Modifying webMethods Messaging Trigger Properties
During capacity planning or production, you might decide that the configured trigger properties need to be reset. For example, you might determine that Integration Server performs document retrieval more smoothly for some triggers when the triggers' queue capacity operates at 80% of its configured value. Using Integration Server Administrator, you can reset the configured capacity for those triggers. In fact, any trigger property that affects thread or memory usage for document retrieval or document processing can be set using Integration Server Administrator. These properties include trigger queue capacity, refill level, and maximum execution threads.
The ability to change the capacity and refill level for a webMethods messaging trigger is limited to webMethods messaging trigger that receive documents from the Broker. The capacity for triggers that receive documents from Universal Messaging can be changed only at design time and not at run time. To set the capacity for a webMethods messaging trigger that receives documents from Universal Messaging, edit the trigger in Designer.Furthermore, webMethods messaging triggers that receive documents from Universal Messaging do not have a refill level.
To modify webMethods messaging trigger properties
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, click the name of the trigger for which you want to edit properties.
5. Click Edit Trigger Properties.
6. Under Properties, do one or more of the following:
For this property...
Specify...
Queue Capacity
The maximum number of documents that the trigger queue can contain.
Note:  
The ability to change the queue capacity at run time via Integration Server Administrator applies to webMethods messaging triggers that receive documents from Broker only. To set the capacity for a webMethods messaging trigger that receives documents from Universal Messaging, edit the trigger in Designer.
Queue Refill Level
The number of unprocessed documents that must remain in this trigger queue before Integration Server retrieves more documents for the queue from the Broker. The Queue Refill Level value must be less than or equal to the Queue Capacity value.
Note:  
The Queue Refill Level applies to webMethods messaging triggers that receive documents from Broker only. The refill level does not apply to webMethods messaging trigger that receive documents from Universal Messaging. The Queue Refill Level field displays N/A for triggers that receive documents from Universal Messaging.
Max Execution Threads
The maximum number of documents that Integration Server can process concurrently. You can only specify a maximum execution threads value for concurrent triggers. This field displays N/A for serial triggers.
For more information and guidelines for setting trigger queue capacity, refill level, and maximum execution threads, see the webMethods Service Development Help
7. If you want to apply the property changes 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.
8. Click Save Changes.
Note:  
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 © 2015- 2017 Software AG, Darmstadt, Germany. (Innovation Release)

Product LogoContact Support   |   Community   |   Feedback