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

Task topic

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

Debug: stepping into 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 on entry to a node that contains ESQL code, Java code, or mappings, you can step into 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.
    Note: Mapping routines are implemented in ESQL; you can choose either to step through the ESQL code, or step through the mappings.
  1. Switch to the Debug perspective.
  2. In the Debug view, click the Step into Source Code icon Step into code on the toolbar, or right-click the flow stack frame, then click Step into Step Into.
After stepping into the code, you can step through the source code, line by line, in an environment that is optimized for source code debugging. This task is described in Stepping over source code.

You can also step out of the code, as described in Stepping out of source code; the message flow continues to run to the next breakpoint, or to completion if no further breakpoints are set.

Related concepts
Flow debugger overview
Debug perspective
Related tasks
Debug: stepping over source code
Debug: stepping out of 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

ag11330_ This topic's URL is: