Selecting Consistent Data Formats; Maintaining Consistency In Replicated Schema - Netscape DIRECTORY SERVER 6.2 - DEPLOYMENT Deployment Manual

Selecting Consistent Data Formats

LDAP schema allow you to place any data that you want on any attribute value.
However, it is important to store data consistently in your directory tree by
selecting a format appropriate for your LDAP client applications and directory
users.
With the LDAP protocol and Directory Server, you must represent data in the
data formats specified in RFC 2252.
In addition, the correct LDAP format for telephone numbers is defined in the
following ITU-T Recommendations documents:
• ITU-T Recommendation E.123.
Notation for national and international telephone numbers.
• ITU-T Recommendation E.163.
Numbering plan for the international telephone services.
For example, a US phone number would be formatted as follows:
+1 555 222 1717
The attribute expects an attribute value in the form of a multiline
postalAddress
string that uses dollar signs ($) as line delimiters. A properly formatted directory
entry appears as follows:
postalAddress: 1206 Directory Drive$Pleasant View, MN$34200

Maintaining Consistency in Replicated Schema

When you make changes to your directory schema, the change is recorded in the
change log. During replication, the change log is scanned for changes, and any
changes made are replicated. Maintaining consistency in replicated schema allows
replication to continue smoothly. Consider the following points for maintaining
consistent schema in a replicated environment:
• Do not modify the schema on a read-only replica.
Modifying the schema on a read-only replica introduces an inconsistency in
your schema and causes replication to fail.
Maintaining Consistent Schema
Chapter 3 How to Design the Schema 55