Installation guide

Migration Procedure
Chapter 6 Migrating and Upgrading From Previous Versions 91
2. Move your custom schema elements to the following files:
serverRoot/slapd-serverID/config/slapd.user_at.conf and
serverRoot/slapd-serverID/config/slapd.user_oc.conf
These file names are recommended because the 4.x schema configuration
editor writes to them. However, you can use any file name you like.
Note that if there are inheritance relationships between custom defined object
classes, you must ensure that in the order in which they appear in the schema
configuration file, the superior object class is defined before the others.
3. Include these files into your slapd.conf file using the userat and useroc
directives. Place your new directives at the same place in the file as the include
statements for other configuration files.
The order in which the various configuration files are included is not
important. Then, if you added custom attributes to standard object classes in
slapd.oc.conf, you must do the following:
a. In the slapd.user_oc.conf file (or your equivalent), create a new object
class that includes your custom attributes.
b. Add this new object class to every entry in your directory that uses the
custom attributes.
Migration Procedure
Before you start with migration process, ensure the following:
• Read sections “Migration Overview” on page 87 and “Migration Prerequisites”
on page 88.
• The migration script will automatically back up your Directory Server
configuration, if it’s in the default location.
❍ If you are migrating from Directory Server 4.x, all of the files with a
.conf extension in the /usr/netscape/server4/slapd-serverID
directory are backed up.
❍ If you are migrating from Directory Server 5.x, all of the configuration
files in the
/usr/netscape/servers/slapd-serverID/config directory
will be backed up to a directory named
serverRoot/slapd-serverID/config_backup.
If your configuration files are stored in non-default locations, before you
migrate your server, copy them to a secure place.