HP-UX Directory Server 8.1 installation guide

setup file (see “Importing LDIF files for configuring Directory Server users, replication, and other
entities” (page 36)).
1.2.7 Configuration directory
The configuration directory (also referred to as the Configuration Directory Server) is the main
directory that stores configuration information such as log files, configuration files, and port
numbers. These configuration data get stored in the o=NetscapeRoot tree. A single Directory
Server instance can be both the configuration directory and the user directory.
If you install Directory Server for general directory services, and more than one Directory Server
exists in your organization, you must determine which Directory Server instance will host the
configuration directory tree, o=NetscapeRoot. Make this decision before installing any
compatible Directory Server applications. The Directory Server setup script asks if you want
to register the new Directory Server instance with an existing Configuration Directory Server,
and if you do, it prompts you for information about the Configuration Directory Server. If you
are setting up the first Directory Server instance on the network, then the new Directory Server
instance will be set up as the Configuration Directory Server as well.
Because the main configuration directory generally experiences low traffic, you can permit its
server instances to coexist on any machine with a heavier-loaded Directory Server instance.
However, for large sites that deploy a large number of Directory Server instances, improve
performance by dedicating a low-end machine for the configuration directory. Directory Server
instances write to the configuration directory, and for larger sites, this write activity can create
performance issues for other directory service activities. The configuration directory can be
replicated to increase availability and reliability.
If the configuration directory tree gets corrupted, you may have to re-register or re-configure all
Directory Server instances. To prevent this:
• Always back up the configuration directory after setting up a new instance
• Never change a host name or port number while active in the configuration directory
• Do not modify the configuration directory tree; only the setup script can directly modify
a configuration
1.2.8 Administration domain
The administration domain allows servers to be grouped together logically when splitting
administrative tasks. This level of organization is beneficial, for example, when different divisions
within an organization want individual control of their servers while system administrators
require centralized control of all servers.
When setting up the administration domain, consider the following:
• Each administration domain must have an administration domain owner with complete
access to all the domain servers but no access to the servers in other administration domains.
The administration domain owner may grant individual users administrative access on a
server-by-server basis within the domain.
• All servers must share the same configuration directory. The Configuration Directory
Administrator has complete access to all installed Directory Servers, regardless of the domain.
• Servers on two different domains can use different user directories for authentication and
user management.
The Directory Server setup script allows you to set up a separate Administration domain for the
new Directory Server instance. If you do not need to set up a different domain for the new
instance, the default is the host's domain (the domain of the new Directory Server instance).
10 Preparing for a Directory Server installation