To view Identity Manage processing events, use DSTRACE. You only use this during testing and troubleshooting Identity Manager. Running DSTRACE while the drivers are in production increases the utilization on the Identity Manager server and can cause events to process very slowly.
To see Identity Manager processes in DSTRACE, you add values to the driver set and the drivers. You can do this in Designer and iManager.
You can add trace levels to the driver set or to each driver.
In an open project in Designer, select the driver set in the
view.Right-click and select
, then click .Set the parameters for tracing, then click Table 2-1 for more information about the driver set trace parameters.
. SeeIf you set the trace level on the driver set, all drivers appear in the DSTRACE logs.
Table 2-1 Driver Set Trace Parameters
In an open project in Designer, select the driver in the Outline view.
Right-click and select
, then click .Set the parameters for tracing, then click Table 2-2 for more information about these parameters.
. SeeIf you set the parameters on the driver only, only information for that driver appears in the DSTRACE log.
Table 2-2 Driver Trace Parameters
You can add trace levels to the driver set or to each driver.
In iManager select
.Browse to the driver set, then click
.Click on the driver set name.
Select the
tab for the driver set.Set the parameters for tracing, then click Table 2-1 for more information about these parameters.
. SeeIn iManager select
.Browse to the driver set where the driver resides, then click
.Click the upper right corner of the driver, then click
.Select the
tab for the driver.Set the parameters for tracing, then click Table 2-2 for more information.
. SeeNOTE:The option
does not exist in iManager.Identity Manager processes are saved to a file by using a parameter on the driver or through DSTRACE. The parameter on the driver is the Trace file parameter.
The driver processed 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 OS platforms.
Use DSTRACE.NLM to display trace messages on the system console or trace messages to a file (SYS:\SYSTEM\DSTRACE.LOG). DSTRACE.NLM displays the trace messages to a screen labeled DSTRACE Console.
Type DSTRACE.NLM at the server console.
This loads DSTRACE.NLM into memory.
Type DSTRACE SCREEN ON at the server console.
Allows trace messages to appear on the DSTRACE Console screen.
Type DSTRACE FILE ON at the server console.
Captures trace messages sent to the DSTRACE Console to the DSTRACE.LOG.
Type DSTRACE -ALL at the server console.
Turns off all trace flags.
Type DSTRACE +DXML DSTRACE +DVRS at the server console.
Displays the Identity Manager events.
Type DSTRACE +TAGS DSTRACE +TIME at the server console
Displays the message tags and timestamps.
Toggle to the DSTRACE Console screen and watch for the event to pass.
Toggle back to the server console.
Type DSTRACE FILE OFF at the server console.
Stops capture trace messages to the log file. It stops logging the information into the file as well.
Open the DSTRACE.LOG in a text editor and search for the event or the object you modified.
Open the Control Panel > NDS Services > dstrace.dlm, then click
.A window opens named NDS Server Trace Utility.
Select
> , then click .This clears all of the default flags.
Select
and .Click OK.
Select
.Specify the filename and location of where you want the DSTRACE information saved, then click Open.
Wait for the event to occur.
Select
.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.
Type ndstrace to start the ndstrace utility.
Type set ndstrace=nodebug
Turns off all trace flags currently set.
Type set ndstrace on
Displays trace messages to the console.
Type set ndstrace file on
Captures trace messages to the file ndstrace.log the directory where eDirectory is installed. By default it is /var/nds.
Type set ndstrace=+dxml
Displays the Identity Manager events.
Type set ndstrace=+dvrs
Displays the Identity Manager driver events.
Wait for the event to occur.
Type set ndstrace file off
This stops the logging of information to the file.
Type 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. These are the files that run iMonitor:
NDSIMON.NLM Runs on NetWare.
NDSIMON.DLM Runs on Windows*.
ndsimonitor Runs on UNIX.
Access iMonitor from http://server_ip:8008/nds.
The port of 8008 is the default port.
Enter in a user name and password with administrative rights, the click
.Select
on the left side.Click
.Select DirXML and DirXML Drivers.
Click
.Select
on the left side.Click the document with the Modification Time of Current 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.You can view the trace history by selecting Trace History. The files are distinguished by their timestamp.
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 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 following switches. For more information, see Section 3.4, Configuring the Remote Loader.
Table 2-3 Command Line Tracing Switches