In order to best help you with Identity Manager, we need to have some
understanding of your environment, of what you are trying to do, and what
is happening when you try.

First, it is helpful if you post some basic information about your IDM
system, including:

Operating System (ID Vault): ______________ Version: _____
Operating System (Connected System): ______________ Version: _____
Identity Manager Version: ______________
Identity Manager Driver: ______________ Version: _______
Identity Manager Driver Preconfig / Version: _______
Remote Loader: Yes/No
Remote Loader Version: _______

Not all of these are necessarily going to be relevant to all problems,
but it saves time if these are included in the first post, rather than
having to go back-and-forth to get them.

Second, having a clear description of what you are trying to accomplish
is important. Identity Manager polices are a programming language, and
clear goals lead to clear code. If you can summarize your goal in to a
few sentences, then that usually helps us figure out how to help you
reach it. Conversely, if you cannot summarize your goal, it is likely
that we won't be able to help you reach it.

Third, please include a summary of what you have tried. Ideally this
includes your policy (or stylesheet), and a sample <input> document, so
that we can see what you are getting and what you are trying to do with
it. By including these, you make it easier for us to help you figure out
where you are stuck, rather than having to re-implement your goals from
scratch.

Forth, and probably the most important of all, a "level 3 trace" of the
IDM engine processing your sample <input> document. IDM has a wonderful
"trace" facility that shows what the engine got (the "input" document),
the processing of every policy that acted on the document, the eventual
resulting command document, and the status return along with any error
messages. Having this makes troubleshooting problems in policy,
eDirectory, or the connected system, much easier.

To get this trace, first configure the Java Trace File, then configure
the Trace Level. These can be done with iManager or Designer.

Designer: Right click on the driver (line).
Select "Properties"
Go to the Trace tab
Set the Trace Level to 3
Set the Trace File to a path and file name appropriate for
your engine host operating system like:
Linux: /tmp/drivername.log
Windows: c:\drivername.log
NetWare: sys:system\drivername.log
Save the changes
Deploy the driver

iManager: In the IDM Administration tasks, Driver Set Overview, find
the Driver you want to trace.
Click on the status icon (green circle).
Select "Edit properties"
Go to the "Misc" tab
Set the Trace Level to 3
Set the Trace File to a path and file name appropriate for
your engine host operating system like:
Linux: /tmp/drivername.log
Windows: c:\drivername.log
NetWare: sys:system\drivername.log
Save the changes

The trace will start immediately. Now try whatever it is that you're
trying to do. After the event is processed, use the same steps as above
to stop the trace. Take the resulting trace file and post it somewhere
like pastebin.com so that we can see it. If necessary, please edit out
any sensitive or personal information in the trace. In your post, include
the URL to the trace.


--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.novell.com

Please post questions in the forums. No support provided via email.