DSEE includes several features that improve the way in which the component products can be installed.
DSEE provides flexible commands for each step of the installation process so that you can write custom scripts to install and minimally configure a DSEE instance. You can then use your scripts to standardize your deployment so that each server is automatically configured the same.
Directory Server allows you to install the DSEE components as a non-root user. This non-root installation is possible with the zip distribution. You can also install the Directory Service Control Center as a non-root user using the WAR file.
Operating system-specific packaging formats, such as SVR4 for Solaris, requires installation as a privileged user.
Both the zip distribution and native packages provide the ability to install DSEE components into a user-specified installation directory.
With the zip distribution, you can install multiple distinct installations of the component products within a single operating system instance. You can even install the zip distribution on a system with an existing directory server packaging installation. The following constraints apply when installing multiple installations on a single system:
Each instance must be configured so that the total resources (RAM, CPU, and disk) that are consumed by the sum of all instances on the server do not exceed the available resources.
Each installation must have its own distinct installation path.
Each installation must have its own agent port.
With the introduction of Solaris 10 zones, you can also install different versions and installations of the package version of DSEE. In this case, each installation must be contained within its own unique Solaris 10 whole root zone.
The dsmig tool migrates a single Directory Server instance. The dsmig tool allows you to migrate your schema, security information, and configuration information, including replication data, from Directory Server 5.2 and 5.2.x to 11g Release 1 (11.1.1).