Message aggregation
A typical messaging requirement is to aggregate multiple related messages for processing within a single BPEL process instance. Messages are aggregated using a common correlation ID, in much the same way as we covered previously.
The other challenge is to determine when we have all the messages that belong to the aggregation. Typically, most use cases fall into two broad patterns:
- Fixed Duration: In this scenario, we don't know how many messages we expect to receive, so we will process all those received within a specified period of time.
- Wait For All: In this scenario, we know how many messages we expect to receive. Once they have been received, we can then process them as an aggregated message. It's usual to combine this with ...
Get Oracle SOA Suite 11g R1 Developer's Guide now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
