Audit overview

Content Engine auditing is accomplished by recording custom or system events that occur on an object. When an audited event occurs, Content Engine creates audit entries in an audit log that is stored in the Event table of the object store database.

For example, a document class can be configured to automatically create audit entries whenever documents of that class are checked in. From the resulting audit entry, also called an event object, you can get the creation date, originating user, result status, source object of the event, and other information.

Applications can programmatically create audit entries that are specific to the application needs. See Auditing Concepts in the Content Engine Java and .NET Developer's Guide for more information about incorporating auditing into custom applications.

Audit concepts
Auditing is the recording of events that occur on source objects. Most events on Content Engine classes can be audited. If Content Engine is configured for auditing, Content Engine creates audit entries that are instances of one of the subclasses of the Event class.
Guidelines for configuring auditing
Before you configure auditing, consider these guidelines.
Auditable objects and events
Content Engine provides configurable audit logging for all of the subscribable Content Engine classes and their subclasses.