WebSphere Message Broker, Version 8.0.0.7
Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS
See information about the latest product version
See information about the latest product version
Debug: stepping into subflows
When message flow processing pauses at a breakpoint, you can step into the subflow that follows.
Before you start:
Add one or more breakpoints to your message flow. See: Adding breakpoints in the flow debugger.
To step into a subflow:
The subflow opens in the Message Flow editor and displaces the parent message flow. Message flow processing continues until the next breakpoint that is set in the logical processing of the current message. If there is no further enabled breakpoint at which the flow instance can pause, processing runs to completion and the flow instance is removed from the Debug view.
Next:
If you have finished debugging, you can remove the breakpoints, or end the debugging session: