Viewing driver processes is necessary to analyze unexpected behavior. To view the driver processing events, use DSTrace. You should only use it during testing and troubleshooting the driver. Running DSTrace while the drivers are in production increases the utilization on the Identity Manager server and can cause events to process very slowly.
In order to see the driver processes in DSTrace, values are added to the driver set and the driver objects. You can do this in Designer and iManager.
You can add trace levels to the driver set object or to each driver object.
In an open project in Designer, select the driver set object in the
view.Right-click and select
, then click .Set the parameters for tracing, then click
.If you set the trace level on the driver set object, all drivers appear in the DSTrace log. For more information, see Capturing Driver Processes to a File.
In an open project in Designer, select the driver object in the
view.Right-click and select
, then click .Set the parameters for tracing, then click
.If you set the parameters only on the driver object, only information for that driver appears in the DSTrace log. For more information, see Capturing Driver Processes to a File.
You can add trace levels to the driver set object or to each driver object.
In iManager, select
.Browse to the driver set object, then click
.Click the driver set name.
Select the
tab for the driver set object.Set the parameters for tracing, then click
.See Driver trace level for the parameters.
In i Manager, select
.Browse to the driver set object where the driver object resides, then click
.Click the upper right corner of the driver object, then click
.Select the
tab for the driver object.Set the parameters for tracing, then click
.See Trace level for the parameters.
The option
does not exist in iManager.You can save driver processes to a file by using the parameter on the driver object or by using DSTrace. The parameter on the driver object is the
parameter, under the tab.The driver processes that are captured through DSTrace are the processes that occur on the Identity Manager engine. If you use the Remote Loader, you need to capture a trace on the Remote Loader at the same time as you are capturing the trace on the Identity Manager engine.
The following methods helps you capture and save Identity Manager processes through DSTrace on different platforms.
Use dstrace.nlm to display trace messages on the system console or trace messages to a file ( sys:\system\dstrace.log). Use dstrace.nlm to display the trace messages to a screen labeled DSTrace Console.
Enter dstrace.nlm at the server console to load dstrace.nlm into memory.
Enter dstrace screen on at the server console to allow trace messages to appear on the DSTrace Console screen.
Enter dstrace file on at the server console to capture trace messages sent to the DSTrace Console to the dstrace.log file.
(Optional) Enter dstrace -all at the server console to make it easier to read the trace log.
Enter dstrace +dxml dstrace +dvrs at the server console to display Identity Manager events.
Enter dstrace +tags dstrace +time at the server console to display message tags and time stamps.
Toggle to the DSTrace Console screen and watch for the event to pass.
Toggle back to the server console.
Enter dstrace file off at the server console.
This stops capturing trace messages to the log file. It also stops logging information into the file.
Open the dstrace.log in a text editor and search for the event or the object you modified.
Open the dstrace.dlm, then click to display the NDS Server Trace utility window.
> >Click
> , then click to clear all of the default flags.Select
and .Click OK.
Click
.Specify the filename and location where you want the DSTrace information saved, then click
.Wait for the event to occur.
Click
.This stops the information from being written to the log file.
Open the file in a text editor and search for the event or the object you modified.
Enter ndstrace to start the ndstrace utility.
Enter set ndstrace=nodebug to turn off all trace flags currently set.
Enter set ndstrace on to display trace messages to the console.
Enter set ndstrace file on to capture trace messages to the ndstrace.log file in the directory where eDirectory is installed. By default it is /var/nds.
Enter set ndstrace=+dxml to display the Identity Manager events.
Enter set ndstrace=+dvrs to display the Identity Manager driver events.
Wait for the event to occur.
Enter set ndstrace file off to stop logging information to the file.
Enter exit to quite the ndstrace utility.
Open the file in a text editor. Search for the event or the object that was modified.
iMonitor allows you to get DSTrace information from a Web browser. It does not matter where Identity Manager is running. The following files run iMonitor:
ndsimon.nlm runs on NetWare®.
ndsimon.dlm runs on Windows.
ndsimonitor runs on UNIX.
Access iMonitor from http:// server_ip:8008/nds.
Port 8008 is the default.
Specify a username and password with administrative rights, then click
.Select
on the left side.Click
.Select
and .Click
.Select
on the left side.Click the document with the
of to see a live trace.Change the
if you want to see information more often.Select
on the left side, then click to turn the tracing off.Select
to view the trace history.The files are distinguished by their time stamp.
If you need a copy of the HTML file, the default location is:
NetWare: sys:\system\ndsimon\dstrace*.htm
Windows: Drive_letter:\novell\nds\ndsimon\dstrace\*.htm
UNIX: /var/nds/dstrace/*.htm
You can capture the events that occur on the machine by running the Remote Loader service.
Launch the Remote Loader Console by clicking the icon.
Select the driver instance, then click
.Set the
to 3 or above.Specify a location and file for the trace file.
Specify the amount of disk space that the file is allowed.
Click
, twice to save the changes.You can also enable tracing from the command line by using the switches in Table 10-1. For more information, see
Configuring the Remote Loader
in the
Novell Identity Manager 3.5.1 Administration Guide
.
Table 10-1 Command Line Tracing Switches