HP-UX Directory Server Administrator Guide HP-UX Directory Server Version 8.1 (5900-3332, November 2013)

7. To create an index for a language other than English, enter the OID of the collation order to
use in the Matching Rules field.
To index the attribute using multiple languages, list multiple OIDs separated by commas, but
no white space. For a list of languages, their associated OIDs, and further information regarding
collation orders, see “Internationalization” (page 573).
8. Click Save.
9. The Indexes dialog box appears, displaying the status of the index creation and informing
you when the indexes have been created. Click the Status Logs box to view the status of the
indexes created. After the indexing is complete, click Close.
The new index is immediately active for any new data that you add and any existing data in your
directory. You do not have to restart your server.
Creating indexes from the command line
Creating presence, equality, approximate, substring, and international indexes for specific attributes
from the command line involves two steps:
1. Using the ldapmodify command line utility to add a new index entry or edit an existing
index entry. See Adding an index entry” (page 455).
2. Running the db2index.pl Perl script to generate the new set of indexes to be maintained
by the server. See “Running the db2index.pl script” (page 456).
NOTE:
You cannot create new system indexes because system indexes are hard-coded in Directory Server.
Adding an index entry
Use ldapmodify to add the new index attributes to your directory.
To create a new index that will become one of the default indexes, add the new index attributes
to the cn=default indexes,cn=config,cn=ldbm database,
cn=plugins,cn=config entry.
To create a new index for a particular database, add it to the
cn=index,cn=database_name,cn=ldbm database,cn=plugins,cn=config entry,
where cn=database_name corresponds to the name of the database.
NOTE:
Avoid creating entries under cn=config in the dse.ldif file. The cn=config entry in the
simple, flat dse.ldif configuration file is not stored in the same highly scalable database as
regular entries. As a result, if many entries, particularly entries that are likely to be updated
frequently, are stored under cn=config, performance will probably suffer. Although we recommend
you do not store simple user entries under cn=config for performance reasons, it can be useful
to store special user entries such as the Directory Manager entry or replication manager (supplier
bind DN) entry under cn=config because this centralizes configuration information.
For information on the LDIF update statements required to add entries, see “LDIF Update Statements
(page 120).
For example, to create presence, equality, and substring indexes for the sn (surname) attribute in
the Example1 database, do the following:
1. Run ldapmodify.
ldapmodify -a -D "cn=directory manager" -w secret -p 389 -h server.example.com
The ldapmodify utility binds to the server and prepares it to add an entry to the configuration
file.
2. Add the LDIF entry for the new indexes:
Creating indexes 455