Installing the Directory Server

If you specified a root DN in Step 9, enter a corresponding password. This password is required. The password must be at least eight characters in length.

Warning

It is possible for the root password to be deleted from the server by directly editing the server's configuration file (slapd.conf). In this situation, the root DN can only obtain the same access to your directory as you allow for anonymous access. Always make sure that a root password is defined in slapd.conf when a root DN is configured for your database.

For more information about slapd.conf, see the Netscape Directory Server Administrator's Guide.

Click OK.

If the configuration was successful, you will see a page showing your new server's name, the port it uses, and the location of your database. From this page, you can configure your server further, start your new server, register your server for technical support, install another server, or return to the server selector. Clicking the "Configure your server further" link will take you to the server manager, where you can configure your server. For more information about the server manager, refer to Managing Netscape Servers.

Creating a Directory Tree

After you have installed a directory server instance, you need to create a database to use with your server; a database is not created for you during server installation, unless you checked "Configure Directory for SuiteSpot" when you created your server instance.

Although you do not need to create your entire directory tree now, you should at least set up the major branch points of your tree before you continue installing additional directory server instances (consumers) or the NT synchronization service.

Note

Currently your database must be in the <NSHOME>/slapd-<serverID>/db directory.

There are several ways you can create a directory:

Create a database from LDIF--Use this method if you want to use the sample directory shipped with the directory server, if you are importing entries from another directory via LDIF, or if you have more than a few entries to add at once. For more information about LDIF, refer to Chapter 2 of the Netscape Directory Server Administrator's Guide.

Start your directory server with an empty database--This method requires you to populate your directory using an LDAP client such as the directory server gateway or the ldapmodify command-line utility. Use this method if you have just a few entries to add at a time. For information on setting up the directory server gateway, see Chapter 5, "Configuring the Gateway."

Use the Create SuiteSpot settings form--From the server manager, select Database Management|SuiteSpot Settings. Filling out this form creates a basic directory and sets minimum access control for the directory. You need to use the ldapadd command-line utility or the directory server gateway to populate the directory.

As you are populating your directory, consider your access control needs and set access control accordingly. If you do not set any access control for your directory, you will be able to access your directory only as the root DN. You had the opportunity to configure the root DN in Step 9. For more information on access control, see the Netscape Directory Server Deployment Guide and the Netscape Directory Server Administrator's Guide.

Upgrading Your Directory Service

You can upgrade to Netscape Directory Server 3.1 from either the 3.0 or 1.x release. For information, see "Upgrading from Directory Server 3.0" or "Upgrading from Directory Server 1.x" as appropriate.


Item	Description and example	Value for your server
Server name	The name your server runs as. For example: `phonebook.airius.com`
Server port	The port you use for standard LDAP connections (not encrypted).
Encryption enabled?	Indicates whether you are using encryption (LDAPS) with your 1.x directory server.
Encrypted port	The port you use for LDAPS (encrypted) connections.
Server identifier	The name of the directory under which your directory server is installed. For example, if your server was installed with the server name of phonebook, then your server was probably installed at: `<NSHOME>/slapd-phonebook`
Database subtree	The directory suffix. You will have at least two suffixes set for your directory. One equates to your directory root point (for example, `o=airius.com`) and one will be related to your directory's machine data area (for example, `dc=name`, `dc=domain`, `dc=domain`). Record the suffix name that you store your primary directory contents under. If your directory serves more than one suffix, record all of your suffixes.
Root DN	The user who has unrestricted access to the directory. For example, directory manager.
Root DN password	The password that corresponds to the root DN user.

Installing the New Server Instance

Once you have saved your configuration files and old database, you are ready to install the new server instance. Use the procedure titled "Installing a Directory Server Instance" to install the server. Use the information you recorded in Table 4.1 when prompted for configuration information.

Note

The new installation form has an option that allows you to configure your directory server for integration with other SuiteSpot 3.x servers. Do not select this option. This option creates a directory database that will only be overwritten when you recreate your database from the LDIF file you created from your old database. You can manually configure your server for SuiteSpot integration. See the Netscape Directory Server Administrator's Guide for instructions.

Updating the Configuration Files

When you installed the new server instance, a new server configuration file, slapd.conf, was created. You must manually update the new file with any configuration changes you made to your 1.x server configuration. (You do this by comparing the old slapd.conf file you saved in Step 3 of the procedure titled "Saving the Configuration Files" with the new slapd.conf.) Update your new slapd.conf file with any parameter values that exist in the old version of the file but not in the new version. Some parameters that commonly need updating are the index and suffix parameters.

In addition, if you made any changes to the gateway configuration file, dsgw.conf, in your 1.x installation, you should copy the old file that you saved (in Step 5 of the procedure titled "Saving the Configuration Files") to the following location in the new directory server installation:

<NSHOME>/slapd-<serverID>/dsgw/config

Extending the Schema

If you extended the schema in your 1.x directory server installation, you must make the same extensions in your 3.1 schema configuration before you import your LDIF database. You must also extend the 3.1 schema configuration if you used any of the object classes or attributes that were in use in the 1.x product but that have been removed for the 3.1 release.

For a list of the obsolete object classes and attributes, look in relnotes.htm included on the product CD or go to the following URL:

http://home.netscape.com/eng/server/directory/3.1/relnotes.htm#delobj

If you are unsure of what modifications you made to your schema, you can refer to the attribute configuration file (slapd.at.conf) and object class configuration file (slapd.oc.conf) that you saved in Step 4 of the procedure titled "Saving the Configuration Files". Any new attributes that were added are listed after the # attributes below added for Netscape Directory Server 1.x comment line in the slapd.at.conf file. Any new object classes that were added are listed after the # objectclasses below added for Netscape Directory Server 1.x comment line in the slapd.oc.conf file.

You can extend the schema using the 3.1 directory server manager as follows:

Make sure your 1.x directory server is shut down.

Start your 3.1 directory server.

Select the Schema tab from the directory server manager.

You can create custom attributes by selecting Edit or View Attributes.

You can create custom object classes by selecting Create Objectclass.

You should not modify a standard object class or attribute. Instead, to extend the schema create new object classes and attributes. For more information on extending the schema, refer to the Netscape Directory Server Administrator's Guide.

Stop the directory server.

Upgrading the Access Control Statements

You can upgrade your 1.x access control statements to use the new 3.1 syntax using the aclupg utility.

Before you can use the aclupg utility, you must update the PATH variable to include the location of the aclupg utility, which is <NSHOME>/bin/slapd/server. On Unix systems you should also set your LD_LIBRARY_PATH variable to include the following two locations:

<NSHOME>/lib

<NSHOME>/bin/slapd

For information on how to set environment variables, see your operating system documentation.

To run the aclupg utility, do the following:

Save your 1.x database to LDIF.

Enter the following command:

aclupg -i <filename>

where <filename> is the name of the LDIF file you want to convert. The updated LDIF file is saved as the aclupgrade.ldif file in the same directory as the file you converted.

Importing the LDIF File

After you have upgraded the ACL statements in the old LDIF file, you can import the old LDIF file into your new database as follows:

Copy the LDIF file that you saved earlier (in Step 2 of the procedure titled "Saving the Configuration Files") to the following location in the new server instance installation:

<NSHOME>/slapd-<serverID>/ldif

From the directory server manager, go to Database Management|Import.

Select the LDIF file from the list of possible files, or enter the full path to the LDIF file in the field provided.

Click OK.

The new directory database is created and placed in the database directory for you.

Start the directory server.

Removing the 1.x Directory Server Instance

Do not remove the 1.x directory server until you have successfully migrated to 3.1. To remove the 1.x directory server instance, do the following:

Stop the 1.x directory server.

From the directory server manager, click "Remove a server from this machine."

In the "Remove this server" pull-down list, select the directory server instance you want to remove.

Under Verification, click Yes next to "Yes, I really do want to remove this server." Do not click Yes next to "Remove the administration binaries as well."

Click OK to remove the directory server instance.

Creating the SuiteSpot Integration Entries

If you want your new directory server to manage user and group information for other SuiteSpot 3.x servers, you must make some directory modifications to allow the 3.x administration server to bind to the directory and perform directory management activities.

See the section titled "Managing SuiteSpot 3.x Integration" in the Netscape Directory Server Administrator's Guide for a discussion of the entries that must be created for integration with SuiteSpot 3.x servers.

If you decide that you want to create the SuiteSpot 3.x integration entries, see the section titled "Creating SuiteSpot 3.x Integration Entries" in the Netscape Directory Server Administrator's Guide for instructions.

Upgrading a Replicated Site

To upgrade a replicated 1.x directory service to 3.1, do the following:

Upgrade your consumer servers using the process defined in "Automatically Upgrading from 1.x to 3.1" or "Manually Upgrading from 1.x to 3.1".

Before you can replicate to an upgraded consumer server, you must configure the supplier DN password. Do this on the consumer server using the Consumer Server Replication Settings area of the Replication | Configure this Server form.

Also, when you upgrade your consumer servers, you can start them and continue with normal operations because a 1.x supplier server can replicate to a 3.1 consumer server. However, a 3.1 supplier server cannot replicate to a 1.x consumer server.

Once you have upgraded all of your consumer servers, upgrade your 1.x supplier server to 3.1 using the process defined in "Automatically Upgrading from 1.x to 3.1" or "Manually Upgrading from 1.x to 3.1".

Before you can replicate to your consumer server(s), you must configure your supplier's change log. Do this on the supplier server using the Supplier Server Replication Settings area of the Replication | Configure this Server form.

Reinitialize all your consumer servers. If you are replicating an entire database that contains more than 5,000 - 10,000 entries, you should consider using a manual consumer initialization process. That is, use the Replication | Manual Consumer Initialization form instead of the Initialize Consumer button in the Replication | Configure Replication Agreements form.

For information on how to initialize consumer servers, see the Netscape Directory Server Administrator's Guide.

Museum

Installing the Directory Server

Performing a New Installation

Installing a Directory Server Instance

Upgrading from Directory Server 1.x

Automatically Upgrading from 1.x to 3.1

Updating the Configuration Files

Extending the Schema

Upgrading a Replicated Site