Starting and Finishing a BPEL Debugging Session

See Also

A debugging session begins when you start the BPEL Debugger on the BPEL Service Engine. Only one debugging session can be running on the BPEL Service Engine at a given time. However, several Java debugging sessions can be started at the same time.

After a BPEL debugging session starts, you can execute process instances step-by-step, inspecting the values of BPEL variables and XPath expressions in the Local Variables and Watches windows. You can monitor the execution of a BPEL process within a debugger session on the diagram in the Design view: the activities that are being executed are highlighted on the diagram as the current execution position advances. The BPEL Process Execution window also shows the execution of the BPEL process.

To prepare for debugging:

To start a debugging session on the BPEL Service Engine:

Note that the Debug Project (BPEL) command performs the following actions:

Therefore, whenever you start a debugging session you can be sure that the latest version of the BPEL process is deployed on the BPEL Service Engine.

Now you can run a test case and monitor the execution of the BPEL process until it stops or reaches a breakpoint. As the process advances, the current context is displayed on the diagram and in the BPEL Process Execution window.

To change the current debugging session:

To finish a debugging session:

To finish all debugging sessions:

See Also
About Debugging Java Applications
Starting and Stopping a Server
BPEL Debugger Windows
Using Breakpoints to Debug BPEL Processes
Using Watches to Debug BPEL Processes
Logging and Alerting

Legal Notices