Custom Audit Event Implementation

Audit data provides a historical record of operations that occur in a idmgr environment. You can enable auditing for some or all the idmgr events generated by admin tasks.
Audit data provides a historical record of operations that occur in a
environment. You can enable auditing for some or all the
events generated by admin tasks.
You can implement application-specific auditing in cases where you have custom code that performs a non-standard operation, for example, an object that updates a user directory directly, rather than through
. You could create a custom audit event to report unexpected results back to
.
To create an audit event to support your custom application, write a class that implements AuditEvent and that extends GenericAuditEvent. Typically, an extension of this class updates the description associated with the custom event, which is passed to
when the event occurs. You can override that class’s extractAuditData() method to process the audit data passed in to it (an EnhancedAuditData object) as appropriate for the situation.
The audit event name should contain the "Audit" keyword.
The auditable attributes of an event are contained in EventProfile. This class also lets you set and retrieve the stage of an event cycle in which event attributes are recorded for auditing.
You can find a sample BLTH application with an associated audit event in the following directory:
admin_tools
\samples\BLTH\Group