Notes Driver Basics
Identity Manager fundamentals are explained in the Novell Nsure Identity Manager 2 Administration Guide. This documentation discusses implementations, additions, or exceptions, specific to the DirXML Driver for Lotus Notes.
Default Data Flow
Subscriber Channel
The Subscriber channel is the channel of communication from eDirectory to Lotus Notes. The following illustration shows this data flow:

The driver can be configured to work with Notes databases other than names.nsf.
Publisher Channel
The Publisher channel represents the channel of communication from Lotus Notes to eDirectory. The following illustration shows how this data is published:

Policies
Policies are used to control the synchronization of data between eDirectory and the application, database, or directory. Policies transform an event on a channel input into a set of commands on the channel output. The driver includes the following set of preconfigured policies:
- Schema Mapping: Mappings have been defined for the Notes address book.
- Creation: The default Creation policy logic for the Publisher channel and the Subscriber channel is the same. For a User object to be created, Given name and Surname are required. For a Group object to be created, Description, Membership, and Owner are required.
- Matching: The default Matching policy logic for the Publisher channel and the Subscriber channel is the same. An eDirectory User object is considered to be the same object in Notes when Given name and Surname match in both directories. An eDirectory Group object is considered to be the same object in Notes when the CN is the same in both directories.
- Placement: The default Placement policy on the Subscriber channel places all User objects from a specified eDirectory container in a specified Notes Organizational Unit, and all Group objects from a specified eDirectory container in a specified Organizational Unit in Notes. The same relationship is typically maintained on the Publisher channel. The container names and OU names for this default Placement policy are collected from the user when importing the default driver configuration.