Page 1: Installation Guide
Installation Guide Netscape Directory Server Version 6.2 December 2003...
Page 2 Netscape Communications Corporation ("Netscape") and its licensors retain all ownership rights to the software programs offered by Netscape (referred to herein as "Software") and related documentation. Use of the Software and related documentation is governed by the license agreement for the Software and applicable copyright law.
Page 3: Table Of Contents
Contents About This Guide ............. . . 7 Prerequisite Reading .
Page 4 Chapter 3 Computer System Requirements ........33 Summary of Supported Platforms .
Page 5 Setting File Descriptors ............64 Tuning TCP Parameters .
Page 6 After You Upgrade ..............108 Chapter 7 Uninstalling Directory Server .
Page 7: About This Guide
About This Guide Welcome to Netscape Directory Server (Directory Server). This manual provides a high-level overview of design and planning decisions you need to make before installing the Directory Server, and describes the different installation methods that you can use. This preface contains the following sections: •...
Page 8: Conventions Used In This Guide
Conventions Used In This Guide • Directory Server Console—An improved management console that dramatically reduces the effort of setting up and maintaining your directory service. The directory console is part of Netscape Console, the common management framework for Netscape servers. •...
Page 9: Related Information
Related Information All paths specified in this manual are in UNIX format. If you are using a Windows-based Directory Server, you should assume the equivalent file paths whenever UNIX file paths are shown in this guide. Related Information The document set for Directory Server also contains the following guides: •...
Page 10 Related Information Netscape Directory Server Installation Guide • December 2003...
Page 11: Chapter 1 Preparing For A Directory Server Installation
Chapter 1 Preparing for a Directory Server Installation Before you begin installing Netscape Directory Server (Directory Server), you should have an understanding of the various Directory Server components and the design and configuration decisions you need to make. To help you prepare for your Directory Server installation, you should be familiar with the concepts contained in the following sections: •...
Page 12: Configuration Decisions
Configuration Decisions • Netscape Administration Server—Administration Server is a common front-end to all Netscape servers. It receives communications from Netscape Console and passes those communications on to the appropriate Netscape server. Your site will have at least one Administration Server for each server root in which you have installed an Netscape server.
Page 13: Choosing Unique Port Numbers
Configuration Decisions Choosing Unique Port Numbers Port numbers can be any number from 1 to 65535. Keep the following in mind when choosing a port number for your Directory Server: • The standard Directory Server (LDAP) port number is 389. •...
Page 14: Deciding The User And Group For Your Netscape Servers (Unix Only)
Configuration Decisions By default, the server root directory is one of the following: • (on UNIX systems) /usr/netscape/servers • (on Windows systems) c:\netscape\servers Deciding the User and Group for Your Netscape Servers (UNIX only) For security reasons, it is always best to run UNIX-based production servers with normal user privileges.
Page 15: Defining Authentication Entities
Configuration Decisions Defining Authentication Entities As you install Directory Server and Administration Server, you will be asked for various user names, distinguished names (DN), and passwords. This list of login and bind entities will differ depending on the type of installation that you are performing: •...
Page 16: Determining Your Directory Suffix
Configuration Decisions Normally, Administration Server user and password should be identical to the configuration directory administrator ID and password. Determining Your Directory Suffix A directory suffix is the directory entry that represents the first entry in a directory tree. You will need at least one directory suffix for the tree that will contain your enterprise’s data.
Page 17: Determining The Location Of The User Directory
Configuration Decisions Because the configuration directory normally experiences very little traffic, you can allow its server instance to coexist on a machine with another more heavily loaded Directory Server instance. However, for very large sites that are installing a large number of Netscape servers, you may want to dedicate a low-end machine to the configuration directory so as to not hurt the performance of your other production servers.
Page 18: Determining The Administration Domain
Configuration Decisions Between your user directory and your configuration directory, it is your user directory that will receive the overwhelming percentage of the directory traffic. For this reason, you should give the user directory the greatest computing resources. Because the configuration directory should receive very little traffic, it can be installed on a machine with very low-end resources (such as a minimally-equipped Pentium).
Page 19: Installation Process Overview
Installation Process Overview For many installations, you can have just one administration domain. In this case, choose a name that is representative of your organization. For other installations, you may want different domains because of the demands at your site. In the latter case, try to name your administration domains after the organizations that will control the servers in that domain.
Page 20: Migration And Upgrade Process
Installation Process Overview Beyond determining which type of installation process you will use, the process for installing Directory Server is as follows: Plan your directory service. By planning your directory tree in advance, you can design a service that is easy to manage and easy to scale as your organization grows.
Page 21: Installation Privileges
Installation Privileges On Windows, unzip the product binaries. Installation Privileges On UNIX you must install as if you choose to run the server on a port root below 1024, such as the default LDAP ports: 389 and 636 (LDAP over SSL). If you choose port numbers higher than 1024, you can install using any valid UNIX login.
Page 22 Installation Privileges Netscape Directory Server Installation Guide • December 2003...
Page 23: Chapter 2 Using Express And Typical Installation
Chapter 2 Using Express and Typical Installation This chapter describes how to perform basic installation activities. This chapter contains the following sections: • Using Express Installation (page 23) • Using Typical Installation (page 25) Using Express Installation Use express installation if you are installing Directory Server to evaluate or test the product.
Page 24 Using Express Installation where corresponds to the product binaries you want to unpack. filename On a Windows system, unzip the product binaries. Run the program. You can find it in the directory in which you untarred setup or unzipped the binary files. On a UNIX system, issue the following command: ./setup Select “yes”...
Page 25: Using Typical Installation
Using Typical Installation o=NetscapeRoot Do not modify the contents of the directory under the o=NetscapeRoot suffix. Either create data under the first suffix or create a new suffix to be used for this purpose. For details on how to create new suffixes for your Directory Server, see the Netscape Directory Server Administrator’s Guide.
Page 26 Using Typical Installation Next, the program asks you if you agree to the license terms. Press “y” setup to agree with the license terms. When you are asked what you would like to install, press Enter to select the default, Netscape Servers. When you are asked what type of installation you would like to perform, press Enter to select the default, Typical Installation.
Page 27 Using Typical Installation CAUTION Note that the default hostname may be incorrect if the installer cannot locate a DNS name in your system. For example, you might not have a DNS name if your system uses NIS. The hostname must be a fully qualified host and domain name. If the default hostname is not a fully qualified host and domain name, installation will fail.
Page 28 Using Typical Installation 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 (DN) meaningful to your enterprise.
Page 29: Using Typical Installation On Windows
Using Typical Installation For the user you want to run Administration Server as, enter . This is root the default. For information on why you should run Administration Server as root, see “Deciding the User and Group for Your Netscape Servers (UNIX only),” on page 14.
Page 30 Using Typical Installation For configuration directory, select the default if this directory will host your tree. Otherwise, enter the appropriate contact information for o=NetscapeRoot the configuration directory. If this Directory Server instance is not the configuration directory, then the configuration directory must exist and be running before you can continue this installation.
Page 31 Using Typical Installation NOTE Any DN must be entered in the UTF-8 character set encoding. Older encodings such as ISO-8859-1 are not supported. In former releases of 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.
Page 32 Using Typical Installation Netscape Directory Server Installation Guide • December 2003...
Page 33: Chapter 3 Computer System Requirements
Chapter 3 Computer System Requirements Before you can install Netscape Directory Server (Directory Server), you must make sure that the systems on which you plan to install the software meet the minimum hardware and operating system requirements. These requirements are described in detail for each platform in the following sections: •...
Page 34 Summary of Supported Platforms Table 3-1 Supported Platforms (Continued) Memory/RAM 256 MB. However, you should plan from 512 MB to 1 GB of RAM for best performance on large production systems. Storage Space/Hard Disk Approximately 300 MB of disk space for a minimal installation. For production systems, you should plan at least 2 GB to support the product binaries, databases, and log files (log files require 1 GB by default);...
Page 35 Summary of Supported Platforms Table 3-1 Supported Platforms (Continued) Storage Space/Hard Disk Approximately 300 MB of disk space for a minimal installation. For production systems, you should plan at least 2 GB to support the product binaries, databases, and log files (log files require 1 GB by default);...
Page 36: Hardware Requirements
Hardware Requirements Hardware Requirements On all platforms, you will need: • Roughly 200 MB of disk space for a minimal installation. For production systems, you should plan at least 2GB to support the product binaries, databases, and log files (log files require 1 GB by default); 4GB and greater may be required for very large directories.
Page 37: Dsktune Utility
Operating System Requirements dsktune Utility For UNIX platforms, Directory Server provides a utility named that dsktune can help you verify whether you have the appropriate patches installed on your system. The utility also provides useful information and advice on how to tune your kernel parameters for best performance.
Page 38: Verifying Required System Modules
Operating System Requirements Verifying Required System Modules Directory Server is not supported on HP-UX 10 or earlier versions. The minimum system module required is HP-UX 11. Directory Server may be used on a 64 bit HP-UX 11 environment, but will run as a 32 bit process, and is limited to 1 GB of process memory.
Page 39: Tuning The System
Operating System Requirements PHSS_16587: HP aC++ runtime libraries PHKL_20335: boot,Jfs;IO perf;PA8600;3GB data;NFS;bcache PHKL_20174: Allow sam to set maxdsize patch PHCO_21187: Cumulative SAM/ObAM patch • Install the patches listed below; Netscape Console uses the Abstract Window Tool (AWT) kit and requires you to install these patches. PHSS_25290: Xserver cumulative patch PHSS_25091:...
Page 40: Installing Third-Party Utilities
Operating System Requirements • to 512 (the old value was 64). max_thread_proc • to 64 (the old value was 32). maxusers • to 512 (the old value was 75). maxuprc • to 750, a new value which is not based on a formula (the old nproc formula was , which evaluated to 276).
Page 41: Microsoft Windows 2000 Advanced Server
Operating System Requirements Microsoft Windows 2000 Advanced Server If you plan to install Directory Server on a machine running the Windows 2000 Advanced Server operating system (OS), follow the recommendations outlined in these sections: • Configuring a Machine to Run Directory Server •...
Page 42: Installing Windows 2000 Server
Operating System Requirements Installing Windows 2000 Server During the installation of Windows 2000, observe the following: • If there is already an operating system present on the computer, choose to perform a fresh install rather than an upgrade. • Format the drives with NTFS rather than FAT, as NTFS allows access controls to be set on files and directories.
Page 43: Ensuring System Clock Accuracy
Operating System Requirements Before downloading the font, read the files. READMEfirst.txt ReadMe.htm Ensuring System Clock Accuracy To facilitate the correlation of date and time stamps in log files with those of other computer systems, keep your system clock reasonably in sync. As the NET TIME command requires NetBIOS, which will be disabled during post-installation system configuration, either a TCP/IP based NTP client should be installed (such as the shareware program Tardis), or a time radio receiver...
Page 44: Red Hat Linux 7.3 Operating System
Installing Third-Party Utilities In addition to these recommendations, be sure to check the OS vendor’s web site for the latest information pertaining to your OS version: http://www.redhat.com/apps/support/ Verifying Disk Space Requirements Ensure that you have sufficient disk space before downloading the software.
Page 45: Installing System Patches
Operating System Requirements Default glibc - glibc-2.2.5-34 glibc used for certification - glibc-2.2.5-43 Required Filesytem: ext3 ( support enabled) filesystem has been used for the LARGEFILES certification process. Installing System Patches Directory Server has been certified on Red Hat Linux 7.3 with kernel revisions 2.4.18-27.7.x ( ) / glibc version 2.2.5-43 kernel-2.4.18-27.7.x.i686.rpm...
Page 46 Operating System Requirements Table 3-2 Red Hat Linux 7.3 Patch List (Continued) file-3.39-8.7x.i386.rpm losetup-2.11n-12.7.3.i386.rpm fileutils-4.1-10.1.i386.rpm LPRng-3.8.9-4.i386.rpm gaim-0.59.1-0.7.3.i386.rpm mew-2.2-5.7x.i386.rpm gal-0.19.2-3.7x.i386.rpm mew-common-2.2-5.7x.i386.rpm gal-devel-0.19.2-3.7x.i386.rpm mm-1.1.3-11.i386.rpm galeon-1.2.6-0.7.3.i386.rpm mm-devel-1.1.3-11.i386.rpm gcc-2.96-113.i386.rpm modutils-2.4.18-3.7x.i386.rpm gcc-c++-2.96-113.i386.rpm mount-2.11n-12.7.3.i386.rpm gcc-g77-2.96-113.i386.rpm mozilla-1.0.1-2.7.3.i386.rpm gcc-objc-2.96-113.i386.rpm mozilla-chat-1.0.1-2.7.3.i386.rpm gdb-5.2-2.i386.rpm mozilla-devel-1.0.1-2.7.3.i386.rpm ghostscript-6.52-9.4.i386.rpm mozilla-dom-inspector-1.0.1-2.7.3.i386.rpm glibc-2.2.5-43.i686.rpm mozilla-js-debugger-1.0.1-2.7.3.i386.rpm glibc-common-2.2.5-43.i386.rpm mozilla-mail-1.0.1-2.7.3.i386.rpm glibc-devel-2.2.5-43.i386.rpm mozilla-nspr-1.0.1-2.7.3.i386.rpm glibc-kernheaders-2.4-7.16.i386.rpm...
Page 47 Operating System Requirements Table 3-2 Red Hat Linux 7.3 Patch List (Continued) kdeartwork-screensavers-3.0.3-0.7.1.i386.rpm openldap-devel-2.0.27-2.7.3.i386.rpm kdebase-3.0.3-0.7.2.i386.rpm openssh-3.1p1-6.i386.rpm kdebase-devel-3.0.3-0.7.2.i386.rpm openssh-askpass-3.1p1-6.i386.rpm kdegames-3.0.3-0.7.i386.rpm openssh-askpass-gnome-3.1p1-6.i386.rpm kdegames-devel-3.0.3-0.7.i386.rpm openssh-clients-3.1p1-6.i386.rpm kdelibs-3.0.3-0.7.2.i386.rpm openssh-server-3.1p1-6.i386.rpm kdelibs-devel-3.0.3-0.7.2.i386.rpm openssl-0.9.6b-30.7.i686.rpm kdemultimedia-arts-3.0.3-0.7.1.i386.rpm openssl-0.9.6b-32.7.i686.rpm kdemultimedia-devel-3.0.3-0.7.1.i386.rpm openssl-devel-0.9.6b-30.7.i386.rpm kdemultimedia-kfile-3.0.3-0.7.1.i386.rpm openssl-devel-0.9.6b-32.7.i386.rpm kdemultimedia-libs-3.0.3-0.7.1.i386.rpm pam-0.75-46.7.3.i386.rpm kdenetwork-devel-3.0.3-0.7.2.i386.rpm pam-devel-0.75-46.7.3.i386.rpm kdenetwork-libs-3.0.3-0.7.2.i386.rpm perl-Digest-MD5-2.20-1.i386.rpm kdepasswd-3.0.3-0.7.i386.rpm pine-4.44-7.73.0.i386.rpm kdepim-3.0.3-0.7.i386.rpm psmisc-20.2-3.73.i386.rpm kdepim-cellphone-3.0.3-0.7.i386.rpm...
Page 48 Operating System Requirements Table 3-2 Red Hat Linux 7.3 Patch List (Continued) kernel-smp-2.4.18-27.7.x.i686.rpm sendmail-cf-8.11.6-25.73.i386.rpm kfloppy-3.0.3-0.7.i386.rpm sendmail-devel-8.11.6-23.73.i386.rpm khexedit-3.0.3-0.7.i386.rpm sendmail-devel-8.11.6-25.73.i386.rpm kit-3.0.3-0.7.2.i386.rpm shadow-utils-20000902-9.7.i386.rpm kjots-3.0.3-0.7.i386.rpm tar-1.13.25-4.7.1.i386.rpm kljettool-3.0.3-0.7.i386.rpm tetex-1.0.7-47.1.i386.rpm klpq-3.0.3-0.7.i386.rpm tkinter-1.5.2-43.73.i386.rpm klprfax-3.0.3-0.7.i386.rpm ucd-snmp-4.2.5-7.73.0.i386.rpm kmail-3.0.3-0.7.2.i386.rpm ucd-snmp-utils-4.2.5-7.73.0.i386.rpm kmid-3.0.3-0.7.1.i386.rpm up2date-2.8.39-1.7.3.i386.rpm kmidi-3.0.3-0.7.1.i386.rpm up2date-gnome-2.8.39-1.7.3.i386.rpm kmix-3.0.3-0.7.1.i386.rpm util-linux-2.11n-12.7.3.i386.rpm knewsticker-3.0.3-0.7.2.i386.rpm vim-common-6.1-18.7x.2.i386.rpm knode-3.0.3-0.7.2.i386.rpm vim-enhanced-6.1-18.7x.2.i386.rpm knotes-3.0.3-0.7.i386.rpm vim-minimal-6.1-18.7x.2.i386.rpm koncd-3.0.3-0.7.1.i386.rpm...
Page 49: Tuning The System
Operating System Requirements Tuning the System This section contains some basic system tuning information. Keep in mind that changing any of the following kernel tuning parameters requires a system reboot. • NFS Tuning—This tuning is recommended if you are using Directory Server to write to NFS mounted drives.
Page 50: Red Hat Linux Advanced Server 2.1 Operating System
Installing Third-Party Utilities In addition to these recommendations, be sure to check the OS vendor’s web site for the latest information pertaining to your OS version: http://www.redhat.com/apps/support/ Verifying Disk Space Requirements Ensure that you have sufficient disk space before downloading the software.
Page 51: Installing System Patches
Chapter 3 Computer System Requirements...
Page 52 Operating System Requirements Table 3-3 Red Hat Linux Advanced Server 2.1 Patch List (Continued) iputils-20001110-6.AS21.2.i386.rpm sendmail-8.11.6-26.72.i386.rpm kde-i18n-Japanese-3.0.3-2.noarch.rpm sendmail-cf-8.11.6-24.72.i386.rpm kdebase-2.2.2-6.i386.rpm sendmail-cf-8.11.6-26.72.i386.rpm kdelibs-2.2.2-6.i386.rpm shadow-utils-20000902-9.7.i386.rpm kdelibs-sound-2.2.2-6.i386.rpm tar-1.13.25-4.AS21.0.i386.rpm kdenetwork-2.2.2-3.i386.rpm tkinter-1.5.2-43.72.i386.rpm kdepim-2.2.2-4.i386.rpm unzip-5.50-2.i386.rpm kdeutils-2.2.2-2.i386.rpm util-linux-2.11f-20.i386.rpm kernel-2.4.9-e.16.i686.rpm vim-common-6.0-7.15.i386.rpm kernel-headers-2.4.9-e.16.i386.rpm vim-minimal-6.0-7.15.i386.rpm kernel-smp-2.4.9-e.16.i686.rpm vnc-3.3.3r2-18.6.i386.rpm krb5-libs-1.2.2-24.i386.rpm vnc-server-3.3.3r2-18.6.i386.rpm libpcap-0.6.2-12.2.1AS.2.i386.rpm wget-1.8.2-4.72.i386.rpm libpng-1.0.14-0.7x.4.i386.rpm x86-compat-libs-7.2-1.i386.rpm libstdc++-2.96-116.7.2.i386.rpm...
Page 53: Tuning The System
Operating System Requirements Tuning the System This section contains some basic system tuning information. Keep in mind that changing any of the following kernel tuning parameters requires a system reboot. • NFS Tuning—This tuning is recommended if you are using Directory Server to write to NFS mounted drives.
Page 54: Sun Solaris 8 Operating System
Operating System Requirements Sun Solaris 8 Operating System If you plan to install Directory Server on a machine running the Solaris 8 operating system (OS), follow the recommendations outlined in these sections: • Verifying Disk Space Requirements • Verifying Required System Modules •...
Page 55: Installing Patches
Operating System Requirements Installing Patches You must use Solaris 8 with the Sun recommended patches. The Sun recommended patch clusters can be obtained from your Solaris support representative, or from the site. http://sunsolve.sun.com Solaris patches are generally identified by two numbers, for example 108434-10. The first number (108434) identifies the patch itself.
Page 56 Operating System Requirements Table 3-4 Solaris 8 Patch List (Continued) 108949-07: CDE 1.4: libDtHelp/libDtSvc patch 108968-08: SunOS 5.8: vol/vold/rmmount/dev_pcmem.so.1 patch 108974-25: SunOS 5.8: dada, uata, dad, sd and scsi drivers patch 108975-06: SunOS 5.8: /usr/bin/rmformat and /usr/sbin/format patch 108977-01: SunOS 5.8: libsmedia patch 108981-10: SunOS 5.8: /kernel/drv/hme and /kernel/drv/sparcv9/hme patch 108985-03:...
Page 57 Operating System Requirements Table 3-4 Solaris 8 Patch List (Continued) 109805-15: SunOS 5.8: /usr/lib/security/pam_krb5.so.1 patch 109862-03: X11 6.4.1 Font Server patch 109882-06: SunOS 5.8: eri header files patch 109885-09: SunOS 5.8: glm patch 109888-20: SunOS 5.8: platform drivers patch 109898-05: SunOS 5.8: /kernel/drv/arp patch 109951-01: SunOS 5.8: jserver buffer overflow...
Page 58 Operating System Requirements Table 3-4 Solaris 8 Patch List (Continued) 110916-03: SunOS 5.8: sort patch 110934-11: SunOS 5.8: pkgtrans, pkgadd, pkgchk and libpkg.a patch 110939-01: SunOS 5.8: /usr/lib/acct/closewtmp patch 110943-01: SunOS 5.8: /usr/bin/tcsh patch 110945-07: SunOS 5.8: /usr/sbin/syslogd patch 110951-03: SunOS 5.8: /usr/sbin/tar and /usr/sbin/static/tar patch 110957-02: SunOS 5.8: /usr/bin/mailx patch...
Page 59: Tuning The System
Operating System Requirements Table 3-4 Solaris 8 Patch List (Continued) 111879-01: SunOS 5.8: Solaris Product Registry patch SUNWwsr 111881-03: SunOS 5.8: /usr/kernel/strmod/telmod patch 111883-14: SunOS 5.8: Sun GigaSwift Ethernet 1.0 driver patch 111958-02: SunOS 5.8: /usr/lib/nfs/statd patch 112138-01: SunOS 5.8:: usr/bin/domainname patch 112218-01: SunOS 5.8:: pam_ldap.so.1 patch 112237-07:...
Page 60: Setting File Descriptors
Operating System Requirements Setting File Descriptors The system-wide maximum file descriptor table size setting will limit the number of concurrent connections that can be established to Directory Server. The governing parameter, , is set in the file. By rlim_fd_max /etc/system default, if this parameter is not present, the maximum is 1024.
Page 61: Sun Solaris 9 Operating System
Operating System Requirements ndd -set /dev/tcp tcp_conn_req_max_q0 1024 ndd -set /dev/tcp tcp_conn_req_max_q 1024 specifies the interval in seconds between tcp_keepalive_interval keepalive packets sent by Solaris for each open TCP connection. This can be used to remove connections to clients that have become disconnected from the network.
Page 62: Verifying Disk Space Requirements
Operating System Requirements http://sunsolve.sun.com Verifying Disk Space Requirements Ensure that you have sufficient disk space before downloading the Directory Server software. Current working directory: 120 MB Partition containing : 2 GB /usr/netscape Verifying Required System Modules Directory Server requires the use of a SPARC v8+ or an UltraSPARC (SPARC v9) processor, as these processors include support for high performance and multiprocessor systems.
Page 63 Operating System Requirements Table 3-5 Solaris 9 Patch List 112233-04: SunOS 5.9: Kernel Patch 112601-04: SunOS 5.9: PGX32 Graphics 112764-04: SunOS 5.9: Sun Quad FastEthernet qfe driver 112785-12: X11 6.6.1: Xsun patch 112808-03: OpenWindows 3.6.3: Tooltalk patch 112817-06: SunOS 5.9: Sun GigaSwift Ethernet 1.0 driver patch 112834-02: SunOS 5.9: patch scsi 112875-01:...
Page 64: Tuning The System
Operating System Requirements Table 3-5 Solaris 9 Patch List (Continued) 113923-02: X11 6.6.1: security font server patch 113993-01: SunOS 5.9: mkfs Patch 114135-01: SunOS 5.9: at utility Patch Tuning the System Basic Solaris tuning guidelines are available from several books, including Sun Performance and Tuning: Java and the Internet (ISBN 0-13-095249-4).
Page 65: Tuning Tcp Parameters
Operating System Requirements Tuning TCP Parameters By default, the TCP/IP implementation in a Solaris kernel is not correctly tuned for Internet or Intranet services. The following tuning parameters should be /dev/tcp inspected and, if necessary, changed to fit the network topology of the installation environment.
Page 66 Operating System Requirements The DNS resolver is typically set by the file . However, also /etc/resolv.conf check the file , and on Solaris , to ensure /etc/nsswitch.conf /etc/netconfig that the DNS resolver will be used for name resolution. If you are not already using NIS, you will also need to set the default NIS domain name.
Page 67: Chapter 4 Silent Installation And Instance Creation
Chapter 4 Silent Installation and Instance Creation Silent installation allows you to use a file to predefine all the answers that you would normally supply to the program interactively; this provides you with setup the ability to script the installation of multiple instances of Netscape Directory Server (Directory Server).
Page 68: Preparing Silent Installation Files
Using Silent Installation Create a new directory: # mkdir ds # cd ds If you have not already done so, download the product binaries file to the installation directory. On Windows machines, unzip the product binaries. On UNIX, unpack the product binaries file using the following command: # gunzip -dc filename.tar.gz | tar -xvof- where...
Page 69 Using Silent Installation You will have to make some modifications to this file before you use it. Specifically, ensure that you have done the following: • —Set this directive to a value that is appropriate for the FullMachineName machine on which Directory Server will be installed, if it’s not to be the local machine.
Page 70: Sample File For Typical Installation
Using Silent Installation You can find a definition of the individual installation directives in “Specifying Silent Installation Directives” on page 73. NOTE file provided with the Directory Server is merely a silent.inf template, an example of how to write your own. For the file to work, many of the parameters (host name, ports, paths, and so on) in the file must be replaced with appropriate values.
Page 71: Sample File For Using An Existing Configuration Directory
Using Silent Installation [admin] SysUser= root Port= 23611 ServerIpAddress= 111.11.11.11 ServerAdminID= admin ServerAdminPwd= admin Components= admin,admin-client [base] Components= base,base-client,base-jre [nsperl] Components= nsperl561 [perldap] Components= perldap14 Sample File for Using an Existing Configuration Directory The following is an example of the file that is generated when you install.inf perform a typical installation and you choose to use an existing Directory Server...
Page 72: Sample File For Installing The Standalone Netscape Console
Using Silent Installation AddSampleEntries= No InstallLdifFile= suggest AddOrgEntries= Yes DisableSchemaChecking= No RootDNPwd= admin123 Components= slapd,slapd-client [admin] SysUser= root Port= 33646 ServerIpAddress= 111.11.11.11 ServerAdminID= admin ServerAdminPwd= admin Components= admin,admin-client [base] Components= base,base-client,base-jre [nsperl] Components= nsperl561 [perldap] Components= perldap14 Sample File for Installing the Standalone Netscape Console The following is an example of the file that is generated when you install.inf...
Page 73: Specifying Silent Installation Directives
Using Silent Installation Specifying Silent Installation Directives This section describes the basic format of the file used for silent installation. It then describes the directives that are available for each area of the silent installation file. • Silent Installation File Format •...
Page 74: [General] Installation Directives
Using Silent Installation [General] Installation Directives [General] installation directives specify information of global interest to the Netscape servers installed at your site. That is, the information you provide here will be common to all your Netscape servers. The [General] installation directives are listed in Table 4-1. Table 4-1 [General] Installation Directives Directive...
Page 75: [Slapd] Installation Directives
Using Silent Installation Table 4-1 [General] Installation Directives (Continued) Directive Description Specifies the LDAP URL that is used to connect to your ConfigDirectoryLdapURL configuration directory. LDAP URLs are described in the Netscape Directory Server Administrator’s Guide. This directive is required. Specifies the administration domain under which this AdminDomain server will be registered.
Page 76 Using Silent Installation Table 4-2 Required and Optional [slapd] Installation Directives Required Directive Description Specifies the slapd components to be installed. The Components components are: • slapd—Install Directory Server. • slapd-client—Install Directory Server Console. This directive is required. It is recommended that you always install both components any time you install the Directory Server.
Page 77: [Admin] Installation Directives
Using Silent Installation Table 4-2 Required and Optional [slapd] Installation Directives (Continued) Required Directive Description If set to Yes, this directive causes the new Directory AddOrgEntries Server instance to be created with a suggested directory structure and access control. If this directive is used and InstallLdifFile is also used, then this directive has no effect.
Page 78: [Base] Installation Directives
Using Silent Installation Table 4-3 [admin] Installation Directives (Continued) Directive Description Specifies the port that the Administration Server will Port use. Note that the Administration Server’s host name is given by the FullMachineName directive. For more information on FullMachineName, see Table 4-1. Specifies the administration ID that can be used to access ServerAdminID this Administration Server if the configuration...
Page 79: [Nsperl] Installation Directives
Using Silent Instance Creation [nsperl] Installation Directives There is only one [nsperl] installation directive and it allows you to determine whether nsPerl is to be installed. Table 4-5 lists the directive. [nsperl] Installation Directive Table 4-5 Directive Description Specifies whether nsPerl that is bundled with Directory Components Server is to be installed.
Page 80 Using Silent Instance Creation Because all instances of Directory Server under a server root use the same Administration Server, the instance creation process does not install Administration Server binaries; you cannot create two instances of Administration Server in one server root. Having multiple instances in a single server root is useful for testing and for when one host is used for multiple purposes.
Page 81 Using Silent Instance Creation SlapdConfigForMC= No UseExistingMC= Yes UseExistingUG= No SecurityOn= No UseReplication= No SetupSupplier= No SetupConsumer= No AddSampleEntries= No InstallLdifFile= suggest AddOrgEntries= Yes DisableSchemaChecking= No Chapter 4 Silent Installation and Instance Creation...
Page 82 Using Silent Instance Creation Netscape Directory Server Installation Guide • December 2003...
Page 83: Chapter 5 Post Installation
Chapter 5 Post Installation This chapter describes the post-installation procedures for launching the online help and populating the directory tree. This chapter has the following sections: • Launching the Help System (page 83) • Populating the Directory Tree (page 84) Launching the Help System The help system for Directory Server is dependent upon Netscape Administration Server.
Page 84: Populating The Directory Tree
Populating the Directory Tree Restart Administration Server. You can now launch the online help by clicking any of the Help buttons in the Directory Server Console. Proxy authorized on Administration Server. If you use proxies for your HTTP connections on the client machine running Directory Server Console, you need to do one of the following: •...
Page 85 Populating the Directory Tree • Start your Directory Server with an empty database and import data over LDAP—This method requires you to populate your directory using an LDAP client such as Directory Server Gateway or the ldapmodify command-line utility. Use this method if you have just a few entries to add at a time.
Page 86 Populating the Directory Tree Netscape Directory Server Installation Guide • December 2003...
Page 87: Chapter 6 Migrating And Upgrading From Previous Versions
Chapter 6 Migrating and Upgrading From Previous Versions If you have a previous installation of Directory Server, depending on it’s version, you can migrate or upgrade to Netscape Directory Server 6.x. Migration refers to the process of migrating Directory Server 4.x or 5.x files to Directory Server 6.x.
Page 88: Migration Prerequisites
Migration Prerequisites The migration script performs the following tasks in sequence: • Checks the schema configuration files and notifies you of any changes between the standard configuration files and the ones present on your system; see • Creates a database for each suffix stored in the legacy Directory Server. (In Directory Server 5.x and 6.x you can have multiple databases, but just one suffix per database).
Page 89 Migration Prerequisites • Do not install the new Directory Server on top of an existing Directory Server installation. Install your new Directory Server in a separate directory. Migrate your legacy directory data into your new directory and when you are satisfied with the result of the migration, remove your legacy Directory Server.
Page 90: Identifying Custom Schema
Migration Prerequisites • Windows only. If you are migrating a Directory Server 5.x multi master replicated (MMR) environment to Directory Server 6.2, before you run the migration script, export all exports from the old server’s backend databases using the option. db2ldif -r •...
Page 91: Migration Procedure
Migration Procedure 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.
Page 92: Migrating A Standalone Server
Migration Procedure This section contains the following information: • Migrating a Standalone Server • Migrating a 4.x Replicated Site • Migrating a 5.x Replicated Site • Migrating a 5.x Multi-Master Deployment • Managing Console Fail Over Migrating a Standalone Server Once you have backed up your critical configuration information, do the following to migrate a server: Stop your legacy Directory Server.
Page 93 Migration Procedure is the Directory Server 6.x user DN with root permissions, such as rootDN Directory Manager is the password for in Directory Server 6.x. password Directory Manager port is the LDAP port number assigned to Directory Server 6.x. is the path to the installation directory of the legacy Directory oldInstancePath Server (for example, /usr/netscape/server4/slapd-serverID...
Page 94 Migration Procedure oldHome:/export/home/jdoe/50-latest/slapd-bart, oldConfDir: /export/home/jdoe/50-latest/slapd-bart/config/, ldif_rep: /export/home/jdoe/50-latest/slapd-bart/config//ldif/, rootDN: cn=directory manager, Port: 11440, Newname: bart Shutdown the legacy Directory Server instance: /usr/netscape/servers/ds50/slapd-bart Shutting down server slapd-bart ..Name of the old LDAP server: bart.netscape.com Name of the new LDAP server: bart.netscape.com 6.0 localuser: jdoe, uid: 9871, gid: 10 5.x localuser: jdoe, uid: 9871, gid: 10 Backup /export/home/jdoe/61-latest/slapd-bart/config on...
Page 95 Migration Procedure Param: nsslapd-timelimit values To migrate: 3600 Param: nsslapd-timelimit new current values: 3600 Param: nsconcurrentbindlimit values To migrate: 10 Param: nsconcurrentbindlimit new current values: 10 Param: nsbindconnectionslimit values To migrate: 3 Param: nsbindconnectionslimit new current values: 3 Param: nsconnectionlife values To migrate: 0 Param: nsconnectionlife new current values: 0 Param: nsbindretrylimit values To migrate: 3 Param: nsbindretrylimit new current values: 3...
Page 96 Migration Procedure Existing data will be exported under /export/home/jdoe/61-latest/slapd-bart/db_backup/backend1.ldif Continue Yes/No [No] ? y Now baking up database backend1 in /export/home/jdoe/61-latest/slapd-bart/db_backup/backend1.ldif Shutting down server slapd-bart . . . ldiffile: /export/home/jdoe/61-latest/slapd-bart/db_backup/backend1.ldif [12/Jun/2002:10:32:05 -0700] - export backend1: Processed 3 entries (100%). [12/Jun/2002:10:32:05 -0700] - Waiting for 4 database threads to stop [12/Jun/2002:10:32:07 -0700] - All database threads now stopped try to reconnect to search cn=backend2,cn=ldbm database,cn=plugins,cn=config *** LDBM_BACKEND_INSTANCE - cn=backend2,cn=ldbm database,cn=plugins,cn=config...
Page 97 Migration Procedure *** MAPPING_TREE - cn="dc=backend1,dc=com",cn=mapping tree,cn=config already exists *** Migration will not add the suffix *** MAPPING_TREE - cn="dc=backend2,dc=com",cn=mapping tree,cn=config already exists *** Migration will not add the suffix MAPPING_TREE - Add successfull: cn="dc=backend3,dc=com",cn=mapping tree,cn=config *** MAPPING_TREE - cn="dc=netscape,dc=com",cn=mapping tree,cn=config already exists *** Migration will not add the suffix -------------------------------------------------------------------------...
Page 98 Migration Procedure ldiffile: /export/home/jdoe/50-latest/slapd-bart/config//ldif/backend2.ldif [12/Jun/2002:10:33:29 -0700] - export backend2: Processed 3 entries (100%). [12/Jun/2002:10:33:29 -0700] - Waiting for 1 database threads to stop [12/Jun/2002:10:33:30 -0700] - All database threads now stopped ldiffile: /export/home/jdoe/50-latest/slapd-bart/config//ldif/backend3.ldif [12/Jun/2002:10:33:32 -0700] - export backend3: Processed 2 entries (100%) [12/Jun/2002:10:33:32 -0700] - Waiting for 1 database threads to stop [12/Jun/2002:10:33:33 -0700] - All database threads now stopped Done.
Page 99: Migrating A 4.X Replicated Site
Migration Procedure [12/Jun/2002:10:33:51 -0700] - import backend3: Finished scanning file "/export/home/jdoe/50-latest/slapd-bart/config//ldif/backend3.ldif" (2 entries) [12/Jun/2002:10:33:51 -0700] - import backend3: Workers finished; cleaning up... [12/Jun/2002:10:33:54 -0700] - import backend3: Workers cleaned up. [12/Jun/2002:10:33:54 -0700] - import backend3: Cleaning up producer thread... [12/Jun/2002:10:33:54 -0700] - import backend3: Indexing complete. Post-processing...
Page 100: Migrating A Replicated 4.X Site - Approach 1
Migration Procedure • Migrating a Replicated 4.x Site - Approach 1 • Migrating a Replicated 4.x Site - Approach 2 Migrating a Replicated 4.x Site - Approach 1 Given the constraints, an approach to migrating a replication topology of 4.x servers is to: Install the 6.x Directory Server and configure it both: As a read-write replica, the role the server will fulfill once the migration...
Page 101: Migrating A Replicated 4.X Site - Approach 2
Migration Procedure To migrate this topology using Approach 1, follow these steps: Install Directory Server 6.x on a new server, ServerD. Configure ServerD for the role it will fulfill in the migrated replication topology, that is as a read-write replica that logs changes. This procedure is explained in Chapter 8, “Managing Replication”...
Page 102 Migration Procedure Migrate consumers one at a time. After each migration, recreate migration agreements and re-initialize the migrated consumers. To better understand Approach 2, consider a fairly simple replication topology: • One supplier server, ServerA. • Two consumer servers, ServerB and ServerC. •...
Page 103: Migrating A 5.X Replicated Site
Migration Procedure Migrating a 5.x Replicated Site If you are upgrading from Directory Server 5.x to Directory Server 6.x, your replication configuration is automatically migrated when you run the script. migrateInstance6 To migrate a 5.x replicated site: Stop your Directory Server 5.x. Install Directory Server 6.x.
Page 104: Master Migration
Migration Procedure Migrate the first master; see section “Master Migration” on page 104. Verify that writes and changes are being replicated through the servers. Migrate the second master; see section “Master Migration” on page 104. Verify that writes and changes are being replicated through the servers. Migrate the hubs (if any);...
Page 105: Consumer Migration
Migration Procedure Install Directory Server 6.x, registering against the first master’s configuration instance. Run the migration script following the instructions in “Migrating a Standalone Server” on page 92. Once your hub is migrated, test replication and make sure that it is working correctly.
Page 106: Upgrading From Directory Server 6.X Versions
Upgrading From Directory Server 6.x Versions serverRoot/shared/config/dbswitch.conf:directory default ldap://configHostname:configPort/o%3DNetscapeRoot serverRoot/slapd-serverID/config/dse.ldif:nsslapd-pluginarg0: ldap://configHostname:configPort/o%3DnetscapeRoot Turn off the pass through authentication (PTA) plug-in on Server2 by editing its f file. dse.ldi In a text editor, open this file: serverRoot/slapd-serverID/config/dse.ldif Locate the entry for the PTA plug-in: dn: cn=Pass Through Authentication,cn=plugins,cn=config Change nsslapd-pluginEnabled: on...
Page 107: Upgrading
Upgrading From Directory Server 6.x Versions Upgrading The steps below show how to perform an upgrade using the Typical mode of installation on UNIX: On your Directory Server 6.0x or 6.1x host machine, log in as root superuser ( Stop the server. # serverRoot/slapd-serverID/stop-server Create a new directory, for example: # mkdir ds62...
Page 108: After You Upgrade
Upgrading From Directory Server 6.x Versions When prompted to enter the server root (or the installation directory), enter the full path to the location where your Directory Server 6.0x or 6.1x is installed. By default, the program provides the following path: setup /usr/netscape/servers If your 6.0x or 6.1x Directory Server is installed in a different path, be sure to...
Page 109: Chapter 7 Uninstalling Directory Server
Chapter 7 Uninstalling Directory Server You may need to remove an instance of Netscape Directory Server (Directory Server) or uninstall the entire server altogether. The Directory Server provides a utility that enables you to uninstall the software as a whole or to remove selected components.
Page 110: Uninstalling Directory Server
Uninstalling Directory Server From the Object menu, select Stop; you can also right-click to choose this option from the pop-up menu. When the server has stopped, from the Object menu, choose Remove Server. You can also right-click to choose this option from the pop-up menu. When prompted, confirm that you want to remove the server instance.
Page 111: Uninstalling Directory Server On Windows Systems
Uninstalling Directory Server Select the default, , to remove all components of Directory Server. Alternately, you may choose to remove individual components by selecting them from the list that appears on the screen: Administration Services Netscape Directory Suite Server Core Components nsPerl PerLDAP When prompted, enter the administrator ID and password for the...
Page 112: Using Windows Add/Remove Programs Utility
Uninstalling Directory Server Locate and double-click the uninstallation utility, uninst.exe The Netscape Uninstall window appears, showing a list of components: Administration Services Netscape Directory Suite Server Core Components nsPerl PerLDAP Select the components you want to remove and click Uninstall. To remove specific subcomponents, select the component and click Sub Components.
Page 113 Uninstalling Directory Server Locate and select the entry for Netscape Directory Server. The entry is of the form version_number Netscape Server Products server_root, where version_number is your Directory Server’s version number and server_root is your Directory Server’s installation directory. Click Add/Remove. The Netscape Uninstall window appears, showing a list of components: Administration Services Netscape Directory Suite...
Page 114 Uninstalling Directory Server Netscape Directory Server Installation Guide • December 2003...
Page 115: Chapter 8 Troubleshooting
Chapter 8 Troubleshooting This chapter describes the most common installation problems and how to solve them. It also provides some tips on checking patch levels and kernel parameter settings for your system. This chapter has the following sections: • Running dsktune (page 115) •...
Page 116 Running dsktune The following is an example of output that generates. Note that dsktune does not itself make any changes to the system. dsktune Netscape Directory Server system tuning analysis version 15-MAY-2003. NOTICE : System is usparc-SUNW,Ultra-5_10-solaris5.8_s28s_u7wos_08a (1 processor). ERROR : Patch 108528-18 is present, but 108528-19 (Feb/21/2003: SunOS 5.8: kernel update patch) is a more recent version.
Page 117 Running dsktune ERROR : Patch 110934-10 is present, but 110934-11 (Feb/20/2003: SunOS 5.8: pkgtrans, pkgadd, pkgchk and libpkg.a patch) is a more recent version. ERROR : Patch 111874-05 is present, but 111874-06 (Jan/23/2003: SunOS 5.8: usr/bin/mail patch) is a more recent version. ERROR : Patch 111879-01 (Aug/27/2001: SunOS 5.8: Solaris Product Registry patch SUNWwsr) is required but not installed.
Page 118 Running dsktune NOTICE : The NDD tcp_rexmit_interval_initial is currently set to 3000 milliseconds (3 seconds). This may cause packet loss for clients on Solaris 2.5.1 due to a bug in that version of Solaris. If the clients are not using Solaris 2.5.1, no problems should occur. NOTICE : If the directory service is intended only for LAN or private high-speed WAN environment, this interval can be reduced by adding to /etc/init.d/inetinit:...
Page 119: Common Installation Problems
Common Installation Problems WARNING: There are only 256 file descriptors (soft limit) available, which limit the number of simultaneous connections. Additional file descriptors, up to 1024 (hard limit), are available by issuing 'ulimit' ('limit' for tcsh) command with proper arguments. ulimit -n 4096 ERROR : The above errors MUST be corrected before proceeding.
Page 120 (RPM) be installed when compat-libstdc++-6.2 running the server on Redhat 7.x and Advanced Server. The RPM may or may not be installed depending on the options that were chosen when the operating system was installed. If the RPM is not installed, you will get an error similar to the one shown below.
Page 121 Common Installation Problems [18/Jun/2002:10:56:39] failure ( 4322): Configuration initialization failed: Error running init function load-modules: dlopen of /export/dstest/bin/https/lib/libNSServletPlugin.so failed (libstdc++-libc6.1-1.so.2: cannot open shared object file: No such file or directory) For more information on RPM, check the JRE’s release notes at this URL: http://java.sun.com/j2se/1.4/install-linux.html I have forgotten the Directory manager DN and password.
Page 122 Common Installation Problems , is stored in the system TEMP directory. On UNIX, this directory is uninst.log usually . On Windows, check the system properties to see the /tmp /var/tmp value assigned to the TEMP environment variable (alternatively, you can open a command window and type echo %TEMP% Netscape Directory Server Installation Guide •...
Page 123: Glossary
Glossary access control instruction See ACI. ACI Access Control Instruction. An instruction that grants or denies permissions to entries in the directory. access control list See ACL. ACL Access control list. The mechanism for controlling access to your directory. access rights In the context of access control, specify the level of access granted or denied.
Page 124 attribute Holds descriptive information about an entry. Attributes have a label and a value. Each attribute also follows a standard syntax for the type of information that can be stored as the attribute value. attribute list A list of required and optional attributes for a given entry type or object class.
Page 125 browser Software, such as Netscape Navigator, used to request and view World Wide Web material stored as HTML files. The browser uses the HTTP protocol to communicate with the host server. browsing index Otherwise known as the virtual view index, speeds up the display of entries in the Directory Server Console.
Page 126 ciphertext Encrypted information that cannot be read by anyone without the proper key to decrypt the information. CIR See consumer-initiated replication. class definition Specifies the information needed to create an instance of a particular object and determines how the object works in relation to other objects in the directory.
Page 127 daemon A background process on a Unix machine that is responsible for a particular system task. Daemon processes do not need human intervention to continue functioning. DAP Directory Access Protocol. The ISO X.500 standard protocol that provides client access to the directory. Data Master The server that is the master source of a particular piece of data.
Page 128 DNS Domain Name System. The system used by machines on a network to associate standard IP addresses (such as 198.93.93.10) with hostnames (such as ). Machines normally get the IP address for a hostname from www.example.com a DNS server, or they look it up in tables maintained on their systems. DNS alias A DNS alias is a hostname that the DNS server knows points to a different host—specifically a DNS CNAME record.
Page 129 general access When granted, indicates that all authenticated users can access directory information. hostname A name for a machine in the form machine.domain.dom, which is translated into an IP address. For example, is the machine www.example.com in the subdomain domain. example HTML Hypertext Markup Language.
Page 130 ISO International Standards Organization knowledge reference Pointers to directory information stored in different databases. LDAP Lightweight Directory Access Protocol. Directory service protocol designed to run over TCP/IP and across multiple platforms. LDAPv3 Version 3 of the LDAP protocol, upon which Directory Server bases its schema format LDAP client Software used to request and view LDAP entries from an LDAP Directory Server.
Page 131 management information base See MIB. mapping tree A data structure that associates the names of suffixes (subtrees) with databases. master agent See SNMP master agent. matching rule Provides guidelines for how the server compares strings during a search operation. In an international search, the matching rule tells the server what collation order and operator to use.
Page 132 name collisions Multiple entries with the same distinguished name. nested role Allow you to create roles that contain other roles. network management application Network Management Station component that graphically displays information about SNMP managed devices (which device is up or down, which and how many error messages were received, etc.). network management station See NMS.
Page 133 password file A file on Unix machines that stores Unix user login names, passwords, and user ID numbers. It is also known as , because of /etc/passwd where it is kept. password policy A set of rules that govern how passwords are used in a given directory.
Page 134 RAM Random access memory. The physical semiconductor-based memory in a computer. Information stored in RAM is lost when the computer is shut down. rc.local A file on Unix machines that describes programs that are run when the machine starts. It is also called because of its location.
Page 135 role An entry grouping mechanism. Each role has members, which are the entries that possess the role. role-based attributes Attributes that appear on an entry because it possesses a particular role within an associated CoS template. root The most privileged user available on Unix machines. The root user has complete access privileges to all files on the machine.
Page 136 service A background process on a Windows NT machine that is responsible for a particular system task. Service processes do not need human intervention to continue functioning. SIE Server Instance Entry, the ID assigned to an instance of Directory Server during installation.
Page 137 suffix The name of the entry at the top of the directory tree, below which data is stored. Multiple suffixes are possible within the same directory. Each database only has one suffix. superuser The most privileged user available on Unix machines (also called root).
Page 138 uid A unique number associated with each user on a Unix system. URL Uniform Resource Locator. The addressing system used by the server and the client to request documents. It is often called a location. The format of a URL is .
Page 139: Index
Index dsktune utility 37, 55, 62, 115 administration domain, defined 18 administration port number 28 administration server 12 administration server user 15 authentication entities 15 express install defined 19 using 23 configuration decisions 12 configuration directory administrator 15 fonts, in this book 8 configuration directory, defined 16 conventions, in this book 8 creating instances under the same server root 80...
Page 140 install.inf 68 operating systems 33 installation components 11 configuration decisions 12 preparing for 11 process overview 19 new installations 19 port numbers requirements 33 selecting 13 installation directory, default 14 troubleshooting 120 preparing for installation 11 PrePreInstall field 37 prerequisites migration 88 LDAP Data Interchange Format (LDIF) creating databases using 84...
Page 141 perldap 79 slapd 75 silent install directives general 74 silent install files 68 silent install, defined 19 silent install, examples 69 typical install 70 silent install, using 67 styles, in this book 8 supported platforms 33 terms, in this book 8, 123–138 typical install, defined 19 typical install, using on NT 29...
Page 142 Netscape Directory Server Installation Guide • December 2003...

Netscape DIRECTORY SERVER 6.2 Installation Manual

About this Guide

Chapter 1 Preparing for a Directory Server Installation

Chapter 2 Using Express and Typical Installation

Chapter 3 Computer System Requirements

Chapter 4 Silent Installation and Instance Creation

Chapter 5 Post Installation

Chapter 6 Migrating and Upgrading from Previous Versions

Chapter 7 Uninstalling Directory Server

Chapter 8 Troubleshooting

Glossary

Index

Quick Links

Installation Guide

Need help?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Netscape NETSCAPE DIRECTORY SERVER 6.2

Summary of Contents for Netscape NETSCAPE DIRECTORY SERVER 6.2

Table of Contents