Using Breakpoints to Debug BPEL Processes

See Also

Breakpoints are used to instruct the BPEL Debugger to stop execution at the specified place of a BPEL process. When a BPEL process instance reaches a breakpoint, it becomes suspended and you can step into the code, change the current process instance in the BPEL Process Instances window, track the execution of the process instance in the BPEL Process Execution window and in the Design view, examine the values of variables in the BPEL Variables window, and view the values of XPath expressions in the Watches window.

You can also use fault breakpoints to check the values of variables before a fault is thrown. For more information, see Using Fault Breakpoints in the BPEL Debugger.

To view and organize the breakpoints currently set in the IDE, open the Breakpoints window by choosing Windows > Debugging > BPEL > Breakpoints (Alt-Shift-5). For each breakpoint, you can see the name of the file and the line where this breakpoint is located.

To set a breakpoint in a BPEL process:

  1. In the IDE, open the BPEL file in either the Source or Design view.
  2. Do one of the following:
  3. In the Design view, breakpoints are displayed as small red squares on top of specific elements. In the Source view, breakpoints are shown as red squares on the left margins of code lines.

To debug a process instance that has reached a breakpoint:

To remove a breakpoint from the BPEL process, do one of the following:

To disable a breakpoint:

See Also
Setting a Java Breakpoint
Stepping Through Your Program
Starting and Finishing a BPEL Debugging Session
Using Watches to Debug BPEL Processes
Using Fault Breakpoints in the BPEL Debugger

Legal Notices