CentraSite Documentation : Runtime Governance with CentraSite : Run-Time Governance Reference : Built-In Run-Time Actions Reference for Virtual Services : Run-Time Actions Reference for Virtual Services : Throttling Traffic Optimization
Throttling Traffic Optimization
Note:  
Keep the following in mind:
1. This action is not available in Mediator versions below 9.0.
2. Dependency requirement: A policy that includes this action must also include the Identify Consumer action if the Limit Traffic for Applications option is selected.
This action limits the number of service invocations during a specified time interval, and sends alerts to a specified destination when the performance conditions are violated.
Reasons for limiting the service invocation traffic include:
*To avoid overloading the back-end services and their infrastructure.
*To limit specific consumers in terms of resource usage (that is, you can use the “Monitor Service Level Agreement” action to monitor performance conditions for a particular consumer, together with “Throttling Traffic Optimization” to limit the resource usage).
*To shield vulnerable servers, services, and even specific operations.
*For service consumption metering (billable pay-per-use services).
Note:  
To enable Mediator to publish performance metrics, you must configure Mediator to communicate with CentraSite (in the Integration Server Administrator, go to Solutions > Mediator > Administration > CentraSite Communication). For the procedure, see Administering webMethods Mediator.
Input Parameters
Soft Limit
Number. Optional. Specifies the maximum number of invocations allowed per Interval before issuing an alert. Reaching the soft limit will not affect further processing of requests (until the Hard Limit is reached).
Note:  
The limit is reached when the total number of invocations coming from all the consumer applications (specified in the Limit Traffic for Applications field) reaches the limit. Soft Limit is computed in an asynchronous manner; thus when multiple requests are made at the same time, it may be possible that the Soft Limit alert will not be strictly accurate.
Hard Limit
Number. Required. Specifies the maximum number of invocations allowed per alert interval before stopping the processing of further requests and issuing an alert. Typically, this number should be higher than the soft limit.
Note:  
The limit is reached when the total number of invocations coming from all the consumer applications (specified in the Limit Traffic for Applications field) reaches the limit. Hard Limit is computed in an asynchronous manner; thus when multiple requests are made at the same time, it may be possible that the Hard Limit alert will not be strictly accurate.
Limit Traffic for Applications
String. Specifies the consumer application(s) that this action applies to. To specify multiple consumer applications, use the plus button to add rows, or select Any Consumer to apply this action to any consumer application.
Interval
Number. Specifies the amount of time for the soft limit and hard limit to be reached.
Frequency
String. Specifies how frequently to issue alerts.
Value
Description
Every Time
Issue an alert every time the specified condition is violated.
Only Once
Issue an alert only the first time the specified condition is violated.
Reply To Destination
String. Optional. Specifies where to log the alerts.
Important:  
Ensure that Mediator is configured to send event notifications to the destination(s) you specify here. For details, see Administering webMethods Mediator.
Value
Description
CentraSite
Sends the alerts to the virtual service's Events profile in CentraSite.
Prerequisite: You must configure Mediator to communicate with CentraSite (in the Integration Server Administrator, go to Solutions > Mediator > Administration > CentraSite Communication). For the procedure, see Administering webMethods Mediator.
Local Log
Sends the alerts to the server log of the Integration Server on which Mediator is running.
Also choose a value in the Log Level field:
*Info: Logs error-level, warning-level, and informational-level alerts.
*Warn: Logs error-level and warning-level alerts.
*Error: Logs only error-level alerts.
Important:  
The Integration Server Administrator's logging level for Mediator should match the logging level specified for this action (go to Settings > Logging > Server Logger).
SNMP
Sends the alerts to CentraSite's SNMP server or a third-party SNMP server.
Prerequisite: You must configure the SNMP server destination (in the Integration Server Administrator, go to Solutions > Mediator > Administration > Email). For the procedure, see Administering webMethods Mediator.
Email
Sends the alerts to an SMTP email server, which sends them to the email address(es) you specify here. To specify multiple addresses, use the plus button to add rows.
Prerequisite: You must configure the SMTP server destination (in the Integration Server Administrator, go to Solutions > Mediator > Administration > Email). For the procedure, see Administering webMethods Mediator.
EDA/Database
Sends the alerts to an EDA endpoint/Database destination that you configured in Integration Server Administrator:
*An EDA endpoint (that is, a default endpoint configured in the universal messaging configuration).
*A Database (that is, a JDBC connection pool is defined in Integration Server and associated with the Mediator functional alias).
Prerequisite: You must configure the EDA/Database destination in Integration Server on the Solutions > Mediator > Administration > EDA/Database Configuration page. For details, see Administering webMethods Mediator.
Alert Message for Soft Limit
String. Optional. Specify a text message to include in the soft limit alert.
Alert Message for Hard Limit
String. Optional. Specify a text message to include in the hard limit alert.
Copyright © 2005-2016 Software AG, Darmstadt, Germany.
Product LogoContact Support   |   Community   |   Feedback