The flow debugger is a facility provided in the Debug perspective in the workbench that you can use to debug your message flows.
Use the flow debugger to test your message flows. The visual interface makes it straightforward to catch the flow at any point and examine or alter the message state before stepping to the next point.
You can set breakpoints in a flow and then step through the flow. While you are stepping, you can examine and change the message and the variables used by ESQL code, Java code, and mappings. These capabilities enable you to debug a wide variety of error conditions in flows, including:
From a single workbench, the debugger can attach to more than one execution group, and debug multiple flows in different execution groups (and therefore multiple messages) at the same time. However, a deployed flow in one execution group can be debugged by only one user at a time. If you attach your debugger to a flow, another user can attach to the same execution group, but they cannot see the flow that you are debugging.
You cannot debug flows that you have deployed to a 64-bit execution group; only 32-bit execution groups are supported by the flow debugger.
For more information about the nodes that you can debug, see the following topics:
After reading this conceptual overview, follow the guidance given in Debugging a message flow to debug your message flows.
For an introduction to the Debug perspective and the views it presents, see Debug perspective.