5.1 Determining Identity Vault Object Placement When a Notes Object is Moved

A Move is done by 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 the Identity Vault, so it isn’t possible to provide a parent association. Also, the driver shim has no reference of the Identity Vault namespace or containment, so it can’t provide a parent dest‑dn (destination DN). Therefore, an appropriate parent dest‑dn must be provided by a policy.

Notes - Move Sample is a sample Publisher channel policy that contains logic to determine Identity Vault object placement when an associated Notes object is moved.

This policy is designed to provide the same functionality contained in the sample style sheet named placemove.xsl, provided with earlier versions of the driver. A sample configuration is also available with in NotesConfig21.xml, which demonstrates the driver object’s move and rename capabilities.

On a move, the dest‑dn is set for a particular source dn. After importing the Notes - Move Sample policy, you have a policy defining a single mapping between source and destination containers. You can define additional mappings by editing the resulting policy.

NOTE:Because of the way Notes manages CN and DN in FullName, it is not possible to distinguish between a Move and a Rename event in ndsrep. Therefore, when ndsrep determines that the FullName item has changed, it generates both a Move and a Rename event.

To add the Notes - Move Sample policy to your driver configuration:

  1. Open Designer, go to Outline tab in the left and expand the Identity Vault where you deployed your driver.

  2. Go to driverset > Notes Driver > Subscriber.

  3. In the Policy Set tab below Outline tab, select Event Transformation and click .

  4. In the Add Policy Wizard box, select Create a new policy and click Next.

  5. Enter policy name as Move Sample and click Next.

  6. Select DirXML Script and click Finish.

  7. Click Yes to confirms the policy is getting saved.

  8. Select the Move Sample policy and go to XML source tab in the right.

  9. Replace <policy/> with the following content:

    <policy>
<rule>
<description>Move Sample</description>
<comment xml:space="preserve">Sample of handling moves for Lotus Notes.  The rule contained in this policy should be copied/edited for each container mapping required.</comment>
<conditions>
<and>
<if-operation op="equal">move</if-operation>
<if-xpath op="true">parent[@src-dn='noteSource.data']</if-xpath>
</and>
</conditions>
<actions>
<do-set-xml-attr expression="parent[@src-dn='noteSource.data']" name="dest-dn">
<arg-string>
<token-text xml:space="preserve">data\NoteDest</token-text>
</arg-string>
</do-set-xml-attr>
</actions>
</rule>
</policy>

  10. Save it.

  11. In Identity Console, go to IDM Administration > driverset > Notes Driver > Data Transformation and Synchronization and select Policies tab.

  12. Select the Movie Sample and complete the “mappings” for all the containers in Notes and Identity Vault by editing the XML for the policy.