Throttling Traffic Optimization

Soft Limit

(Number). (Optional). The maximum number of invocations allowed per Interval Value before issuing an alert. Reaching the soft limit does 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 clients (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 is not strictly accurate.

Alert Message for Soft Limit

(String). (Optional). A text message to include in the soft limit alert.

Hard Limit

The maximum number of invocations allowed per Interval Value 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 clients (specified in the Limit Traffic for Consumers 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 is not strictly accurate.

Alert Message for Hard Limit

(String). (Optional). A text message to include in the hard limit alert.

Alert for Consumer Applications

(String). The consumer application that this action applies to. To specify multiple consumers, use the plus button to add rows, or select Any Consumer to apply this action to any consumer application.

Alert Interval

(String). The amount and unit (Minutes, Hours, Days or Weeks) of time for the soft limit and hard limit to be reached.

Alert Frequency

(String). Frequency to issue alerts.

Value

Description

Every Time

(Default). Issues an alert every time the specified condition is violated.

Only Once

Issues an alert only the first time the specified condition is violated.

Alert Destination

(String). (Optional). A place to log the alerts.

Important:

Ensure that Mediator is configured to send event notifications to the destination you specify here. For details about alerts and transaction logging, see Administering webMethods Mediator.

Value

Description

API Portal

Mediator can use API Portal destination to publish data about run-time events and key performance indicator (KPI) metrics.

Mark the checkbox API Portal and select an API Portal instance from the drop-down list. When you mark the checkbox, CentraSite displays the list of API Portal instances that are registered and are available to you. To specify multiple API Portal instances, use the plus button to add rows.

Note:

When you publish an API that is configured with an API Portal destination to Mediator, CentraSite automatically creates an entry of the configured API Portal destination in the Integration Server Administrator's Solutions > Mediator > Administration > API Portal page.

Mediator uses the API Portal destination to publish the following event types:

Transaction Events

Monitoring Events

Lifecycle Events

Policy Violation Events

Error Events

Performance Metrics

You can also use the Mediator capability to specify the intervals at which the events and KPI metrics must be published to the API Portal destination.

Prerequisite: You must configure CentraSite to communicate with API Portal using the Add Gateway action.

CentraSite

Sends the alerts to the API'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 information about how to configure communication with CentraSite, see Administering webMethods Mediator.

Elasticsearch

Mediator can use Elasticsearch destination to publish data about run-time events and key performance indicator (KPI) metrics.

Mediator uses the Elasticsearch destination to publish the following event types:

Transaction Events

Monitoring Events

Lifecycle Events

Policy Violation Events

Error Events

Performance Metrics

You can also use the Mediator capability to specify the intervals at which the events and KPI metrics must be published to the Elasticsearch destination.

Prerequisite: You must configure the Elasticsearch destination (in the Integration Server Administrator, go to Solutions > Mediator > Administration > Elasticsearch). 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 select 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.

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 or 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.