To start and finish a debugging session on the BPEL Engine

1. In the Projects window, right-click the Composite Applications project you want to debug and choose Debug (BPEL) from the pop-up menu.

   A debug session is established on the BPEL Service Engine.

   11:35:17 Connecting to localhost:3343

   • Enables debugging with the BPEL Service Engine (sets the DebugEnabled property of the BPEL Service Engine to true)

   • Builds the Composite Application project and all JBI Modules added to this project

   • Deploys the Composite Application project to the BPEL Service Engine

   • Starts the debugging session by connecting the BPEL Debugger to the BPEL Service Engine

   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.

   If you have several debugging sessions (you may have a Java debugging session running at the same time) and want to change the current session, double-click the name of this session in the Sessions window. Alternatively, right-click the session you want to make current and select Make Current. This session becomes current and the BPEL Process Instances, Watches and Local Variables Windows are updated to show the data related to the new current session.

   When you want to finish a debugging session, open the pop-up menu for the session you want to stop and choose Finish in the Sessions window or select Finish Debugger Session 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.

2. 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 and the following messages in the BPEL Debugger Console:

   • 11:35:17 Connecting to localhost:3343

   • 11:36:19 Debug session started

     The Debug (BPEL) command performs the following actions:

     • Enables debugging with the BPEL Service Engine (sets the DebugEnabled property of the BPEL Service Engine to true)

     • Builds the Composite Application project and all JBI Modules added to this project

     • Deploys the Composite Application project to the BPEL Service Engine

     • Starts the debugging session by connecting the BPEL Debugger to the BPEL Service Engine 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

3. Now, 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.

   If you have several debugging sessions (you may have a Java debugging session running at the same time) and want to change the current session, double-click the name of this session in the Sessions window. Alternatively, right-click the session you want to make current and select Make Current. This session becomes current and the BPEL Process Instances, Watches and Local Variables Windows are updated to show the data related to the new current session.

4. To finish a debugging session, open the pop-up menu for the session you want to stop and choose Finish in the Sessions window, or select Finish Debugger Session on the toolbar.

   A message that the debugging session is finished is displayed in the BPEL Debugger Console.

5. To finish all debugging sessions, in the Sessions window, right-click any session and choose Finish All.