Netscape DIRECTORY SERVER 6.0 Installation Manual

Also see for NETSCAPE DIRECTORY SERVER 6.0: Deployment guide Reference Configuration guide

Contents

Netscape DIRECTORY SERVER 6.0 Installation Manual Manual pdf 71 page image

Identifying Custom SchemaChapter 6 Migrating From Previous Versions 71If you will not be running your legacy Directory Server, use the same portnumbers to ensure that any directory clients that have static configurationinformation (including directory server port numbers) will continue to work.• Your Directory Server 6.0 must be running when you execute the migrationscript.• Any custom schema that you created in a legacy 4.x Directory Server must bestored in the default files or included using an include statement in theslapd.conf file. The default files for custom schema are slapd.user_oc.confand slapd.user_at.conf files in Directory Server 4.x. If you have customschema that is not stored in those files, refer to the procedure described in“Identifying Custom Schema” to move it to those files.• Any custom schema that you created in a 5.0 Directory Server must be storedin an LDIF file in the/usr/netscape/servers/slapd-serverID/config/schema directory.• On UNIX, set the following environment variables:PERL5LIB=/usr/netscape/servers/bin/slapd/admin/binPATH=/usr/netscape/servers/bin/slapd/admin/bin:$PATH• On NT, set the following environment variable:PERL5LIB=server5root\bin\slapd\admin\binand add server5root/bin/slapd/admin/bin to the PATH environmentvariable. Replace server5root with the directory under which you installedthe Directory Server.Identifying Custom SchemaIf you customized the schema in your legacy Directory Server by modifyingslapd.at.conf or slapd.oc.conf directly, then the server migration processcannot migrate your custom schema for you. Instead, you are notified duringmigration that you have modified the standard schema and that you need tomanually fix the problem. The migration process then saves a copy of your schemafiles and uses standard legacy schema files in their place.While the migration will complete in this situation, you will probably find that youcannot modify your data in Directory Server 6.0. Therefore, you are stronglyrecommended to copy your custom schema into separate files before you performthe migration. You can use the standard slapd.user_oc.conf andslapd.user_at.conf files or any files declared in slapd.conf with the userocand userat keywords respectively.