Table of Contents

Search

  1. Preface
  2. Welcome to Informatica Process Developer
  3. Using Guide Developer for the First Time
  4. Getting Started with Informatica Process Developer
  5. About Interfaces Service References and Local WSDL
  6. Planning Your BPEL Process
  7. Participants
  8. Implementing a BPMN Task or Event in BPEL
  9. Implementing a BPMN Gateway or Control Flow
  10. Using Variables
  11. Attachments
  12. Using Links
  13. Data Manipulation
  14. Compensation
  15. Correlation
  16. What is Correlation
  17. What is a Correlation Set
  18. Creating Message Properties and Property Aliases
  19. Adding a Correlation Set
  20. Deleting a Correlation Set
  21. Adding Correlations to an Activity
  22. Rules for Declaring and Using Correlation Sets
  23. Correlation Sets and Engine-Managed Correlation
  24. Event Handling
  25. Fault Handling
  26. Simulating and Debugging
  27. Deploying Your Processes
  28. BPEL Unit Testing
  29. Creating POJO and XQuery Custom Functions
  30. Custom Service Interactions
  31. Process Exception Management
  32. Creating Reports for Process Server and Central
  33. Business Event Processing
  34. Process Central Forms and Configuration
  35. Building a Process with a System Service
  36. Human Tasks
  37. BPEL Faults and Reports

2. Designer

2. Designer

Engine-Managed Correlation

Engine-Managed Correlation

Select this policy assertion as described in Adding Policy Assertions.
There are two ways that Process Server can correlate messages that are received by a BPEL process: correlation sets and engine-managed correlation policy assertions. A correlation set uses message properties defined within a WSDL and BPEL process. Engine-managed correlation relies on WS-Addressing references in the SOAP header of a message to correlate a received message with the correct process instance.
If you use engine-manage correlation, you need only specify a policy assertion on a My Role partner link. Select a My Role partner link that is associated with a Partner Role in the same partner link. The engine-managed correlation policy assertion directs the Process Server to use WS-Addressing to transmit replyTo endpoint references during transmissions to the partner.
Policy Assertion Example
<myRole allowedRoles="" binding="RPC" service="ManagedCorrelationServiceA"> <wsa:Metadata> <wsp:Policy xmlns:abp="http://schemas. active-endpoints.com/ws/2005/12/policy" xmlns:wsp="http://schemas.xmlsoap.org /ws/2004/09/policy"> <abp:engineManagedCorrelationPolicy/> </wsp:Policy> </wsa:Metadata> </myRole>
How Partner Services Handle Engine Managed Correlation Messages
Often a partner service implemented the WSA SOAP Binding details to automatically handle engine managed correlation messages. The service extracts information from the SOAP header and uses it to reply back to Process Server.
The message Process Server sends to the service is constructed similarly to the following example. Note that the SOAP header contains a
<wsa:ReplyTo>
element including a
<wsa:ReferenceProperties>
element containing the conversation Id for the correlation:
Outbound Message from Process Server
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org /soap/envelope/" xmlns:xsd="http://www.w3.org/2001 /XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Header> ...
<wsa:ReplyTo xmlns:abx="http://www.activebpel.org/bpel/extension" xmlns:wsa="http://schemas.xmlsoap.org/ws/2003/03/addressing"> <wsa:Address>http://localhost:8080/active-bpel/services /ManagedCorrelationServiceA</wsa:Address> <wsa:ReferenceProperties> <abx:conversationId>1:/process/partnerLinks /partnerLink[@name='requestPLT'] </abx:conversationId> </wsa:ReferenceProperties> </wsa:ReplyTo>
... </soapenv:Header> <soapenv:Body> ... </soapenv:Body> </soapenv:Envelope>
When a service receives a message, it should extract the SOAP header
<wsa:ReferenceProperties
> and reply with a similarly formatted SOAP header. If the service you are calling is not replying as expected, use the following example to understand the expectations of Process Server for receiving an engine managed correlation message.
Inbound Message Process Server Expects
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org /soap/envelope/" xmlns:xsd="http://www.w3.org/2001 /XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Header> ... <abx:conversationID
xmlns:abx=
"http://www.activebpel.org/bpel/extension"
>
1:/process/partnerLinks
/partnerLink[@name='requestPLT'
]
</abx:conversationId>
... </soapenv:Header> <soapenv:Body> ... </soapenv:Body> </soapenv:Envelope>
For details on correlation sets, see Correlation.


Updated March 30, 2020