Database Reference
In-Depth Information
to execute in the runtime memory of the engine, and others. Practically there are
several combinations through which the amount of data being saved to the data-
base can be controlled. It is vital to know about some typical configurations that
can be set either at the individual process level or at a domain wide level and
what their impact is on the Dehydration Store.
These configuration properties can be applied at the domain level, enabling you
to set a global configuration for all composites deployed to the domain. You can
also override these configuration properties at the individual component level.
If a setting at the domain level conflicts with the same setting at the compon-
ent level, the component level setting takes priority. The following table shows
the various properties that control data persistence in the Dehydration Store and
their respective descriptions.
Configuration
Level
Property
Description
completionPersistLevel
Domain and
Component
(BPEL only)
This property controls the type
and amount of instance data
being saved after its comple-
tion. When process instances
complete, Oracle SOA Suite
11g
engine by default saves the
final state (for example, the
variable values) of the instance.
If these values are not required
to be saved after completion,
this property can be set to save
only instance metadata (com-
pletion state, start and end
dates, and so on). This prop-
