How to Force a Synchronous BPEL Process to Dehydrate After a Reply Activity? (Doc ID 981513.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle(R) BPEL Process Manager - Version: 10.1.3.1 to 10.1.3.4 - Release: AS10gR3 to AS10gR3
Information in this document applies to any platform.

Goal

In a Synchronous BPEL process, the Reply activity does not dehydrate by default.

There is a statement in the documentation, chapter "6.17 Describing How Adapters Ensure no Message Loss" in Oracle´┐Ż Application Server Adapter Concepts Guide 10g Release 3 (10.1.3.1.0) B31005-01:

"The BPEL engine is constructed to always ensure delivery.
Dehydration points are established before each receive, pick, wait and after each reply and invoke.
By default dehydration after an invoke is deferred but you have control of that through tuning process parameters(see the idempotent setting option in the BPEL Tuning Guide)."


This statement should be updated so that it becomes clear that the default dehydration after an Reply activity is also deferred and that the "idempotentReply" property should be used to control the dehydration for a Reply activity.


Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms