1.

What Are Two Configuration Settings For Auditing?

Answer»

auditLevel:

  • off - absolutely no logging performed WHATSOEVER; MAY result in a slight performance boost for processing instances.
  • minimal - all events are logged; however, no audit details are logged.
  • production - all events are logged. The audit details for assign activities are not logged; the details for all other nodes are logged.
  • development - all events are logged; all audit details for all activities are logged.

auditDetailThreshold: 

The maximum size (in bytes) an audit TRAIL details string can be before it is stored SEPARATELY from the audit trail. If a details string is larger than the threshold it will not be immediately loaded when the audit trail is initially retrieved; a link will be displayed with the size of the details string. Typically, the details string will contain the contents of a BPEL variable. In cases where the variable is very LARGE performance may be severely impacted by logging it to the audit trail. The default value is 50 kilobytes.

auditLevel:

auditDetailThreshold: 

The maximum size (in bytes) an audit trail details string can be before it is stored separately from the audit trail. If a details string is larger than the threshold it will not be immediately loaded when the audit trail is initially retrieved; a link will be displayed with the size of the details string. Typically, the details string will contain the contents of a BPEL variable. In cases where the variable is very large performance may be severely impacted by logging it to the audit trail. The default value is 50 kilobytes.



Discussion

No Comment Found