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

Debug: stepping through source code

When message flow processing has paused at a breakpoint on entry to a node that contains ESQL code or Java™ code, you can step through the code.

Before you start:

Add one or more breakpoints to your message flow. See Adding breakpoints in the flow debugger.

The nodes that can contain ESQL code or Java code are listed in: Flow debugger overview. Add breakpoints as appropriate:
  • ESQL code: add a breakpoint in the ESQL code.
  • Java code: add a breakpoint in the Java code.

To step through your source code:

  1. Switch to the Debug perspective.
  2. Step into the source code. In the Debug view:
    • either, click Step into Source Code Step into code on the toolbar.
    • or, right-click the flow stack frame, then click Step Into Step Into.
  3. When message flow processing has paused at a breakpoint within ESQL code or Java code, you can step through the source code, line by line. Repeat this step as often as necessary. In the Debug view:
    • either, click Step Over Step Over on the toolbar.
    • or, right-click the flow stack frame, then click Step Over Step Over.
    A single line of source code runs and the flow pauses at the next line of code. What you can do depends on what type of code is contained within the node. See:

    If the debugger is paused before the last line of code when you step over, the last line of code runs and message flow processing continues until the next breakpoint 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.

  4. If you have finished looking at the code before the last breakpoint, you can continue processing the message flow. In the Debug view:
    • either, click Step Return Step Return on the toolbar.
    • or, right-click the flow stack frame, then click Step Return Step Return.
    The source code runs to completion from the current breakpoint and 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 completed debugging this message flow, you can remove the breakpoints or end the debugging session:
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:47:03


Task topicTask topic | Version 8.0.0.7 | ag11330_