ag11050_.htm |
Last updated Friday, 21 July 2017Use the flow debugger in the IBM® Integration Toolkit to track messages through your message flows.
Use the Debug perspective in the IBM Integration Toolkit to use the flow debugger. For an introduction to the Debug perspective and the views it presents, see Debug perspective.
You can set breakpoints in a message flow, then step through the flow. While you are stepping through, you can examine and change the message variables and the variables used by ESQL code and Java™ code. You can debug a wide variety of error conditions in flows, including the following:
From a single IBM Integration Toolkit, you can attach the debugger to one or more integration servers, and debug multiple flows in different integration servers (and therefore multiple messages) at the same time. However, an integration server can be debugged by only one user at a time. Therefore, if you attach your debugger to an integration server, another user cannot attach a debugger to that same integration server until you have ended your debugging session.
When you debug message flows, use a broker that is not being used in a production environment. Debugging might degrade the performance of all message flows in the same integration server and those in other integration servers that share the same broker because they might be affected by potential resource contention.
You can use the flow debugger to examine the behavior of code in message flow nodes.
After you have deployed a message flow, you can set a breakpoint just before one of the nodes listed in this section so that, when the flow pauses at the breakpoint, you can step through the code line by line. This allows you to examine the logic, and check the actions taken and their results. You can set additional breakpoints and you can also examine and change variables.
Last updated Friday, 21 July 2017