After Directory Server Enterprise Edition is installed and running, the following elements are found on your system:
Software Files
Data Files
Background Processes
The software files include executable files, resource files, and template files. These files are copied on your system from the Directory Server Enterprise Edition distribution.
The software files are organized hierarchically below a single directory, installation-path, which is chosen at the time of installation. The hierarchy below the installation path is called the installation layout. User commands are located in installation-path/bin and installation-path/dsrk/bin directories. For more information about information layout, see Chapter 1, Directory Server Enterprise Edition File Reference, in Oracle Fusion Middleware Reference for Oracle Directory Server Enterprise Edition.
Disk space occupied by installation-path is fixed and around 1GB.
There are two types of data files, that is, server instances and administration files.
Contain user and configuration data for a single server.
Multiple server instances can reside on the same host.
Server instance location can be freely chosen. They can be separate from the installation-path.
Disk space occupied by a server instance is potentially unlimited.
For more information about server instances, see Chapter 2, Directory Server Instances and Suffixes, in Oracle Fusion Middleware Administration Guide for Oracle Directory Server Enterprise Edition and Chapter 17, Directory Proxy Server Instances, in Oracle Fusion Middleware Administration Guide for Oracle Directory Server Enterprise Edition.
Administration files are located in installation-path/var or /var/opt/SUNWdsee7 directory.
Disk space occupied is limited, that is, a few hundred KB.
Core Server Daemons (ns-slapd)
There is one daemon running per server instance. This daemon listens to the port that is configured in the server instance (389 by default) and processes the incoming LDAP requests. This daemon reads and writers configuration and user data located in the server instance.
Common Agent Container (CACAO) Framework Daemon
This daemon allows Directory Service Control Center to start up server instances that exist on remote hosts. The daemon listens on port 11162, by default, and hosts the Directory Service Control Center Agent plug-in.
The CACAO service can only be managed by using the CACAO administrative command-line interface (cacaoadm). Managing the CACAO service by using the Services Manager on Windows systems is not supported and can have undesirable results.
Application Server Daemon
The application server daemon listens to HTTP on port 8080, by default. The daemon hosts Directory Service Control Center web application and present only on the host where Directory Service Control Center is deployed.
Directory Service Control Center Registry Daemon
This is a directory server instance for Directory Service Control Center's own use. The daemon listens to LDAP port 3998, by default. The daemon responds to requests from Directory Service Control Center and present only on the host where Directory Service Control Center is deployed.
Generally, all the elements listed above are rarely present on the same machine. A typical deployment would be laid out as follows:
One machine (the administration host) is dedicated to Directory Service Control Center. On this machine, only the Application Server daemon and the Directory Service Control Center registry daemon are running.
One or more machines are dedicated to server instances. Each machine hosts a single server instance. Only one core server daemon and the common agent container framework daemons are running.
The following figure shows a typical sample deployment.
For more information, see Directory Server Enterprise Edition Administration Model in Oracle Fusion Middleware Deployment Planning Guide for Oracle Directory Server Enterprise Edition.