ITDS 5.2 installation checklist: 1. Verify that the hardware and operating system meet minimum requirements. See “System and software requirements” on page 99. 2. Obtain products including the latest relevant Fixpacks. 3. Operating system configuration and tuning. 4. Basic product installation. See “Installing the server” on page 102. 5. Add Administrator DN and password. See “Configuring the Administrator DN and password” on page 106. 6. Configure database. See “Configuring the database” on page 108. 7. Add suffix. See “Adding a suffix” on page 115. 8. Tune DB2. See “DB2 tuning” on page 491. 9. Tune slapd parameters in ibmslapd.conf. See “Additional slapd and ibmslapd settings” on page 488. 10. Schema customization. See “Modifying the schema” on page 292. 11. Configure ITDS. a. TCP/IP Ports ITDS uses. b. Password encryption. See “Password encryption” on page 451 c. Password policy enforcement. See “Password policy enforcement” on page 437. d. SSL/TLS, Kerberos, and Digest-MD5. See “SSL/TLS support” on page 455. e. Log locations and settings. See “Enabling and disabling the change log” on page 118. 12. Add data.

Note: The following installation instructions do not cover migration scenarios. For information on how to migrate previous versions of the Directory Server to ITDS 5.2, please refer to the IBM Tivoli Directory Server Installation and Configuration Guide version 5.2, SC32-1338.

Tip: A simple way to create the type of user account that ITDS requires on a Microsoft Windows 2000 Server is with the following two commands. This example uses a username of ldapdb2 and a password of somepassword. Enter these two commands at a Microsoft Windows command prompt window (as an Administrator). NET USER ldapdb2 somepassword /ADD /ACTIVE:yes /expires:never /comment:"ITDS Account"   NET LOCALGROUP Administrators /add ldapdb2 The account ldapdb2 now exists on the Windows Server, is active, and has the proper privileges. You can now move into the actual setup of ITDS.

Note: When installing on Windows, if the installation program exits without displaying the language window, it might be caused by one of the following: •Backlevel video drivers. Update your video drivers to the most recent levels to correct this. •Not enough space in the directory specified by the TEMP environment variable. Be sure that you have at least 100 MB of free space in this directory.

Note: This is the language used in the installation program, not in IBM Tivoli Directory Server. You choose the language used in IBM Tivoli Directory Server in step 10.

Note: Do not use special characters, such as hyphen (-) and period (.) in the name of the installation directory. If you do not use the default location, use a name such as ldap or ldapdir. Do not use a name such as ldap-dir or ldap.dir.

Note: Note the following: •This user ID must not be the one you created in Creating the DB2 database owner. •If you are using an existing Microsoft Windows user ID, be sure that your password is correct. Otherwise, DB2 does not install correctly. •If you are using an existing Windows user ID, it must be a member of the Administrators group. •If you are not using an existing user ID, DB2 creates the user ID you specify with the password you type.

Note: If you installed the server, you must restart your system to complete IBM Tivoli Directory Server configuration. You are unable to use IBM Tivoli Directory Server until this is completed.

Note: Double byte character set (DBCS) characters in the password are not supported.

Note: Verify that the user ID you have created or assigned can successfully log into the system. Check to ensure the password does not expire on first login. Check to see if the account is enabled.

Note: IBM Tivoli Directory Server supports a wide variety of national language characters through the UTF-8 (UCS Transformation Format) character set. As specified for the LDAP Version 3 protocol, all character data that is passed between an LDAP client and a server is in UTF-8. Consequently, the directory server can be configured to store any national language characters that can be represented in UTF-8. The limitations on what types of characters can be stored and searched for are determined by how the database is created. The database character set can be specified as UTF-8 or it can be set to use the server system's local character set (based on the locale, language, and code page environment). If you specify UTF-8, you can store any UTF-8 character data in the directory. LDAP clients running anywhere in the world (in any UTF-8 supported language) can access and search the directory. In many cases, however, the client has limited ability to properly display the results retrieved from the directory in a particular language/character set. There is also a performance advantage to using a UTF-8 database because no data conversion is required when storing data to or retrieving data from the database.

Note: There are a number of other ways to start ITDS. Please refer to Chapter 9, “IBM Tivoli Directory Server Distributed Administration” on page 193, for more information.