The configuration process involves the following steps:
Plan your directory service. By planning your directory tree in advance, you can design a service that is easy to manage and scale as your organization grows. For guidance on planning your directory service, refer to the deployment guide for the version of Sun ONE Directory Server that you are using.
Select the Sun ONE Directory Server configuration method you prefer to use. See Selecting a Directory Server Configuration Method for a list of Sun ONE Directory Server configuration methods.
Configure Sun ONE Directory Server as described in this chapter.
(Optional) Set up the Sun ONE Administration Server and Sun ONE Server Console. For Sun ONE Directory Server 5.1, Sun ONE Administration Server and Sun ONE Server Console are set up during the directory server installation process.
Create the directory suffixes and databases. You do not have to populate your directory now. You should, however, create the basic structure for your tree, including all major roots and branch points. For information about the different methods of creating a directory entry, refer to the administration guide for the version of Sun ONE Directory Server that you are using.
Create additional Sun ONE Directory Server instances and set up replication agreements between the instances to ensure availability of your data. For information about creating additional Directory Server instances and setting up replication agreements, refer to the administration guide for the version of Sun ONE Directory Server that you are using.
You can configure Sun ONE Directory Server software using one of the three different configuration methods supported by the configuration program.
Express configuration
Use this method if you are installing for the purposes of evaluating or testing Sun ONE Directory Server.
Typical configuration
Use this method if you are performing a normal install of Sun ONE Directory Server.
Custom configuration
In Sun ONE Directory Server, the custom configuration process is very similar to the typical configuration process. The main difference is that the custom configuration process allows you to import an LDIF file to initialize the user directory database that is created by default.