Because of the way Notes manages CN and DN in FullName, it is not possible to distinguish between a Move and Rename event in NDSRep. Therefore, when NDSRep determines that the FullName item has changed, it will generate both a Move and a Rename event.PLACEMOVE.XSL is an Input Transformation style sheet that contains logic to determine eDirectoryTM object placement when an associated Notes object is moved. A Move is done by NsureTM Identity Manager relative to either a parent's association key or dest-dn. Containment in Notes is purely logical, and as such, an OU in Notes never has an association to eDirectory, so it isn't possible to provide a parent association. Also, the driver has no reference of the eDirectory namespace or containment, and therefore can't provide a parent dest-dn.
As a result, it is necessary to provide a rule that has the ability to map the Notes OU DN to the eDirectory OU DN. PLACEMOVE.XSL shows how to do this mapping. In the following example from PLACEMOVE.XSL, change the first path to reflect the Notes containment. Change the second path to the target eDirectory container.
<xsl:when test="string($dn) = '\dirxml\engineering'">
<xsl:value-of select="'wazzup_labs\notes\users\eng'"/>
</xsl:when>
Add a when statement for each Notes OU that contains objects to be synchronized with eDirectory.
注: The Notes driver does not support moves or renames from eDirectory on the Subscriber Channel.