This chapter describes how to perform basic installation activities. This chapter contains the following sections:
Using Express Installation
Using Typical Installation
Creating a Directory Tree
Using Netscape SuiteSpot 3.x Servers with a Netscape 4.x Directory Server
To perform an express installation, do the following:
On Unix machines, log in as root (root login is required for express installation). On Windows NT machines, login with Administrator privileges.
If you have not already done so, download the product binaries file to the installation directory.
On Unix, unpack the product binaries file using the following command: # gzip -dc <filename>.tar.gz | tar -xvof- where <filename> corresponds to the product binaries that you want to unpack. On Windows NT, unzip the product binaries.
# gzip -dc <filename>.tar.gz | tar -xvof-
where <filename> corresponds to the product binaries that you want to unpack.
On Windows NT, unzip the product binaries.
Run the setup program. You can find it in the directory to which you untarred or unzipped the installation files.
When you are asked what you would like to install, select the default, Netscape Servers.
When you are asked what type of installation you would like to perform, select Express Installation.
For server root or destination directory, enter a full path to the location where you want to install your server. The location that you enter must be some directory other than the directory from which you are running setup. If the directory that you specify does not exist, setup creates it for you.
For server components, select the default (all components). On Windows NT, you can deselect the NT Synchronization Service component if you are not going to synchronize user and group information between this Windows NT host and your Directory Server. For information on how to install the NT Synchronization Service, see Chapter 5, "Installing and Configuring the Synch Service."
Unix only. For the user and group to run the servers as, enter the identity that you want this server to run as. For more information on the user and groups that you should use when running Netscape servers, see "Decide Which User and Group to Run Netscape Servers As (Unix only)".
For Configuration Directory Administrator ID and password, enter the name and password that you will log in as when you want to authenticate to the console with full privileges (think of this as the root or superuser identity for the Netscape Console).
For Directory Manager DN, enter the distinguished name that you will use when managing the contents of your directory with unlimited privileges (in former releases of the Directory Server, the Directory Manager was labeled the root DN). This is the entry that you bind to the directory as when you want access control to be ignored. This distinguished name does not need to conform to any suffix configured for your directory. It also should not correspond to an actual entry stored in your directory. Examples of possible directory manager DNs are: cn=Directory Manager cn=root uid=admin
cn=Directory Manager
cn=root
uid=admin
For Directory Manager password, enter a value that is at least 8 characters in length.
Note the following about your new Directory Server installation:
The Directory Server is listening on port 389.
The server is configured to use the following suffixes:
o=<your machine's DNS domain name> That is, if your machine is named test.airius.com, then you will have the suffix o=airius.com configured for this server.
dc=<host>, dc=<domain>, dc=<domain>
o=NetscapeRoot
When you are asked if you want to delete the install.inf file, select the default (Yes).
Typical installation differs slightly depending on whether you are installing on Unix or Windows NT. The following sections outline the different procedures.
Using Typical Installation on Unix
To perform a typical installation on Unix:
Log in as root.
If you have not already done so, download the product binaries file to the installation directory
Unpack the product binaries file using the following command: # gzip -dc <filename>.tar.gz | tar -xvof- where <filename> corresponds to the product binaries that you want to unpack.
Run the setup program. You can find it in the directory where you untarred installation files.
When you are asked what type of installation you would like to perform, select the default, Typical Installation.
For server root, enter a full path to the location where you want to install your server. The location that you enter must be some directory other than the directory from which you are running setup. If the directory that you specify does not exist, setup creates it for you.
For Netscape Server Family, Netscape Server Family Core Components, Netscape Directory Suite, and Administration Services components, select the default (all components).
For hostname, select the default (which is the local host).
For the user and group to run the servers as, enter the identity that you want this server to run as. For more information on the user and groups that you should use when running Netscape servers, see "Decide Which User and Group to Run Netscape Servers As (Unix only)".
For configuration directory, select the default if this directory will host your o=NetscapeRoot tree. Otherwise, enter Yes. You will then be asked for the contact information for the configuration directory. If the server you are currently installing is not the configuration directory, then the configuration directory must exist before you can continue this installation.
For the server that will host your user data, you must decide if this Directory Server will store your enterprise's data. For most cases, you can select the default. However, if this server instance is intended to be only a configuration directory, then you should enter Yes.
For the Directory Server port, select the default (389) unless you already have another application using that port.
For server identifier, enter some unique value (normally the default is sufficient). This value is used as part of the name of the directory in which the Directory Server instance is installed. For example, if your machine's host name is phonebook then this name is the default and selecting it will cause the Directory Server instance to be installed into a directory labeled slapd-phonebook.
For Configuration Directory Administrator ID and password, enter the name and password that you will log in as when you want to authenticate to the console with full privileges.
For a directory suffix, enter a distinguished name meaningful to your enterprise. This string is used to form the name of all your organization's directory entries. Therefore, pick some name that is representative of your organization. It is recommended that you pick a suffix that corresponds to your internet DNS name. For example, if your organization uses the DNS name airius.com, then enter o=airius.com here.
For example, if your organization uses the DNS name airius.com, then enter o=airius.com here.
For Directory Manager DN, enter the distinguished name that you will use when managing the contents of your directory with unlimited privileges (in former releases of the Directory Server, the Directory Manager was known as the root DN). This is the entry that you bind to the directory as when you want access control to be ignored. This distinguished name can be short and does not have to conform to any suffix configured for your directory. It also should not correspond to an actual entry stored in your directory. Examples of possible directory manager DNs are: cn=Directory Manager cn=root uid=admin
For Directory Manager password, enter a value that is at least 8 characters long.
For Administration Domain, enter the domain that you want this server to belong to. The name that you enter should be a unique string that is descriptive of the organization responsible for administering the domain. For information on administration domains, see "Determine the Administration Domain".
For administration port number, enter a value that is not in use. Be sure to record this value.
For the user you want to run the Administration Server as, enter Root. This is the default. For information on why you should run the Administration Server as root, see "Decide Which User and Group to Run Netscape Servers As (Unix only)".
The suffix that you configured.
When you are asked if you want to delete the install.inf file (or installation cache), for security reasons you should select Yes.
Using Typical Installation on Windows NT
To perform a typical installation on Windows NT:
Log in as administrator.
Unzip the product binaries files and run the setup program.
When you are asked what type of installation you would like to perform, select the default, Typical.
For server installation root, enter a full path to the location where you want to install your server. The location that you enter must be some directory other than the directory from which you are running setup. If the directory that you specify does not exist, setup creates it for you.
For Components, select the default (all components). Do not select the NT Synchronization Service component if you are not going to synchronize user and group information between this Windows NT host and your Directory Server. For information on how to install the NT Synchronization Service, see Chapter 5, "Installing and Configuring the Synch Service."
For configuration directory, select the default if this directory will host your o=NetscapeRoot tree. Otherwise, enter the appropriate contact information for the configuration directory. If this Directory Server is not the configuration directory, then the configuration directory must exist and be running before you can continue this installation.
For the directory to store data in, you must decide if this Directory Server instance will store your enterprise's data. For most cases, you can select the default, "Store data in this Directory Server". However, if this server instance is intended to be only a configuration directory, then you should select "Store data in an existing Directory Server."
For server identifier, enter some unique value (normally the default is sufficient). This value is used as part of the name of the directory in which the Directory Server instance is installed. For example, if your machine's hostname is phonebook then this name is the default and selecting it will cause the Directory Server instance to be installed into a directory labeled slapd-phonebook.
For a directory suffix, enter a distinguished name meaningful to your enterprise. This string is used to form the name of all your organization's directory entries. Therefore, pick some name that is representative of your organization. It is recommended that you pick a suffix that corresponds to your Internet DNS name. For example, if your organization uses the DNS name airius.com, then enter o=airius.com here.
For Directory Manager DN, enter the distinguished name that you will use when managing the contents of your directory with unlimited privileges (in former releases of the Directory Server, the Directory Manager was known as the root DN). This is the entry that you bind to the directory as when you want access control to be ignored. This distinguished name can be short and does not have to conform to any suffix configured for your directory. It also should not correspond to an actual entry stored in your directory. Examples of possible directory manager DNs are cn=Directory Manager cn=root uid=admin
At this time, you must populate your database with user entries. 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 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 the Netscape Gateway Customization Guide.
First, if you are migrating from Netscape 3.x Directory Server to 4.x, then all you need to do is complete the migration process. All your SuiteSpot settings will be preserved during the migration, and your 3.x Netscape servers should continue to work flawlessly with your new 4.x Directory Server. For information on migrating Directory Servers to 4.x, see Chapter 6, "Upgrading and Migrating the Directory Server."
If, however, you are installing a brand-new 3.x SuiteSpot server and you want that server to work with a 4.x Directory Server that has never before been used by a 3.x server, then you need to add a few additional entries to your 4.x Directory Server. A template for these entries is available in the following file:
<NSHOME>/slapd-<server ID>/ldif/suitespot3.ldif
This file contains the basic entries and permissions necessary to allow a 3.x SuiteSpot server to work with the 4.x Directory Server. Use the ldapmodify command-line tool to add the contents of this file to your already running 4.x Directory Server. Doing so adds the same directory entries to your 4.x Directory Server as if you had used the "Database Management" | "SuiteSpot Settings" form in the 3.x Directory Server manager.
For information on how to add LDIF to a Directory Server with ldapmodify, see the Netscape Directory Server Administrator's Guide. For details on managing SuiteSpot integration, see the "Managing SuiteSpot Integration" section in chapter 4 of the Netscape Directory Server 3.x Administrator's Guide.
Previous
