Front cover - IBM Redbooks

Unlike other synchronizations, the consistency process does not create
documents in the destination database according to a bijective relation with
documents in the source database. The primary purpose is to maintain linkages
between some values stored in the source database and other values stored in
the destination database.
Unlike relational databases, Domino cannot set up links between fields that are
stored in different documents. For example: Person documents in your Domino
Directory contain the names and phone numbers of your sales executives. Now,
assume these phone numbers are also stored in other Domino databases such
as Customer management, Sales leads, and Purchasing. If the phone number is
modified in the Person document, Domino cannot inherently pass on this
modification to a different database document that also contains this phone
number.
In this scenario, there is not a bijective relation between the documents
respectively stored in the two databases. Values associated to one single
document in the source database (the ones we consider authoritative source
“reference values”) are synchronized with several documents in the destination
database (non-authoritative “derived values”). Like in relational databases, this
consistency synchronization is a way to maintain data normalization (value
unicity).
LDAPSync can be used to maintain a strong consistency between field values
that are stored in different documents/databases, without having to modify
already used databases. You should define the database containing reference
values (for instance, your company's LDAP directory) as the (authoritative)
source database, and the databases containing derived values (Domino
Directory, Contacts database, and so forth) as the destination databases.
LDAPSync will carry out updates on these values whenever the reference values
have been changed.
Note that LDAPSync is limited to retrieval of data from LDAP or Domino
database sources, and is capable of updating only Domino databases. For
additional types of data source and destination connectivity, we recommend IBM
Tivoli Directory Integrator, which we discuss next.
IBM Tivoli Directory Integrator
IBM Tivoli Directory Integrator synchronizes identity data residing in directories;
databases; collaborative systems; applications used for HR, CRM, and ERP; and
other corporate applications.
By serving as a flexible synchronization layer between a company's identity
structure and the application sources of identity data, Directory Integrator
eliminates the need for a centralized data store. For those enterprises that do
Chapter 8. Directory strategies 331