rss
SOATUBE
Oracle
Custom Search SOABYTE here

Friday, June 25, 2010

Dehydration point





















Dehydration happens based on the process types:

Transient process — Oracle BPEL Server dehydrates the process instance only once at the end of the process.
Durable process — Oracle BPEL Server dehydrates the process instance inflight at all midprocess breakpoint and idempotent activities, plus the end of the process.
Properties to be used:

CompletionPersistPolicy- If and when to save meta-data and audit trail. Values: on, deferred, faulted, off

 completionPersistLevel- Amount of meta data to save. Values: all, instanceHeader

inMemoryOptimization- Mandatory to be set along with the above two properties. Values: true, false
Incase of transient processes, these properties can be set in bpel.xml to dehydrate either all processes with instanceHeader or all faulted processes with the full audit details.
Eg:
<configurations>
   <property name="inMemoryOptimization">true</property>
   <property name="completionPersistPolicy">faulted</property>
   <property name="completionPersistLevel">all</property>
 </configurations>

0 comments:

Post a Comment

 
Blogger Profile