Identifying Custom Schema - Netscape DIRECTORY SERVER 6.01 Installation Manual

Identifying Custom Schema

Identifying Custom Schema
If you customized the schema in your legacy Directory Server by modifying
slapd.at.conf
cannot migrate your custom schema for you. Instead, you are notified during
migration that you have modified the standard schema and that you need to
manually fix the problem. The migration process then saves a copy of your schema
files and uses standard legacy schema files in their place.
While the migration will complete in this situation, you will probably find that you
cannot modify your data in Directory Server 6.0. Therefore, you are strongly
recommended to copy your custom schema into separate files before you perform
the migration. You can use the standard
slapd.user_at.conf
and
userat
To separate your custom schema from your standard schema:
Examine your old
1.
schema additions that you made there.
To ensure that you have properly identified all your changes to standard files,
you can compare them with the standard files provided in the
/bin/slapd/install/version4
tried to run the
Move your custom schema elements to the following files:
2.
/usr/netscape/servers/slapd-serverID/config/slapd.user_at.conf and
/usr/netscape/servers/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.
Include these files into your
3.
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.
76 Netscape Directory Server Installation Guide • March 2002
or
slapd.oc.conf
files or any files declared in
keywords respectively.
slapd.at.conf
migrateInstance6
slapd.conf
directly, then the server migration process
slapd.user_oc.conf
slapd.conf
and
slapd.oc.conf
directory. Alternatively, if you have already
script, use the notifications that it issues.
file using the
and
with the
useroc
files to discover all the
and
userat useroc