The IBM Integration Bus (IIB) Agent allows you to see the activity flow in your IIB instance. You can use the AppDynamics IIB Agent to do the following:
- Correlate business transactions that flow through IIB to identify where time is spent processing transactions in the larger end-to end architecture.
- Measure where business transaction processing time is spent within IIB flows, allowing operations staff and flow developers to identify any bottlenecks within the flows.
This page describes IBM IIB in the context of it being monitored by AppDynamics. For a full description of IBM IIB and its capabilities, refer to the IBM product documentation.
How It Works
The agent supports inbound and outbound correlation for HTTP, JMS, and IBM MQ messaging nodes. You can identify business transactions that originate in the broker itself by the transaction name, which contains the message flow name and the message flow node name where the BT originated.
To measure where the time is spent within the flows, the agent models each message flow node as a thread (with thread names corresponding to the message flow node name). You can view the per-node timings in the tree view of the Business Transactions dashboard for any business transaction that passed through IIB, as shown below:
The IIB Agent also reports message flow node timing data, represented as thread segments in transaction snapshots, for business transactions that flow through IIB. Message flow node timing data is displayed in the Waterfall View.
Each broker is represented in the AppDynamics flow map as a tier, which is named as you specified in the configuration. Individual broker processes register with AppDynamics as nodes. The node names are generated from the Broker name and the Execution Group name.
<node-reuse-prefix>prefixName</node-reuse-prefix> property when
node-reuse is set to
true. If you do not set this property, the IIB agent generates node names as per the internal node name standards of IBM. See Enable the Node Name Reuse.