If you have followed all tutorial parts so far, you have deployed and run a BPEL process on the Process Server.
In the Project Explorer view of Process Developer, you should have the following files:
that you created in Part 4
that you created in Part 9
After completing Part 11 of the tutorial, you will be able to:
Add a breakpoint to
Create a configuration file for launching a remote debugging session.
Start a remote debugging session.
Step through your process and inspect variables.
Step 1: Add a Breakpoint to tutorial.bpel
You can connect to a running or completed process from within Process Developer for remote debugging. There are several options for remote debugging, and we will set a breakpoint in the process and then attach to the running process when the breakpoint is hit.
in the Process Editor.
Right-mouse click on the Receive activity and select Add Breakpoint. The Receive activity should look like the following example.
The server must be running in order to start remote debugging, so start the server now (if it is not already running) before setting up a debug configuration.
If the server is already running, as described in Part 10 of the tutorial, you can skip to Step 3.
Select the Servers view in the lower right of the workspace, and select Start the Server.
Step 3: Create a Configuration for Launching a Remote Debug Session
A remote debug configuration indicates where processes are running and how you want to attach to them.
From the Run menu, select Debug Configurations.
dialog, select Remote Process and then select the New Launch Configuration icon in the toolbar.
In the Name field, type
In the Main tab, note that the default Server URL is displayed for deployed server processes.
In the Process Selection panel, select Manual process selection or breakpoints. This selection indicates that you do not want to immediately debug a process, but rather will select a process manually.
Enable the option Attach to any process on breakpoint to indicate that a process containing a breakpoint will be attached to, if not already attached, when a breakpoint is hit.
Debug Create, manage, and run configurations
dialog should look like the following example.
Select Debug to begin remote debugging for the current configuration.
Your Debug view should look like the following example.
Step 4: Instantiate the Process
You can create an instance of the process by using the Process Central request form, as you did in Part 10 of the tutorial.
In Process Central, fill in the form with Last Name of
and amount-Requested value of
Select Send Request.
Step 5: Begin Remote Debugging
In Process Developer, open all variables in the Process Variables view and position the view next to the Process Editor canvas. Your Process Editor should look like the following example.
Notice that the running process is stopped on the Receive activity with the breakpoint, as we configured.
In Debug view, click the Step Into icon on the toolbar. The debug highlighter moves to the Invoke Risk Assessor activity. The
variable displays the data submitted by the Process Central request.
Click Step Into twice to terminate and disconnect the process automatically.
variable. Notice that Jones is not going to get a loan. The reply indicates a decline, as shown.
Repeat the above steps by adding different
The LoanApproval and RiskAssessment services are built on the following logic:
5000 <loan amount <=20000
Jones is declined, all others approved
Only Smith is approved, all others declined
Create a new orchestration project for Human Approval Completed. This process replaces the Invoke Loan Approval activity with a People activity, as shown in the illustration. The documentation that accompanies the Human Task (BPEL for People) sample describes how to deploy and run the sample. You can also review the Human Tasks help for details on building a People activity to add human workflow to your BPEL process.