Tuning Audit & Logging levels for Production Environments

      Oracle SOA: Tuning Audit & Logging Levels for Production Environment.      

      Unless there is a reason specific to your environment or a business requirement, keep audit and logging levels to minimal in your production environments. Minimal logging levels can improve performance of your BPEL processes, Mediator components and Worklist app experience. Setting of audit level parameters can be done at SOA global managed server level or individual managed server components level.

The following snapshots will serve as reference to where auditing properties can be set:

a.    In Enterprise Manager Console, Traverse to “Common Properties” section as shown below.

b.    In production, I would advice setting the “Audit Level” parameter to “Production”.

c.     Disabling “Capture Composite Instance State” would improve the performance of your composites. The catch though is, when a support or admin person logs into em console and looks transactions for a composite, they will not be able to see the state of the composite instance like “Completed” right in there. You will have to open each composite instance for details. So in our environment we haven’t disabled composite instance state capture as shown above.

d.    Set auditing at BPEL engine level to “inherited” as shown in screenshots below.

e.    Set auditing at Mediator engine level to “inherited” as shown below. Also , we have observed that disabling “Metrics Level” improves mediator components performance. Please refer to snapshots below.

The following snapshots will serve as reference to where logging properties can be set:

a.    Traverse to log configuration in em console.

b.  In production, I would advice setting logging level for various logger’s to “WARNING:1 (WARNING)”. If you are seeing any issues with a specific component or have to trace, then you can always, set a particular logger to “Notification” or “Trace”.