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:
- In the Projects window, right-click the Composite Applications project you want to debug and choose Debug (BPEL) from the pop-up menu.
The IDE establishes a debug session on the BPEL Service Engine. Watch
the BPEL Debugger Console window for confirmation.
The connection might take some time to complete. When it is successfully completed, you can see the new session in the Sessions window. On the BPEL Debugger Console tab in the Output window you can see the following messages:
17:20:01 Connecting to localhost:3343
17:20:01 Debug session started
If the BPEL Debugger Console is not visible, choose Window > Debugging > BPEL Debugger Console from the main menu.
Note that the Debug Project (BPEL) command performs the following actions:
- Enables debugging on the BPEL Service Engine (sets the DebugEnabled property of the BPEL Service Engine to true)
- Builds the BPEL Module project and adds it as a JBI Module to the Composite Application project
- Deploys the BPEL Module project to the BPEL Service Engine
- Starts the debugging session
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:
- In the Sessions window, double-click the name of the session that you want to make current or choose Make Current from the pop-up menu.
The session becomes current and the BPEL Process Instances and Local Variables windows are updated to show the data related to the new current session.
To finish a debugging session:
- In the Sessions window, open the pop-up menu for the session you want to stop and choose Finish, or select Finish Debugger Session (Shift-F5) on the toolbar.
A message that the debugging session is finished is displayed in the BPEL Debugger Console.
To finish all debugging sessions:
- In the Sessions window, right-click any session and choose
Finish All.
- 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