Consider GlassFish ESB v2 for SOA Tooling, Page 12
Click "Create..." to create a Reply node Output Variable.
Figure 41: Create Reply node Output Variable
Accept the defaults provided and click "Ok".
Click "Ok" to save the modifications to the Reply node's properties.
You should now have a BPEL process that looks like the following:
Figure 42: BPEL Receive/Reply
So, what have you accomplished so far?
- Imported a WSDL.
- Created an empty BPEL process.
- Associated the imported WSDL with a Partner Link.
- Added a Receive node to the BPEL process.
- Associated the Receive node properties to the input WSDL operation.
- Added a Reply node to the BPEL process.
- Associated the Reply node properties to the output WSDL operation.
For now, you will simply stub out a response value to be returned in the Reply Message.
In the interest of brevity for this article, I've left out any interaction with a database or calling another Web Service. Covering all of the features available within the GlassFish ESB is beyond the scope of an article such as this. The intent of this article is to give you enough of an overview to whet your appetite to explore further on your own. There are suggested links provided at the end of this article if you want to explore further.
Map the BPEL Request to the BPEL Reply
Add the "Assign" node to the BPEL process:
- Drag an "Assign" node from the Basic Activities palette.
- Drop it in the available open node that is between the getTroubleTicket Receive node, and the replyTroubleTicket Reply node.
Figure 43: Add Assign node to BPEL Process
Select the new "Assign" node in the BPEL process and click the "Mapper" menu item
Figure 44: BPEL Assign Mapper
Page 12 of 17