eG Help

A message flow node is a processing step in a message flow. It can be a built-in node, a user-defined node, or a subflow node.

A message flow node receives a message, performs a set of actions against the message, and optionally passes the original message, and none or more other messages, to the next node in the message flow.

A message flow node has a fixed number of input and output points known as terminals. You can make connections between the terminals to define the routes that a message can take through a message flow.

This test auto discovers the message flow nodes in the target IBM Integration server and alerts administrators on how well the messages are processed. In addition, this test helps you to review the time taken by each node to process the input messages and the time taken by the CPU of each node to process the input messages. This way, administrators may be alerted to processing bottlenecks on the node that is currently experiencing slowdowns in processing the messages.

Measurement	Description	Measurement Unit	Interpretation
avgElapsedTime	Indicates the average time taken by this node to process the input messages.	Secs	Comparing the value of this measure across the message flow nodes helps you identify the node that is taking too long to process the input messages.
maxElapsedTime	Indicates the maximum time taken by this node to process an input message.	Secs
avgCPUTime	Indicates the average time taken by the CPU of this node to process the input messages.	Secs	The value of this measure should be equal to or less than the value of the avgElapsedTime measure.
maxCpuTime	Indicates the maximum time taken by the CPU of this node to process an input message.	Secs
invocationRate	Indicates the rate at which the messages i.e., invocations are processed by this node.	Invocations/sec	Comparing the value of this measure helps you to identify the node that is currently experiencing slowdowns in processing messages.