Problem with completionPersistPolicy property in deployment descriptor

Question

Hello Everyone,
i am working on SOA 11g.
I read about setting various properties inside deployments descriptor for a BPEL process from the below link
http://download.oracle.com/docs/cd/E15523_01/integration.1111/e10224/bp_app_deploydesc.htm
It states that if we set the value for completionPersistPolicy as "off" then no instance of this a process is saved but i can still see an instance created for this process in the EM.
I thought it might be removed after the process gets completed but even after process reached completed state it was not removed and its entry was still visible in the EM.
Basically i was just trying to figure out is ther a way to have control on dehydration in SOA 11g and after searching the net all that i understood was that one can control it by adding the below entries in composite.xml:
*<property name="bpel.config.inMemoryOptimization">false</property>*
*<property name="bpel.config.completionPersistPolicy">faulted</property>*
I just wanted to know where am i goin wrong and is their other ways to control dehydration in SOA 11g that i am not introduced to.
Any suggestion would be of great help!!!!
Regards
Ajay

Answer 1

This property configures how the instance data is saved. It can only be set at the BPEL component level. The completionPersistPolicy property can only be used when inMemoryOptimization is set to be True (transient processes).
Also, inMemoryOptimization property can only be set to True for transient processes or processes that do not contain any dehydration points such as receive, wait, onMessage and onAlarm activities.
Thanks,
Ashu