Database Reference
In-Depth Information
Log Levels - oracle.bpm ERROR: 1 (SEVERE)
Log Levels - oracle.integration ERROR: 1 (SEVERE)
Log Levels - oracle.sdp ERROR: 1 (SEVERE)
Log Levels - oracle.sdpinternal ERROR: 1 (SEVERE)
Log Levels - oracle.soa ERROR: 1 (SEVERE)
Log Levels - oracle.sysman ERROR: 1 (SEVERE)
Log Levels - oracle.wsm ERROR: 1 (SEVERE)
Optimizing logging through audit store tuning
When enabling production level auditing of composite instances, the application
performance is impacted significantly as compared to when auditing is fully en-
abled. Changing the audit level from
Development
to
Production
, and further
to
Off
, greatly improves the performance of the SOA infrastructure.
In the Oracle Enterprise Manager Fusion Middleware Control navigator, right-
click on
soa-infra
and navigate to
SOA Administration
|
Common Properties
.
Set the
Audit Level
to
Production
unless required otherwise (see
Chapter 2
,
Management of SOA Composite Applications
, for a more detailed explanation
of the audit levels). Uncheck
Capture Composite Instance State
and
Payload
Validation
. The following screenshot shows how instance id
20707
was ex-
ecuted with
Capture Composite Instance State
enabled while instance id
30001
was not.
Although when viewing a list of instances, it is a lot better to know the state of
the instance (versus a question mark), disabling it results in a 24 percent per-
formance improvement! Likewise,
Payload Validation
should only be enabled
in development environments, if needed.
