A throttle T1_BookOrder is defined in such a way that the throttle
T1_BookOrder allows a user to order only 20 books in 10 seconds. In such a case, a throttle
T1_BookOrder is configured using the Config UI as follows:
For example, you can create a custom throttle monitor for this throttle T1_BookOrder to increment the throttle count based on the number of book orders in the request. This allows you to customize the throttle count by providing the increment counter defined as metricIncrement for the monitor. The metricIncrement for this monitor can be populated using an XPath formula based on the total number of book orders in the request message. In this case, you can define the metricIncrement to count the book orders in the request. So, if the count of book orders in a request is 5, then it increments the throttle count as 5 allowing only 4 similar requests within 10 seconds.
For example, the monitor for a throttle T1 is defined in the XSLT file using a
<monitor> tag as follows:
In the preceding example, the metricIncrement is assigned based on the count of the
OrderDtl element in the payload of an incoming request. If you have an input payload with
n number of
OrderDtl elements, you can parse the number of
OrderDtl elements and assign that number to
metricIncrement. The
metricIncrement is applied to the throttle configuration.
