Netscape NETSCAPE DIRECTORY SERVER 6.02, Руководство администратора

Страница: 89 / 568

Creating and Maintaining Databases
Chapter 3 Configuring Directory Databases 89
Add a new entry to the configuration file by performing an
ldapmodify
as follows:
ldapmodify -a -h example1 -p 389 -D "cn=directory manager" -w secret
The
ldapmodify
utility binds to the server and prepares it to add an entry to the
configuration file.
Next, you create the entry for the new database as follows:
dn: cn=UserData,cn=ldbm database,cn=plugins,cn=config
objectclass: extensibleObject
objectclass: nsBackendInstance
nsslapd-suffix: ou=people,dc=example,dc=com
The entry added corresponds to a database named
UserData
that contains the data
for the root or sub suffix
ou=people,dc=example,dc=com
.
To create a root or sub suffix from the command line, refer to “Creating Root and
Sub Suffixes From the Command Line,” on page 80. The database name, given in
the DN attribute, must correspond with the value in the
nsslapd-backend
attribute of the suffix entry.
Adding Multiple Databases for a Single Suffix
You can distribute a single suffix across multiple databases. However, to distribute
the suffix you need to create a custom distribution function to extend the directory.
For more information on creating a custom distribution function, contact Netscape
Professional Services.
NOTE Once you have distributed entries, you cannot redistribute them.
The following restrictions apply:
• You cannot change your distribution function once you have
deployed entry distribution.
• You cannot use the LDAP
modrDN
operation to rename entries
if that would cause them to be distributed into a different
database.
• You cannot replicate distributed local databases.
• You cannot use the
ldapmodify
operation to change entries if
that would cause them to be distributed into a different
database.
Violating these restrictions prevents Directory Server from
correctly locating and returning entries.