How to capture a trace generated by Identity Manager and Drivers

(Last modified: 06Feb2006)

This document (10097185) is provided subject to the disclaimer at the end of this document.

goal

fact

Novell Identity Manager 3.0

Nsure Identity Manager 2.0.x

Novell DirXML Drivers

DirXML Remote Loader

fix

Capturing the trace on the engine

The ideal method of capturing a trace is to capture a separate trace for each driver. This is accomplished by specifying the Trace Level and Trace File on each driver that tracing is desired. To set the Trace Level and Trace File on the driver:

In iManager, click on the Overview task (DirXML | DirXML Overview for IDM 2.0.x, Identity Manager | Identity Manager Overview for IDM 3)
Click Search
Click on the circle in the upper-right corner of the driver icon and click on Edit properties
Click on the Misc link. NOTE: This might be selected from a drop-down list depending upon the browser.
In the Trace level, specify a trace level of 3
In the Trace file field, enter a qualified path with a file name that the trace messages can be written to. NOTE: This file must be in a directory that the IDM engine has write rights to. On *nix systems, the directory /tmp is a good choice if you are uncertain about the rights.
With the driver running, verify that the file is created in the specified location. If the file is not created, restart the driver.

Trace Window (to see the image with better clarity, click on the link, choose to save the file and open it with Microsoft Paint or other imaging utility)

Capturing the remote loader trace

When using the Remote Loader, you will only get information from the driver shim if you capture a trace on the remote loader machine as well. If only the engine side trace is captured, key information will be missing and troubleshooting the problem towards a resolution may be impossible.

Windows platform

On Windows, configuring the driver shim to trace information is done using the Identity Manager Remote Loader Console application. This application is usually available from the desktop of the user who installed remote loader, but it can also be accessed at \novell\remoteloader\rlconsole.exe. To configure the tracing using the console application:

Start the remote loader console application
If the instance is running where tracing is desired stop the instance by selecting the instance and clicking Stop
Click Edit
Under the Trace File section, specify a Trace Level of 3
Specify a quallified path and file name for the Trace File field.
Click OK
Restart the instance and verify that the file is created in the specified location

Remote Loader Trace Configuration (to see the image with better clarity, click on the link, choose to save the file and open it with Microsoft Paint or other imaging utility)

*nix platform

On *nix platforms, the configuration file used by rdxml or jremote_loader must be updated to trace information to a file. To add tracing to a remote loader instance on *nix:

Open the config file for rdxml or jremote_loader using your favorite editor
Add the following lines:

-trace 3
-tracefile "<qualified path and file name to location where write rights exist>"
-tracefilemax 0M

Save the file

document

Document Title:	How to capture a trace generated by Identity Manager and Drivers
Document ID:	10097185
Solution ID:	NOVL101602
Creation Date:	01Apr2005
Modified Date:	06Feb2006
Novell Product Class:	DirXML

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.