PaaS Partner Community

  • November 21, 2016

Correlations in Oracle BPM 12c by Antonis Antoniou

Jürgen Kress
PaaS Partner Adoption


Correlations in Oracle Business Process Management (BPM) is a special mechanism used to associate a message with a conversation between different partners in a business process.

There are two types of correlations:

  • Automatic: This is the default and out-of-the-box correlation used between two business partners which makes use of a special token called "Conversation Id" to uniquely associate a message with a conversation via Web Service Addressing (WS-Addressing) to correlate a callback message using the "Conversation Id".
  • Message Based: This type of correlation enables the definition and use of "business-friendly" information carried as part of the message payload to be used to uniquely identify and associate a message with a conversation (for example, OrderId, CustomerId, etc.). This type of correlation enables the definition of multiple attributes referred to as "Correlation Properties" into various correlation sets know as "Correlation Keys".

So let's see how you to use the two correlation types in a demo scenario. The simulated process will invoke an asynchronous process first by using the default correlations and then by using message-based correlations.
Create the basic BPM application and BPM project (I named it OracleBPM12cCorrelationsDemoApp and OracleBPM12cCorrelationsDemo respectively) and choose "Composite with BPMN Process" in step 3 of the "Create BPM Application" and click “Finish”. Read the complete article here.

SOA & BPM Partner Community

For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn image[7][2][2][2] Facebook clip_image002[8][4][2][2][2] Wiki

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.