I am curious as to what 9 digit system attribute you are matching on? We
have been trying to find a good way to match acounts...

We

someone

Renaming

Let's say that I am creating a user, FRAMON, in the
Novell/Experts/IDM/Users container. IDM will now create that user in my
identity vault in Vault/Users. I want to parse the DN of FRAMON and store
his context (Novell/Experts/IDM/Users)with my valut object. I will use
this for notification purposes, etc. Our file and print tree is very
nested, and our vault is very flat.

I have tried:

Parse DN
Source DN()

Parse DN
Source Attribute DN()

But I get -613 syntax violation. I don't know if parse is the right
verb....I just know I need to somehow capture the user's location/context
in the original tree.

We are migrating from a current install of the original DirXML starter
Pack. (1.0 NW 5.1 days that has been upgraded through the years to NW
6.5 1.1a).

DirXML Structure:
6 OU representing our locations. Each ou has ADSYNC driver set and
ADDriver. Each office has a DirXML engine running on a W2K server
w/PWSync. The driver set is configured to handle just that OU sync to
a matching AD OU.

Target IDM Structure.
IDM Vault Engine etc running on one W2K3 server at corp. Remote loader
running on W2K3 server at each office. Driver (Remote loader)
configured to handle separate OU's as we migate.

Consern and Question:
Each office has users that have been proccessed with the existing
DirXML 1.1 and have the Proccessed GUID in the users DirXML tap through
Console one.

We have had users recreated at UserDoe1 and back again into NDS after
working with the driver.

Thanks, I actually got it working late yesterday. I wish I could say for
sure what it was, but honestly I'm not real sure. All I did was delete and
recreate using the rule you previously posted as a template and VOILA!!
There it was..working like a champ!! Thanks for your responses and
assistance!!

Joey

xmlns:query="http://www.novell.com/nxsl/java/com.novell.nds.dirxml.driver.XdsQueryProcessor">

On Wed, 17 Jan 2007 16:04:01 GMT, Rob wrote:

Thanks! This is just what I needed!!!

Hello....

I am trying to place a rule in my eDir-eDir driver that:

When a user is created in my Identity Vault, it will parse the DN of the
source DN of the user, and set a variable on the object in the vault
equal to that string (so that we can reference it's location in the
source tree).

I have used the parseDN before to parse the creator's name, but I cannot
get the parse token to work when trying to prse the source DN.

parse DN (SourceDN)
parse DN (source attribute DN)
parse DN (operatrion attribute DN)??

I have tried the above combinations, and I get syntax errors. (I have
been putting this policy in the command transformation policies).

Does anyone know how to write this? Thanks so much, Jordan

Hi Perry, thanks for you reply

I have updated Domino driver to the latest version and it seem like it
is working fine now.

Regards,
Tyrrayo

Perry Nuffer wrote:

Hi there,
We're going through a scoping exercise for a GroupWise IDM3 driver. The
implementation guide says that "The driver can connect to a secondary
GroupWise domain, but Novell recommends that the GroupWise driver connects
to the primary GroupWise domain".

The client has four Domains and four relevant Post Offices. Can one GW
driver do it all or should we consider four drivers? Users do move around
and could need to be placed in an OU that is logically serviced by a
different Domain.

Cheers,
Kirk

Thanks for that. We'll give it a try in the coming weeks.
Cheers,
Kirk