IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Adding breakpoints in the flow debugger

Add breakpoints to connections in your message flow to control where flow processing will pause.

Before you start:

Attach the flow debugger to the integration server where your flow is deployed. See: Attaching the flow debugger to an integration server for debugging.

You can add breakpoints to the connections of a message flow that is open in the Message Flow editor. Each breakpoint that you add to a flow is also automatically added to all other instances of the flow and you do not need to restart any of the instances.

Every breakpoint is automatically enabled when you add it to a connection and the connection is flagged with the enabled breakpoint symbol .

Manually set a breakpoint after the collector node or any other multithreaded node. When you use the Debug perspective on the node, you see that the thread has been ended.

To add breakpoints to the connections of a message flow:

Switch to the Debug perspective.

Add breakpoints to the appropriate connections. Use any of the following methods:

Option	Method
Add breakpoints individually to selected connections.	In the Message Flow editor, right-click the connection where you want to set the breakpoint. Click Add Breakpoint.
*Add breakpoints simultaneously to all connections entering* a selected node.**	In the Message Flow editor, right-click the node before which you want to set breakpoints. Click Add Breakpoints Before Node.
*Add breakpoints simultaneously to all connections leaving* a selected node.**	In the Message Flow editor, right-click the node after which you want to set breakpoints. Click Add Breakpoints After Node.

Next:

After you have set one or more breakpoints in the message flow, step through the flow, pausing at each active breakpoint. See: Stepping through message flow instances in the debugger.

You can also examine message data, code, and mappings at appropriate points. See: Debugging data.

ag11210_.htm |

Last updated Friday, 21 July 2017