Describes how to calculate and set the message flow notification threshold.
Before activating the message flow notification threshold, the system administrator must first establish what message rate is required for the message flow in question. The message rate is a measure of the total number of messages arriving each second at the message flow from all input nodes of any type. It is the total rate and not the average rate. For example: A message flow contains two input nodes that are called A and B. If input node A received messages at the rate of 50 messages a second, and input node B received messages at the rate of 70 messages a second, then the total message rate for the message flow would be 120 messages per second.
The notification threshold is set within the BAR file under a property called notificationThresholdMsgsPerSec.
Additionally, once the BAR file is deployed, the property can be set dynamically within the flow through the IBM Integration API. Any change to the property is picked up immediately and does not require the flow to be restarted.
A notification threshold value of zero, or not set, will cause the message flow notification threshold to be turned off. The default state is off.
Within the same integration server, a mixture of message flows can run along side each other, some with the notification threshold set, others with the notification threshold turned off.