Java Reference
In-Depth Information
CustomerLookupService role from “role1” to “lookupRole”. Doing this is a convenience for
writing the following text in your local WSDL file copy:
<plnk:partnerLinkType name="CustomerLookupService">
<plnk:role name="lookupRole" portType="tns:CustomerLookupService"/>
</plnk:partnerLinkType>
Now you're done creating the partner, and you can start creating the process that will invoke
it.
Creating the process
Now you're ready to create the business process that will invoke this partner service. In the
Project view, right-click on the project name and choose New→BPEL Process. In the file-
name field, enter
CustomerProcess
. For the target namespace, change the default value to
http://soacookbook.com/bpel/CustomerProcess
.
This will create a file with a .bpelextension that will contain your executable business process.
Now you're ready to add BPEL activities to orchestrate your business process.
NOTE
You can't import an existing BPEL process into a BPEL project directly from within NetBeans. If
you want to start a new BPEL project from an existing .bpelfile, go to the filesystem and copy it
directly into the <project-name>/srcfolder.
Adding a partner to the process
Back in the Process Design view, in the Web Services palette, click the Partner Link label and
drag it onto the righthand side of the canvas. An orange circle will illuminate near the middle,
indicating where you can drop the partner link. A dialog box will then pop up, containing the
name of your newly added WSDL file and some other default values.
Leave “Use an Existing Partner Link Type” as it is. It should have your
PartnerLinkType
selected. Click the Swap Roles button to move the “lookupRole” from the My Role field into
the Partner Role field, and click OK to save your changes. This will create a representation of
the invokable partner web service on the righthand side of the canvas.
Now that you have made the web service available for the process to invoke, you need a way
for clients to invoke the process.
