3.2 Logging to a Novell Audit or Sentinel Server

To log to a Novell Audit or Sentinel server:

  1. Add the Identity Manager application schema to the Novell Audit server as a log application

    This step applies to Novell Audit only. For more information, see Section 3.2.1, Adding the Identity Manager Application Schema to your Novell Audit Server as a Log Application

  2. Configure the Novell Audit platform agent on your application server

    The Platform Agent is required on any client that reports events to Novell Audit or Sentinel. You configure the platform agent through the logevent configuration file. This file provides the configuration information that the platform agent needs to communicate with the Novell Audit server. The location for this file on the application server needs to be:

    • Linux: /etc/logevent.conf

    • Windows: /<WindowsDir>/logevent.cfg (Usually c:\windows)

    On Linux installs, you need to move the logevent.conf from the root folder where the Roles Based Provisioning Module was installed (for example, /home/userapp/idm) to /etc. This file needs to be readable by the same user that the RBPM will be running on as the Linux box.

    Specify the following four properties:

    Loghost: The IP address or DNS name of your Novell Audit or Sentinel server. For example:


    LogJavaClassPath: The location of the lcache jar file NauditPA.jar. For example:


    LogCacheDir: Specifies where lcache stores cache files. For example:


    LogCachePort: Specifies on which port lcache listens for connections. The default is 288, but in a Linux server, set the port number greater than 1000. For example:


    BigData Specifies the maximum number of bytes that the client will allow. Larger amounts of logging data will be truncated. The default value is 3072 bytes, but you should change this to at least 8192 bytes to handle a typical form that has approximately 15 fields on a half page.


    IMPORTANT:If your data is very large, you may want to increase this value. If you are logging events that include digital signatures, it is critical that the value of LogMaxBigData be large enough to handle the data being logged.

    Specify any other settings needed for your environment.

    NOTE:You must restart the Platform Agent any time you change the configuration.

    For more information about the structure of the logevent configuration file, see the section on configuring platform agents in the section on the logging system in the Novell Audit Administration Guide.

  3. Enable Novell Audit or Sentinel logging.

    This step applies to both Novell Audit and Sentinel. For more information, see Section 3.2.2, Enabling Audit or Sentinel Logging.

NOTE:You need to create the folder structure /var/opt/novell/naudit/ so that the file nproduct.log can be created when enabling "Audit". Otherwise an error will be displayed that says: Error writing to NAudit Log file: /var/opt/novell/naudit/nproduct.log (No such file or directory). The folders and its contents need be readable and writable to the same user that is running the Roles Based Provisioning Module.

3.2.1 Adding the Identity Manager Application Schema to your Novell Audit Server as a Log Application

If you are using Novell Audit (not Sentinel), you need to add the schema to your Novell Audit Server as a log application. This section applies to Novell Audit only.

To configure Audit to use the Identity Manager User Application as a log application:

  1. Locate the following file:


    This file is located in the Identity Manager User Application installation directory after the install, for example /opt/novell/idm.

  2. Use a Web browser to access an iManager with the Novell Audit plug-in installed, and log in as an administrator.

  3. Go to Roles and Tasks > Auditing and Logging and select Logging Server Options.

  4. Browse to the Logging Services container in your tree and select the appropriate Audit Secure Logging Server. Then click OK.

  5. Go to the Log Applications tab, select the appropriate Container Name, and click the New Log Application link.

  6. When the New Log Application dialog box displays, specify the following:

    For this setting

    Do this

    Log Application Name

    Type any name that is meaningful for your environment

    Import LSC File

    Use the Browse button to select the dirxml.lsc file

    Click OK. The Log Applications tab displays the added application name.

  7. Click OK to complete your Novell Audit server configuration.

  8. Make sure the status on the Log Application is set to ON. (The circle under the status should be green. If it is red, click it to switch it to ON.)

  9. Restart the Novell Audit server to activate the new log application settings.

3.2.2 Enabling Audit or Sentinel Logging

To enable Novell Audit or Sentinel logging in your Identity Manager User Application:

  1. Log in to the User Application as the User Application Administrator.

  2. Select the Administration tab.

  3. Select the Logging link.

  4. Select the Also send logging messages to Novell Audit check box (near the bottom of the page).

  5. To save the changes for any subsequent application server restarts, make sure Persist the logging changes is selected.

  6. Click Submit.

NOTE:To enable logging for Role events, the Role Service driver Generate audit events property must be selected. For more information on this property, see Section 2.9.1, Role Service Driver Configuration.

3.2.3 Log Reports

If you log events to the Novell Audit database channel, you can run reports on the data. There are several ways to generate reports against data logged to a Novell Audit database:

  • Use the Novell Audit Report application to run your own reports or to run the predefined reports described in Predefined Log Reports for Novell Audit.

  • Write queries against the logged data by using iManager to select Auditing and Logging > Queries (Novell Audit only).

  • Write your own SQL queries against the logged data.

  • Produce Identity Manager reports in Sentinel (see Sentinel Reports).

The default Novell Audit table is called NAUDITLOG.

Predefined Log Reports for Novell Audit

The following predefined log reports are created in Crystal Reports (.rpt) format for filtering data logged to the Novell Audit database:

Report Name


Administrative Action

Shows all administrative actions initiated from the Identity Manager User Application portal. This report includes the administrator who initiated the action.

It excludes any administrative changes made using iManager or the Designer for Identity Manager.

Historical Approval Flow

Shows all approval flow activities for a specified time frame.

Resource Provisioning

Shows all provisioning activities, sorted by resource.

User Audit Trail

Shows all activity relating to a user. Activities include both provisioning and self-service activities.

Specific User Provisioning

Shows all provisioning activities for a specific user.

User Provisioning

Shows all provisioning activities, sorted by user.

The following graphic shows an example of the Specific User Audit Trail report:

Figure 3-1 Sample Audit Trail Report


The report files are in the following locations:





You can use these reports as templates for creating custom reports in the Crystal Reports Designer or you can run the reports using Audit Report (lreport.exe), a Windows program supplied with Novell Audit. The predefined reports query data from the default Novell Audit log database named naudit and a database table named nauditlog. If your Novell Audit log database has a different name, use the Set Datasource Location menu item in Crystal Reports Designer to replace the naudit database name with the one in your environment.

For more information, see the section on working with reports in the Novell Audit documentation.

Sentinel Reports

If you have configured the platform agent to send events to Sentinel, you can produce the following reports about Identity Manager events in Sentinel:

  • IDM_Administrative_Action_Report.rpt

  • IDM_Historical_Approval_Flow_Report.rpt

  • IDM_Password-Management.rpt

  • IDM_Provisioning_Report_by_Top_10_DHNs.rpt

  • IDM_Provisioning_Report_by_Top_10_DIPs.rpt

  • IDM_Resource_Provisioning_Report.rpt

  • IDM_Specific_User_Audit_Trail_Report.rpt

  • IDM_Specific_User_Provisioning_Report.rpt

  • IDM_Sync-vs-Reset.rpt

  • IDM_User_Provisioning_Report.rpt

  • IDM_Workflow_Stats_by_Top_10_DHNs.rpt

  • IDM_Workflow_Stats_by_Top_10_DIPs.rpt

For more information about Sentinel reports, see the Sentinel User’s Guide. The following is a sample Sentinel report on Password Management:

Figure 3-2 Sample Sentinel Report