Stepping into component elements in the integration debugger

Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15

Depending on the kind of business integration component that you are debugging, you can use the integration debugger to step into component elements.

Before you begin

The elements that you can step into for each kind of business integration component are listed in the following table:

Business integration component	Elements that can be stepped into
Business processes	Java™ snippets, visual snippets
State machines	None
Business object data maps	Submaps, Java snippets,
Business rules	Rule set templates
Visual snippets	Custom visual snippets, Java visual snippets
Mediation flows	Subflows

To step into component elements:

In the Debug view, ensure that the correct stack frame is selected.
In the component editor, ensure that the component thread is paused at a position immediately before the element that you want to step into. For example, if you want to step into a Java snippet in the business process editor, you must ensure that the Java snippet activity has an entry breakpoint on it and that the component thread is paused before the breakpoint.
In the Debug view, click the Step Into icon . The element that you are stepping into opens and the component thread pauses at the first location where a breakpoint exists or can be set. For example, if you step into a Java snippet, the component thread pauses at the first line of code that contains a breakpoint or where you could set a breakpoint.