Events

The Content Engine API provides event interfaces through which audit- and subscription-related functionality is exposed. Auditing logs events for specified Content Engine classes. In response to triggered events, subscriptions run actions that you implement as Java™ event handlers. When a subscribed event occurs, the Content Engine API creates an event object that is passed to your implemented action. When an audited event occurs, the Content Engine API creates an event object that is stored in the object store database to form an audit record.

All events are inherited from the Event class. An event-based object is one of the following subobject types:

• AuditConfigurationEvent, which occurs when auditing is enabled or disabled in an object store configuration. This event is auditable but not subscribable.
• ObjectChangeEvent-derived objects, which occur when a Content Engine object changes. These events are subscribable and auditable.
• RetrievalEvent-derived objects, which occur when a Content Engine object or its content is retrieved or queried. Events of this type are auditable, and the GetContentEvent subclass is subscribable as well.

Event objects provide the context of an event within the Content Engine, and you can garner this information by retrieving the properties of an audited event. For example, you can get an event's type (as represented in the class of the event object), creation date, originating user, and result status from the base Event class (see Event Properties). From an Event subclass, you can get the source object of an event, the class of the source object, and other subclass-specific properties.