Red Hat DIRECTORY SERVER 7.1 - ADMINISTRATOR Administrator's Manual page 400

Table of Contents

Advertisement

Creating Indexes
First, type the following to change to the directory containing the utility:
cd serverRoot/shared/bin
Run the
ldapmodify -a -h server -p 389 -D "cn=directory manager" -w
password
The
ldapmodify
configuration file.
Next, you add the following entry for the new indexes:
dn: cn=sn,cn=index,cn=Example1,cn=ldbm
database,cn=plugins,cn=config
objectClass:top
objectClass:nsIndex
cn:sn
nsSystemIndex:false
nsIndexType:pres
nsIndexType:eq
nsIndexType:sub
nsMatchingRule:2.16.840.1.113730.3.3.2.3.1
The
cn
example, the
nsSystemIndex
Directory Server operations. The multi-valued
the presence (
to be entered on a separate line. The
of the Bulgarian collation order.
Specifying an index entry with no value in the
indexes (except international) being maintained for the specified attribute. For
example, suppose instead that you specify the following entry for your new
indexes:
dn: cn=sn,cn=index,cn=
database,cn=plugins,cn=config
objectClass:top
objectClass:nsIndex
cn:sn
nsSystemIndex:false
nsIndexType:
This new entry results in all indexes for the
400
Red Hat Directory Server Administrator's Guide • May 2005
command-line utility as follows:
ldapmodify
utility binds to the server and prepares it to add an entry to the
attribute contains the name of the attribute you want to index, in this
attribute. The entry is a member of the
sn
attribute is
false
), equality (
pres
, indicating that the index is not essential to
nsIndexType
) and substring (
eq
sub
nsMatchingRule
nsIndexType
database_name
,cn=ldbm
(surname) attribute.
sn
object class. The
nsIndex
attribute specifies
) indexes. Each keyword has
attribute specifies the OID
attribute results in all
sn

Advertisement

Table of Contents
loading

This manual is also suitable for:

Directory server 7.1

Table of Contents