Edirectory Objects That Store Identity Manager Event Data; Using Status Documents To Generate Events - Novell IDENTITY MANAGER 3.6.1 Reporting Manual

7.2.2 Using Status Documents to Generate Events

Status documents generated through style sheets using the
Sentinel with an event ID that corresponds to the status document level attribute. The level attributes
and corresponding event IDs are defined in the following table:
Status Documents
Table 7-2
Status Level Status Event ID
Success EV_LOG_STATUS_SUCCESS (1)
Retry EV_LOG_STATUS_RETRY (2)
Warning EV_LOG_STATUS_WARNING (3)
Error EV_LOG_STATUS_ERROR (4)
Fatal EV_LOG_STATUS_FATAL (5)
User Defined EV_LOG_STATUS_OTHER (6)
The following example generates an event 0x004 and value1=7777, with a level of
EV_LOG_STATUS_ERROR:
<xsl:message>
<status level="error" text1="This would be text1" value="7777">This data
would be in the blob and in text 2, since no value is specified for text2 in
the attributes.</status>
</xsl:message>
The following example generates an event 0x004 and value1=7778, with a level of
EV_LOG_STATUS_ERROR:
<xsl:message>
<status level="error" text1="This would be text1" text2="This would be
text2" value1="7778">This data would be in the blob only for this case, since
a value for text2 is specified in the attributes.</status>
</xsl:message>
7.3 eDirectory Objects that Store Identity
Manager Event Data
The Identity Manager events you want to log are stored in the DirXML-LogEvent attribute on the
Driver Set object or Driver object. The attribute is a multi-value integer with each value identifying
an event ID to be logged.
You do not need to modify these attributes directly, because these objects are automatically
configured based on your selections in iManager.
Before logging an event, the engine checks the current event type against the contents of the
DirXML-LogEvent attribute to determine whether the event should be logged.
element are sent to
<xsl:message>
Managing Identity Manager Events 35