Set Metric Increment for Content-Based Throttles
Using transformation(XSLT) file to set the metricContent for content-based throttles.
TIBCO API Exchange Gateway supports the notion of content-based throttles, by extending a throttle configuration with a monitor. You can define a content-based metric increment counter using the throttle configuration.
Using the content-based throttles, you can define custom throttle policies. The custom throttle policies enforce the API usage controls on business metric such as order amounts. When a throttle configuration has been extended with a monitor definition, it uses the parse step XSLT transformation at run time. The parse step XSLT transformation maps the business metric containing element from the request payload message to a throttle monitor specific element in the output document generated by the parse step XSLT transformation.
To support the content-based throttle extension mechanism for multiple throttle definitions on a request's throttle chain, the monitor element is defined as a repeatable element in the output document of the parse step XSLT transformation. The monitor element itself is a node element that contains two elements which need to be defined when setting the content-based throttle metric increment. The first element of the monitor node element is the metric name element that must contain the throttle name to which the content-based metric counter increment must be applied. The second element of the monitor node element is the metric increment that contains the actual counter increment that has been derived from the request message payload and needs to be applied to the throttle.
For more information on how to configure and use content-based throttles, see Content Based Throttles section.