Database Reference
In-Depth Information
BPEL correlation
Correlation is a process that matches incoming messages to a particular BPEL pro-
cess instance. Synchronous BPEL does not require correlation. Correlation is only re-
quired for asynchronous BPEL processes.
Oracle BPEL Process Manager automatically establishes correlation using WS-Ad-
dressing. However, manual content-based correlation is required if the asynchronous
service doesn't support WS-Addressing or the BPEL message is coming from an ex-
ternal system.
Oracle BPEL Processor Manager has the following two methods for correlating asyn-
chronous callback messages to the calling instance.
• WS-Addressing
• Correlation sets
One needs to write a manual correlation for the following scenarios:
• Calling service does not support WS-Addressing.
• When the asynchronous call has multiple layers. For example, Service A
calls B, B calls C, and C Calls D. Response comes from D to A (instead
of D to C to B to A). Another option in this scenario is to manipulate the
replyTo
header without implementing custom correlation.
Creating a Correlation set
A
correlation set
is a set of properties shared by all messages in the correlated
group. These properties must be defined in a WSDL file imported into the BPEL pro-
cess.
The first step is to create a correlation set. In order to create a correlation set, first
click on the
Correlation
icon (up and down green arrow icon) on the JDeveloper, as
shown in the following screenshot. Second, click on the green plus sign on the
Cor-
relation Sets
window, as shown in the following screenshot that will open the
Create
Correlation Set
window. Third, enter the
Name
and click on
OK
. Another option to
create a correlation set is to create it from Invoke and Receive activities.
