In the Project Explorer, right-click on the

loanProcessHuman.bpel

process and select

New > Deployment Descriptor

to open the

New Deployment Descriptor

dialog.

Select the

deploy

folder, and press

Finish

, as shown.

The

loanProcessHuman.pdd

file opens in the PDD editor The properties of the General tab are displayed.

Accept the defaults on the General tab and press the Partner Links tab to define the bindings to the web services called by the process.

Set the runtime bindings for the CustomerService partner link by clicking on the CustomerService row and set the following properties:

Invoke Handler
:
WSA Address
Endpoint type
:
static
Press the ellipses (...) button next to the textarea labeled Endpoint Reference to open the
Endpoint Reference
dialog
Select the
loanCRM.wsdl
file from the WSDL picklist.

Press
OK
.

Set the runtime binding information for the RiskAssessment partner link by selecting the RiskAssessment row and set the following properties:

Invoke Handle
r: WSA Address
Endpoint type
: static
Press the ellipses (...) button next to the textarea labeled Endpoint Reference to open the
Endpoint Reference
dialog
Select the
riskAssessment.wsdl
file from the WSDL picklist.

Press
OK
.

Next set the runtime binding information for the LoanProcess partner link by selecting the LoanProcess row and setting the following properties:

Binding
: Document Literal
Service
: LoanProcess Note that this name must match the Service name selected in the
HumanApproval.html
request form, described in
Creating a Request Form
above.

The final step is to bind the Logical People Groups to actual server roles. Select the People tab and notice that the Logical People Groups are already assigned to names in the

tomcat-users.xml

file for the Process Developer embedded server Identity Service. Because Identity Service group names are used in the People activity, they are already selected here.

Save the file.