This specification provides a usecases for BPEL debugger for Service Oriented Architecture features within Netbeans Enterprise Pack Beta2 and explains methods of testing a debugger for BPEL processes . It uses Synchronous, Asynchronous and TravelReservationService sample projects from SOA samples as examples of BPEL processes to be debugged. Check different ways to start debug session. Start the IDE. Start Sun Java System Application Server. Create a new BPEL project from "Samples | Service Oriented Architecture " project. Start Sun Java Application Server. Switch to Runtime tab. Expand "Sun Java System Application Server/JBI/Service Engines/com.sun.bpelse" and call Properties from the context menu. Set "DebugEnabled" property to false. Set "DebugEnabled" property to true. "com.sun.bpelse - Properties" window appears. "DebugEnabled" property is set to false. "DebugEnabled" property is set to true. Start Sun Java Application Server. Switch to Runtime tab. Expand "Sun Java System Application Server/JBI/Service Engines/com.sun.bpelse" and call Properties from the context menu. Set "DebugPort" property to 3344. Set "DebugPort" property to 3343. "com.sun.bpelse - Properties" window appears. "DebugPort" property is set to 3344. "DebugPort" property is set to 3343. Start Sun Java Application Server. Switch to Runtime tab. Expand "Sun Java System Application Server/JBI/Service Engines/com.sun.bpelse" and call Properties from the context menu. Set "DebugEnabled" property to true. Be sure that "DebugPort" property is set to 3343 if not then adjust it and restart the application server. Attach debugger, select BPEL debugger and set a host to localhost and a port to 3343. Stop debug session. "com.sun.bpelse - Properties" window appears. "DebugEnabled" property is set to true. "DebugPort" property is set to 3343. The application server is running, BPEL service engine started. BPEL Debugger Console shows "Connecting to localhost:3343. Debug session started." BPEL Debugger Console shows "Debug session finished." Start Sun Java Application Server. Switch to Runtime tab. Expand "Sun Java System Application Server/JBI/Service Engines/com.sun.bpelse" and call Properties from the context menu. Check that "DebugEnabled" is set to true otherwise set it to true. Set "DebugPort" property to 3344. Restart the application server. Attach debugger, select BPEL debugger and set a host to localhost and a port to 3343. Attach debugger, select BPEL debugger and set a host to localhost and a port to 3344. Stop debug session. "com.sun.bpelse - Properties" window appears. "DebugEnabled" property is set to true. "DebugPort" property is set to 3344. The application server is running, BPEL service engine started. BPEL Debugger Console shows "Unable to start debug session: Unable to connect to localhost:3343 : Connection refused". BPEL Debugger Console shows "Connecting to localhost:3344. Debug session started." BPEL Debugger Console shows "Debug session finished." Start Sun Java System Application Server on another machine, set there DebugEnabled to true and check DebugPort (e.g. 3343). Attach debugger, select BPEL debugger and set a host to the name of the machine where AS is running and a port to appropriate value. Stop debug session. On remote machine "DebugEnabled" property is set to true and "DebugPort" property is set to 3343 ,the application server is running, BPEL service engine started. BPEL Debugger Console shows "Connecting to (remotehostname):3343. Debug session started." BPEL Debugger Console shows "Debug session finished." Check Debugger windows features. Start the IDE. Start Sun Java System Application Server. Create a new BPEL project from "Samples | Service Oriented Architecture " project. Start a debug session. Set a breakpoint in the BPEL source. Deploy the BPEL process. Run test scenario. Wait until the breakpoint is reached. Open the "BPEL Variables" debug window via the "Window | Debugging | BPEL" menu Open the "Watches" debug window via the "Window | Debugging" menu Open the "Breakpoints" debug window via the "Window | Debugging | BPEL" menu Open the "Sessions" debug window via the "Window | Debugging | BPEL" menu Open the "BPEL Process Instances" debug window via the "Window | Debugging | BPEL" menu Open the "BPEL Console" debug window via the "Window | Debugging | BPEL" menu The "BPEL Variables" debug window appears. It contains Name, Type and Value columns. The "Watches" debug window appears. It contains Name, Type and Value columns. The "Breakpoints" debug window appears. It contains Name and Enabled columns. The "Sessions" debug window appears. It contains Name, State and Language columns. The "BPEL Process Instances" debug window appears. It contains Name, State and Suspended columns. The "BPEL Console" debug window appears Open the "BPEL Variables" debug window via the "Window | Debugging | BPEL" menu The "BPEL Variables" debug window appears. It contains Name, Type and Value columns. Open the "Watches" debug window via the "Window | Debugging" menu Create a new Watch using valid xPath expression The "Watches" debug window appears. It contains Name, Type and Value columns. The xPath expression and its value appear in the Watches window. Open the "Breakpoints" debug window via the "Window | Debugging | BPEL" menu The "Breakpoints" debug window appears. It contains Name and Enabled columns. Open the "Sessions" debug window via the "Window | Debugging | BPEL" menu The "Sessions" debug window appears. It contains Name, State and Language columns. Open the "BPEL Process Instances" debug window via the "Window | Debugging | BPEL" menu The "BPEL Process Instances" debug window appears. It contains Name, State and Suspended columns. Open the "BPEL Console" debug window via the "Window | Debugging | BPEL" menu The "BPEL Console" debug window appears Check that breakpoints can be set and modified in BPEL project Open TravelReservationService sample project. Open TravelReservationService.bpel in the Editor. Open "Breakpoints" debug window. Click on a gutter in the source editor next to the certain line Uncheck the checkbox in the column Enabled in the Breakpoints window. Check the checkbox in the column Enabled in the Breakpoints window. Click on a gutter in the source editor next to the same line A new breakpoint is added, breakpoint annotation is added to the editor and "Breakpoints" window is updated accordingly The breakpoint is disabled, breakpoint annotation is greyed in the editor and "Breakpoints" window is updated accordingly. The breakpoint is enabled, breakpoint annotation is enabled in the editor and "Breakpoints" window is updated accordingly. The breakpoint is removed, breakpoint annotation is removed from the editor and "Breakpoints" window is updated accordingly. Right-click on the element in Designer and choose Toggle Breakpoint Uncheck the checkbox in the column Enabled in the Breakpoints window. Check the checkbox in the column Enabled in the Breakpoints window. Right-click on the same element in Designer and choose Toggle Breakpoint A new breakpoint is added, breakpoint annotation is added to the editor and "Breakpoints" window is updated accordingly The breakpoint is disabled, breakpoint annotation is greyed in the editor and "Breakpoints" window is updated accordingly. The breakpoint is enabled, breakpoint annotation is enabled in the editor and "Breakpoints" window is updated accordingly. The breakpoint is removed, breakpoint annotation is removed from the editor and "Breakpoints" window is updated accordingly. Right-click on the element in Navigator and choose Toggle Breakpoint Uncheck the checkbox in the column Enabled in the Breakpoints window. Check the checkbox in the column Enabled in the Breakpoints window. Right-click on the same element in Navigator and choose Toggle Breakpoint A new breakpoint is added, breakpoint annotation is added to the editor and "Breakpoints" window is updated accordingly The breakpoint is disabled, breakpoint annotation is greyed in the editor and "Breakpoints" window is updated accordingly. The breakpoint is enabled, breakpoint annotation is enabled in the editor and "Breakpoints" window is updated accordingly. The breakpoint is removed, breakpoint annotation is removed from the editor and "Breakpoints" window is updated accordingly. Click on some line in the source editor then call "Run | Toggle Breakpoint" from the main menu. Right-click on the breakpoint in the column Name in the Breakpoints window and call "Disable" from the popup menu. Call "Run | Toggle Breakpoint" from the main menu one more time. A new breakpoint is added, breakpoint annotation is added to the editor and "Breakpoints" window is updated accordingly The breakpoint is disabled, breakpoint annotation is greyed in the editor and "Breakpoints" window is updated accordingly. The breakpoint is removed, breakpoint annotation is removed from the editor and "Breakpoints" window is updated accordingly. Click on some line in the source editor then press "Ctrl+F8. Press "Ctrl+F8 one more time. A new breakpoint is added, breakpoint annotation is added to the editor and "Breakpoints" window is updated accordingly The breakpoint is removed, breakpoint annotation is removed from the editor and "Breakpoints" window is updated accordingly. Set several breakpoints in the source editor. Select all lines in the the Breakpoints window, right-click on them and call "Disable" from the popup menu. Select all lines in the the Breakpoints window, right-click on them and call "Enable" from the popup menu. Remove all the breakpoints in the source editor. All breakpoints are added, breakpoint annotations are added to the editor and "Breakpoints" window is updated accordingly All the breakpoints are disabled, breakpoint annotations are greyed in the editor and "Breakpoints" window is updated accordingly. All the breakpoints are enabled, breakpoint annotations are enabled in the editor and "Breakpoints" window is updated accordingly. All the breakpoints are removed, breakpoint annotations are removed from the editor and "Breakpoints" window is updated accordingly. Check that the debugger toolbar is accessible while debug session and its buttons work properly. Start the IDE. Start Sun Java System Application Server. Create a new BPEL project from "Samples | Service Oriented Architecture " project. Deploy the project. Start a debug session. When user starts a debug session debug toolbar appears. There are the following buttons on toolbar. Finish debug session - enabled, Pause - disabled, Continue - disabled, Step Over - disabled, Step Into - disabled, Step Out - disabled, Run to Cursor - disabled, New Watch... - enabled Functionality is not Accessible, the button is disabled. Set a breakpoint in the process then run test. Click on Continue button or press Ctrl+F5. The process suspends when the breakpoint is reached. The process resumes. Functionality is not accessible, the button is disabled. Set a breakpoint in the process then run test. Click on StepInto button or press F7. The process suspends when the breakpoint is reached. The process resumes performs one activity then suspends. Functionality is not accessible, the button is disabled. Functionality is not accessible, the button is disabled. Click on New Watch... button A New Watch dialog window appears. Click on the Finish Debug Sssion button or press Shift+F5. Start a new debug session. Set a breakpoint in a bpel peocess Run a test. Click on the Finish Debug Sssion button or press Shift+F5. Debug session finishes. All debug windows close. A new debug session starts. A breakpoint is set. The breakpoint is reached. The process suspends. All debug windows are updated accordingly. The process resumes and completes. Check that the BPEL process instance can be debugged and breakpoints are processed correctly. Open the TravelReservationService sample project. Open the TravelReservationService.bpel in the Editor, switch to Source view. Set a breakpoint. Start a new debug session. Open debug windows. Select the "Run" context menu item for the "TravelReservationService | Processes | TravelReservationService.bpel | Test Scenarios | HasHotel" node Switch to the Source editor window Switch to the "Threads" debug window Switch to the "Local variables" debug window A new process instance starts, reaches the breakpoint and gets suspended The current position (where process instance have stopped) is marked in the Source editor and the cursor is set on that position The corresponding record in the "Threads" window has state "suspended" The "Local variables" window is populated with the variable values of the "current" process instance. Press the "Step Into" button on the toolbar Press "F7" Process instance change it's state to "running" performs one step and gets suspended. The "Local variables" window is updated Process instance change it's state to "running" performs one step and gets suspended. The "Local variables" window is updated Press the "Continue" button on the toolbar or "F5" Run the "HasHotel" test scenario one more time and press the "F5" key when it stops at the breakpoint Process instance continue working till the end and gets completed. The "Local variables" window is cleared. Process instance continue working till the end and gets completed. The "Local variables" window is cleared. Create a Flow activity. Add some activities into the Flow so they are in different threads of the Flow. Redeploy the bpel process. Set a breakpoint to the Flow activity. Run test from CompositeApplication/Test Do StepInto steadily to perform an activities inside the Flow. Do continue to complete execution. The Flow activity contains several activities in different threads. The deployed process is updated. Breakpoint is set. The breakpoint is reached, the process becomes suspended. Debug widows are updated accordingly. All activities inside the Flow are performed in indefinite order. Bpel process completes. Add Throw activity to the process. Add CatchAll fault handler to the process and put some activities inside it. Redeploy the bpel process. Set a breakpoint to an activity inside the CatchAll fault handler. Run test from CompositeApplication/Test Do StepInto to perform an activityinside the the CatchAll fault handler. Do continue to complete execution. A new CatchAll fault handler is added to the process. The deployed process is updated. Breakpoint is set. The breakpoint is reached, the process becomes suspended. Debug widows are updated accordingly. An activity is performed, debug widows are updated accordingly. Bpel process completes. Check that several BPEL process instances can be debugged simultaneously Open the TravelReservationService sample project. Open the TravelReservationService.bpel in the Editor. Set a breakpoint. Start a new debug session. Open debug windows User can switch between process instances in the "BPEL Processes" window by marking one of them as "current". There can be only one thread marked as "current". Select the "Run" context menu item for the "TravelReservationService | Processes | TravelReservationService.bpel | Test Scenarios | HasHotel" node Press the "Step Into" button on the toolbar Select the "Run" context menu item for the "TravelReservationService | Processes | TravelReservationService.bpel | Test Scenarios | HasAirline" node A new process instance starts, reaches the breakpoint and gets suspended Process instance change it's state to "running" performs one step and gets suspended. The "Local variables" window is updated. The current position (where process instance have stopped) jump to the next executable line in the Source editor and the cursor is set on that position A new process instance starts, reaches the breakpoint and gets suspended. A new process appears in the "BPEL Processes" debug window. Now both threads are suspended. The current position (where process instance have stopped) is set to breakpoint line in the Source editor and the cursor is set on that position Double-click on the first thread in the "BPEL Processes" debug window Right-click on the last thread in the "BPEL Processes" debug window and select "Make Current" in the context menu Press the "Continue" button on the toolbar or "F5" Double-click on the first thread in the "BPEL Processes" debug window and press the "Continue" button on the toolbar or "F5" The current position is updated according the first process state in the Source editor and the cursor is set on that position The current position is updated according the second process state in the Source editor and the cursor is set on that position The second process instance continue working till the end and the second thread gets completed. The first process instance continue working till the end and the first thread gets completed. Creaet an Asynchronous sample application. Add AsynchronousSample as JBI module to the AsynchronousSampleApplication. Deploy the AsynchronousSampleApplication. Set Breakpoints in the AsynchronousSample.bpel and in AsynchronousSampleClient.bpel on the "invokepartner" activity. Run a test from AsynchronousSampleApplication/Test. Do StepInto twice. Switch to AsynchronousSample process and do StepInto until it completes. Press Continue to compelte AsynchronousSampleClient process. AsynchronousSample and AsynchronousSampleApplication appear inthe project tree. AsynchronousSampleApplication is deployed. A new AsynchronousSampleClient BPEL process appears in BPEL processes debug window, reaches the breakpoint and becomes suspended. A new AsynchronousSample BPEL process appears in BPEL processes debug window, reaches the breakpoint and becomes suspended. The AsynchronousSampleClient BPEL process becomes running. The AsynchronousSample BPEL process becomes completed then disappears from the BPEL processes debug window. The AsynchronousSampleClient BPEL process becomes suspended. The AsynchronousSampleClient BPEL process becomes completed then disappears from the BPEL processes debug window. Check that IDE allows to switch between several debug sessions. Start the IDE. Start Sun Java System Application Server. Create a new BPEL project from "Samples | Service Oriented Architecture " project. Start BPEL debug session. Deploy BPEL process. Create a new java application. Set some breakpoints in java code. Debug the java application. A new Java Application appears in the Projects tree. Breakpoints appear in java editor and in the Breakpoints debug window. A new debug session starts and appears in the Sessions debug window. Open the Sessions debug window. Double-click on BPEL debug session in the Session debug window. Double-click on Java debug session in the Session debug window. Right-click on BPEL debug session in the Session debug window and choose "Make current" from the context menu. Right-click on Java debug session in the Session debug window and choose "Make current" from the context menu. Sessions debug window appears and shows existing BPEL and Java debug sessions. The BPEL debug session becomes active and its name is decorated in bold font. The content of other debug windos is updated according the current state of the BPEL process. The Java debug session becomes active and its name is decorated in bold font. The content of other debug windos is updated according the current state of the Java process. The BPEL debug session becomes active and its name is decorated in bold font. The content of other debug windos is updated according the current state of the BPEL process. The Java debug session becomes active and its name is decorated in bold font. The content of other debug windos is updated according the current state of the Java process. Check that the debug session can be finished Open the TravelReservationService sample project. Start a new debug session. Open debug windows. Press the "Finish" button on the toolbar or press "Shift+F5" The debug toolbar disappears. The "BPEL variables" and "BPEL Processes" window are cleared. The "BPEL variables" and "BPEL Processes" window are cleared. The Debug sessions finishes. The Debugger console output window is updated with notification "hh:mm:ss Debug session finished" Select "Finish" or "Finish All" menu item in the session context menu in the Sessions debugger window. The debug toolbar disappears. The "BPEL variables" and "BPEL Processes" window are cleared. The "BPEL variables" and "BPEL Processes" window are cleared. The Debug sessions finishes. The Debugger console output window is updated with notification "hh:mm:ss Debug session finished"