Multipart Message Support in Oracle BPEL

BPEL2.0 in Oracle SOA 11g supports multipart WSDL messages. The toParts element in invoke
and reply activities provides an alternative to explicitly creating multipart WSDL messages from
the contents of BPEL variables.
<toParts>
<toPart part="payload" fromVariable="request"/>
</toParts>
The fromParts element in receive activities, invoke activities, the onEvent branch of scope
activities, and the onMessage branch of pick activities is similar to the toParts element. The
fromParts element retrieves data from an incoming multipart WSDL message and places the
data into individual variables
<fromParts>
<fromPart part="payload" toVariable="request"/>
</fromParts>
This document will explain how to use the multi part messages in BPEL 2.0
Create a sample BPEL project that will accept the multi part message as input.
I am using the below schema elements to define the part elements in WSDL.

Modify the project WSDL to accept the multi part message as input.

Verify the inputvariable; this will have two parts defined now.

In receive activity we can assign the input data including all the parts to a variable or individual
parts can be retrieved and assigned to separate variable when retrieving the individual parts the
parts value can be assigned to a variable created based on element not to message type based
variable.

Deploy and test the BPEL process, the receive activity will get both the parts as input.

To invoke the service with multipart message either we can provide the input as single variable
create based on the partnlerlink type or assign the data from individual elements based variable
to parts using toParts.

10