Cedric Flink asked 3 years ago
Title : Audit Trail configurations in Oracle SOA Suite 11g.

Question :

Audit Trail configurations in Oracle SOA Suite 11g.

1 Answers
ParwezParwez Staff answered 3 years ago

Audit trail is configured via following properties.

  1. auditStorePolicy: This flag is used to choose the audit store strategy.  There are following ways to achieve desired configuration.

    syncSingleWrite – would store audit data synchronously when it saves the cube instance, this is done as part of the cube instance transaction.

    This is the default value. And the behavior is the same as in the 10.1.3.x version.

    syncMultipleWrite – would store audit data synchronously using a separate local transaction.

    By “synchronously” it means the BPEL service engine is saving the audit trail in the same thread as the main transaction. However, it is doing it in a “separate local transaction”.

    async – would store the audit data asynchronously using an in-memory queue and pool of audit threads.

    This is almost the same as “syncMultipleWrite”, except that it is done not just in a separate transaction but also in a separate thread.

    The pro is the audit trail latency is NOT directly included in the latency of main transaction (but because they still share the computing resources and database, the latency is still indirectly related).

    The con is that because audit trails are being saved asynchronously, the audit trail may be out of sync from the main transaction (as the name ‘async’ implies)

  2. AuditFlushByteThreshold and AuditFlushEventThreshold
    When auditStorePolicy=syncMultipleWrite or auditStorePolicy=async, you use these two flags to control how often the engine should flush the audit events. These two properties do NOT apply to auditStorePolicy=syncSingleWrite.

    auditFlushByteThreshold means after adding an event to the current batch, the engine would check if current batch byte size is greater than this value or not. if yes, then it would flush the current batch. The default value is 2048000 (byte), i.e. 2MB.

    Similarly, auditFlushEventThreshold means this limit is reached; the engine would trigger the store call. The default value is 300 (event)

    Both values need to be tuned based on the application and requirements.


    This is the maximum size (in bytes) an audit trail details string can be before it is stored separately from the audit trail.

Now to configure any or all of these, go to em console, http://hostname:port/em, and then follow the path

 EM -> SOA ->SOA-INFR – > SOA Administration -> BPEL Properties -> More BPEL Configuration Properties

Cubastion is among a very small number of specialized Siebel CRM Oracle Gold Partners in SME.