How to Route Callback Messages to the Correct Endpoint when Multiple Receive and Pick Activities Use the Same Partner Link

Set this property to the client's replyToAddress on the invoke activity (for the callback) following the midprocess receive activity. This means that even if the client sends WS-Addressing replyTo information for a midprocess receive activity, it is not set on the partner link unless you use an assign activity to set it dynamically.

For example, assume your BPEL process is as shown below:

Caller                               Callee
-----------------------------------------------------------
<receive>                            <receive> Initiate CS1
<invoke>initiate CS1 -------->       <receive> Use CS1
                                     <wait>
<receive>use CS1    <--------        <invoke>
<invoke>

To route callback messages to the correct endpoint when multiple receive and pick activities use the same partner link:

Obtain the client's replyToAddress value from the midprocess receive activity.

<receive name="receiveMsgFromAccessor" partnerLink="midprocess_client"
       portType="client:mySingletonBPEL" operation="process"
       variable="ReceiveMidProcess" createInstance="no">
<bpelx:fromProperties>
   <bpelx:fromProperty name="replyToAddress" variable="var_replyToAddress"/>
</bpelx:fromProperties>
   <correlations>
       <correlation set="<YourCorrset>" initiate="no"/>
   </correlations>
</receive>

On the invoke activity (for the callback), click the Properties tab.
Click the Add icon to select the property and its content (either a variable or an XPath expression).

Note:

In BPEL 1.1 processes, the properties are automatically displayed in the Properties column. Select the property in the Name column and double-click the Value and Type columns to enter appropriate values.
In the Name column, scroll down and select the replyToAddress property. Do not select wsa.replyToAddress or bpel.replyToAddress.
In the Value column, specify the variable name as the value (for this example, var_replyToAddress from Step 1 is entered), and click OK.

The Edit Invoke dialog appears as shown in Figure 8-1.

Figure 8-1 Properties Tab of Invoke Activity

Description of "Figure 8-1 Properties Tab of Invoke Activity"
Click Apply, then OK.

In Oracle BPEL Designer, click Source.

The invoke activity in the BPEL process file looks as follows:

<invoke name="callbackAccessor" partnerLink="midprocess_client"
                portType="client:mySingletonBPELCallback"
                operation="processResponse"
inputVariable="CallbackAccessorVar"
                bpelx:invokeAsDetail="no">
            <bpelx:inputProperty name="replyToAddress"
variable="var_replyToAddtess"/>