Installing Directory Server Enterprise Edition 6.0
By mcraig on Mar 03, 2007
This entry takes you through Directory Server Enterprise Edition installation on Windows, showing screen shots taken while installing Directory Service Control Center with Directory Server and Directory Proxy Server on a Windows system.
Directory Server Enterprise Edition 6.0 comes in two installation distributions:
The Java Enterprise System native packaging distribution, which is installed as root on UNIX, Administrator on Windows.
You install this distribution through the Java ES installer.
The zip distribution, which you can install as non-root.
You install this distribution using a command called dsee_deploy.
One big difference between the distributions is that they do not include exactly the same software. The Java ES distribution gives you the web-based console, Directory Service Control Center. The Zip distribution gives you Identity Synchronization for Windows and Directory Editor.
So if you want to install Directory Service Control Center, as I will do below, you choose the Java ES distribution. For a longer explanation, see the DSEE Installation Guide.
Downloading Directory Server Enterprise Edition
To install Directory Server Enterprise Edition with the web-based Directory Service Control Center on Windows, get the Windows .zip file, java_es-5-identsuite-ga-windows-x86.zip.
Installing Software With the Java ES Distribution
After you unpack the Java ES distribution download, run the setup program. I double-clicked setup.exe.
When you run setup.exe, you get the choice of doing a full install of everything in Java ES, or a custom install. The default is a full install. Pick custom to install just Directory Server Enterprise Edition. Custom install is not the default choice.
As you go through the installer wizard, there are two screens where you need to pay close attention. First, when you go to select what to install, clear the default. Pick just Directory Server Enterprise Edition instead.
Second, choose Configure manually after installation. This gives you control over what Directory Server Enterprise Edition software you set up. You will set things up afterward with Directory Service Control Center.
This “configure later” installation may seem to leave you high and dry when the install program finishes. The installer window closes. Nothing indicates what steps come next.
It turns out that a configure later installation only puts the software in the right places on your disk, and registers software with the system. Everything is awaiting your command. So the next thing to do is issue some commands.
(By the way, if you run the setup.exe again, you can use the installation program to remove software, or to modify your installation.)
Initializing Directory Service Control Center
The first command to issue is the one to set up Directory Service Control Center. Directory Service Control Center is the web-based console where you can set up Directory Server and Directory Proxy Server. The command to issue is dsccsetup initialize.
In order to get this to work, you first need to find the dsccsetup program. If you just accepted the default path, then you will find Directory Server Enterprise Edition software installed under C:\\Program Files\\Sun\\JavaES5\\DSEE.
So C:\\Program Files\\Sun\\JavaES5\\DSEE\\dscc6\\bin is where you will find the dsccsetup program.
When you run dsccsetup initialize, you notice that it registers the Directory Service Control Center web application into Sun Java Web Console, and registers an agent into Cacao. Cacao, the Common Agent Container. Cacao is a sort of clearing house service for applications that do remote management. Cacao lets those applications register their local agents. Cacao then lets remote applications contact their local agents. The local agents can therefore do system level work - create a new server, start a server, etc. - that remote applications cannot easily do over the network.
The key step to notice, however, is that you pick a password for your Directory Service Manager. Keep track of that password. If you set everything up properly, you can use the Directory Service Manager password to do all sorts of directory service administration. Directory Service Manager is an account that is typically set up throughout your directory service.
Starting Directory Service Control Center
Directory Service Control Center is a Java Web Console application, a container for web applications. So you get to Directory Service Control Center through Java Web Console, which by default is at https://localhost:6789 where you install.
On Windows, the first time you login to Java Web Console, you must do so as a member of the local administrators' group. So this first login is done as a system user. The first login gets you to the Java Web Console page that shows all the applications you can manage.
I installed on a system with support for French, as you can see. Of course, you have your choice of several languages, including English.
After you log in through Java Web Console, you get a link to Directory Service Control Center.
Clicking that link takes you to the Directory Service Control Center login page. Here is where you need to remember the Directory Service Manager password. This second login is done as Directory Service Manager, a user whose credentials are stored in the DSCC Registry, not anywhere on the system. The second login takes you from the page of all applications you can manage to the page specifically for DSCC.
Successful login brings you finally to the Directory Service Control Center home page.
Great! You are ready to set up directory services.
If you are a command line type, you probably did not read this far. Suffice it to say that the Zip distribution install, once you get to the dsee_deploy command, is quick. But you do not get the web-based console, just the command line tools for 6.0. To summarize, here is a dsee_deploy installation.
$ ./dsee_deploy install -c all -i /local/partition $
Look at the dsee_deploy(1M) man page for more. Or read the DSEE Installation Guide. The DSEE Installation Guide also explains how to create servers with command line tools.