Stepping into source code

Before you start

Complete the following tasks:

The flow being debugged must be paused at a breakpoint before a node containing ESQL code or Java code.

In a message flow there are three types of node that can contain source code:
  • Built-in nodes: a Compute node, Filter node, or Database node that contains ESQL code.
  • User-defined Java plug-in nodes that contain Java code.
  • Nodes used to access and maintain mappings: a Mapping node, DataInsert node, DataUpdate node, DataDelete node, Extract node, or Warehouse node that contains mapping routines.
When you stop at a breakpoint just before one of the above types of node, you can choose how to step past the code:

To step into source code:

  1. Switch to the Flow Debug perspective.
  2. In the Flow Debug view, click the Step into Source Code icon Step into Source Code on the toolbar (or right-click the flow stack frame, then click Step Into Step Into). The perspective automatically changes from the Flow Debug perspective to the Debug perspective, which enables you to step over (that is, step through) the source code, line by line, in an environment that is optimized for source code debugging.
Note: If you want to step out of the source code after you have finished stepping through it, see Stepping out of source code.
Related concepts
Flow debugger overview
Related tasks
Debugging a message flow
Stepping over source code
Stepping out of source code
Related reference
Flow debugger shortcuts
Flow debugger icons and symbols