Services Throttling in webMethods

Problem

Services throttling is the intentional slowing of service by a service provider. It can be implemented by webMethods components at the application level to limit network congestion, database slowdown and server crashes.

Using this behavior, you can fine-tune the performance of your application.

Solution

Service throttling can be implemented based on two conditions: the number of simultaneous messages processing and memory usage. Service throttling can be implemented in webMethods as such:

1. Create publishable document for the messages to be processed, sync the document with Broker.
2. Create a Trigger to subscribe to the Broker document, set up Trigger properties:

• Message processing - Processing mode : Serial/Concurrent
• Max Execution Threads

     3.      In the triggered service, control the duration of processing, i.e. set the sleep time to control the elapse of the service.
 
Throttling Threshold can be set up. When a high threshold is reached, Services starts to throttle. Throttling stops when the low threshold is reached.