Database Reference
In-Depth Information
posite and its underlying components. Neither the service engine nor SOA Infra-
structure audit levels take effect in this case. When the audit level of a composite
is set to
inherit
, depending on what the audit levels of the service engine and
the SOA Infrastructure are, either of them may take effect, which is confusing.
Detailed examples of order of precedence can be found in the first chapter of
the Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite 11g
Release 1 (11.1.1).
Modifying audit levels
We had previously discussed that audit levels can be set at the component,
composite, service engine, and SOA Infrastructure levels. Here, we will describe
how to set each of these.
Modifying component audit levels
Component level auditing can only be manipulated for BPEL and BPMN com-
ponents, but not Mediator components.
For example, developers can modify BPEL component level auditing by insert-
ing the
bpel.config.auditLevel
property within their component referen-
ce in the
composite.xml
file of their project as shown in the following code
snippet:
<component name="HelloWorld">
<implementation.bpel src="HelloWorld.bpel" />
<property name="bpel.config.auditLevel">Off</property>
</component>
Modifying composite audit levels
Audit levels can be changed during runtime at the composite level. To do so,
perform the following steps:
