WebSphere Message Brokers
File: ag11340_
Writer: John Morris-Smith

Task topic

This build: July 31, 2007 21:29:46

Debug: stepping out of source code

Before you start

To complete this task, you must have completed the following tasks:

When message flow processing has paused at a breakpoint within ESQL code, Java code, or mappings, you can step out of the code.

In a message flow there are three types of node that can contain source code:
  • Nodes that contain ESQL code: Compute node, Filter node, or Database node.
  • Nodes that contain Java code: user-defined node containing Java code, or JavaCompute node.
  • Nodes used to access and maintain mappings: a Mapping node, DataInsert node, DataUpdate node, DataDelete node, Extract node, or Warehouse node.

    Mapping routines are implemented in ESQL; if you step into the code, you can choose either to step through the ESQL code, or to step through the mappings.

  1. Switch to the Debug perspective.
  2. In the Debug view, click the Step Return icon 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 breakpoint at which the flow instance can pause, the flow instance runs to completion and is removed from the Debug view.

If you have now completed debugging this message flow, you can remove the breakpoints, or end the debug session:

Related concepts
Flow debugger overview
Debug perspective
Related tasks
Debug: stepping into source code
Debug: running to completion
Related reference
Flow debugger shortcuts
Flow debugger icons and symbols
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:29:46

ag11340_ This topic's URL is: