Message publication when the message rate for a message flow goes back into range

Lists the conditions that control the publishing of the message rate is back in range message.

Before you begin

Ensure that the publication of events is enabled, and the pub/sub broker is correctly configured. The default configuration enables publication of events using the built-in MQTT pub/sub broker. If WebSphere® MQ is installed, and there is a WebSphere MQ queue manager specified on the integration node, then the MQ pub/sub broker is used for the publication of events. For more information, see Configuring the publication of event messages and Configuring the built-in MQTT pub/sub broker.

About this task

The message rate statistics are collected at a checkpoint that occurs every 20 seconds and the total message rate is calculated at this checkpoint. If the total message rate previously exceeded the notification threshold, and then later the total message rate drops back into range, the back in range XML message is published.

No state is stored when the message flow is stopped, restarted, or redeployed.

When a flow is terminated, the flow termination process checks to see whether the last message published was to report that the message rate exceeded the notification threshold. In this situation, the flow termination process automatically publishes a message to report that the message flow is now back in range.

If you enable the notification threshold you can subscribe to the following topic:

For publications on an MQ pub/sub broker:

$SYS/Broker/integrationNodeName/WorkloadManagement/BelowThreshold/integrationServerName
/<applicationName>/<libraryName>/<messageFlowLabel>

For publications on an MQTT pub/sub broker:

IBM/IntegrationBus/integrationNodeName/WorkloadManagement/BelowThreshold/integrationServerName
/<applicationName>/<libraryName>/<messageFlowLabel>

where integrationNodeName is the name of the integration node, integrationServerName is the name of the integration server on that integration node, application_name is the name of the application on that integration server, library_name is the name of the library on that application, and messageFlowLabel is the name of the message flow that is deployed to the library.

In the situation where the message flow is not contained in either an application or a library, the application_name or library_name parameters must be omitted along with their enclosing forward slash (/). For example:

If the message flow is not contained in an application and a library:
```
$SYS/Broker/integrationNodeName/WorkloadManagement/BelowThreshold/integrationServerName
/<messageFlowLabel>
```
or
```
IBM/IntegrationBus/integrationNodeName/WorkloadManagement/BelowThreshold/integrationServerName
/<messageFlowLabel>
```
where integrationNodeName is the name of the integration node, integrationServerName is the name of the integration server on that integration node, and messageFlowLabel is the name of the message flow that is deployed to the integration server.
If the message flow is contained in an application and not in a library:
```
$SYS/Broker/integrationNodeName/WorkloadManagement/BelowThreshold/integrationServerName
/<applicationName>/<messageFlowLabel>
```
or
```
IBM/IntegrationBus/integrationNodeName/WorkloadManagement/BelowThreshold/integrationServerName
/<applicationName>/<messageFlowLabel>
```
where integrationNodeName is the name of the integration node, integrationServerName is the name of the integration server on that integration node, application_name is the name of the application on that integration server, and messageFlowLabel is the name of the message flow that is deployed to the application.