Installing Directory Server Enterprise Edition 7.0

Download DSEE free of charge This entry takes you through Directory Server Enterprise Edition installation on Windows Server 2008, showing screen shots taken while installing Directory Service Control Center with Directory Server and Directory Proxy Server on a Windows system. I wrote a similar entry for DSEE 6.0 in March 2007.

Downloading Directory Server Enterprise Edition

You can download Directory Server Enterprise Edition 7.0 from

To install Directory Server Enterprise Edition, get the Windows .zip file,

Note that DSEE 7.0 processes run as 32-bit applications on Windows systems.

Installing Directory Server Enterprise Edition Software

  1. Unpack the .zip file, which contains the idsktune utility, the Microsoft Visual C++ 2008 Redistributable Package, and the to unpack.
    Files in distribution
  2. Double-click and install vcredist_x86 if the Microsoft Visual C++ 2008 Redistributable Package is not already installed on the system.
  3. Run the idsktune utility.
    idsktune Output
    Note that if this were a production install, I would need more RAM.
  4. Unpack where you want to put the software, such as C:\\Program Files\\Sun.
    The .zip contains a dsee7 folder that houses all the files you need to keep.
    Files unpacked

Note that the files are now installed under C:\\Program Files\\Sun\\dsee7\\.

Setting Up Directory Service Control Center Components

Before you can create Directory Server and Directory Proxy Server instances through the DSCC console, you must set up the DSCC console (a web app housed in an application server such as GlassFish, Tomcat, or WebLogic that I expect you to have installed already), and set up the DSCC agent (a local service residing in the Common Agent Container, aka Cacao, that allows you to access servers, in particular to start them when they are stopped, and so forth).

Note that on Windows 2008 if you are not Administrator, you cannot register the DSCC Agent in the Common Agent Container until you set the following Windows registry keys to 0:


The procedure below worked with GlassFish v2.1.

  1. Create the dscc7.war file containing the application to deploy.
    C:\\Program Files\\Sun\\dsee7\\bin>dsccsetup war-file-create
  2. Initialize the DSCC Registry (the Directory Server instance DSCC uses to keep track of managed servers).
    C:\\Program Files\\Sun\\dsee7\\bin>dsccsetup ads-create
    During this step, set and remember the Directory Service Manager password.
    Directory Service Manager is the DSCC user who has credentials to handle all managed servers.
  3. Register the DSCC Agent in the Common Agent Container.
    C:\\Program Files\\Sun\\dsee7\\bin>dsccsetup cacao-reg
    Cacao will listen on port 21162
    Note the port number used by the Common Agent Container.
  4. Add the following permissions to the end of the C:\\Program Files\\Sun\\SDK\\domains\\domain1\\config\\server.policy file.
    // Permissions for Directory Service Control Center
    grant codeBase "file:${com.sun.aas.instanceRoot}/applications/j2ee-modules/dscc7/-"
  5. Deploy DSCC.
    Select WAR file

    Deploying DSCC war
  6. Login to Directory Service Control Center using the Directory Service Manager password from the previous procedure.
    Login DSCC
  7. At this point, you should see the DSCC home page.DSCC home

Creating a Directory Server Instance

Time to create a directory to hold sample data.

  1. Click Create New Directory Server.
  2. Provide the properties needed to create the server, and click Next.
    (See the screen shot below for hints.)
  3. Accept the self-signed certificate, and click Next.
  4. Accept the Default Settings, and click Next.
  5. Note that the DSCC Agent Port is the port number provided when the Agent was registered in the previous procedure.
    Create DS instance
    The host name in this case is localhost, since the server is running in VirtualBox on a laptop. (Now you know why I did not give it 4GB RAM ;-)
  6. Click Finish.

Before going further, add a dc=example,dc=com suffix, and import sample data into the Directory Server instance just created.

  1. In DSCC under Directory Server > Suffixes, click New Suffix.
  2. Use the example suffix DN, dc=example,dc=com, and click Next.
  3. Skip replication for now, and click Next.
  4. Choose the localhost:1389 server you created, then click Next.
  5. Accept the Default Settings, and click Next.
  6. Accept the Default Database Location, and click Next.
  7. Select , and click Next.
  8. Read the summary, and click Finish.
    Import example data

Creating a Directory Proxy Server Instance

Next, create a proxy that could be used instead of allowing direct access to the directory.

  1. On the DSCC home page, click Create New Proxy Server.
  2. Provide the properties needed to create the server, and click Next.
    (See the screenshot below for hints.)
  3. Accept the Default Settings, and click Next.
  4. Read the summary, and click Finish.
    Create DPS instance

Finally, you can use DSCC to configure the proxy to send requests to the Directory Server instance.

  1. Under the Proxy Servers tab, click localhost:9389.
  2. Under the Routing > Data Sources tab, click New Data Source.
  3. Provide a name, but otherwise accept defaults throughout the Creating New Data Source wizard.
  4. Under the Routing > Data Source Pools tab, click defaultDataSourcePool.
  5. Click Choose Data Sources, and add the new data source you created to the Data Source list.
  6. In each LDAP operation column for the data source, set the weight to 1.
    Data source pool settings
  7. Under Server Operation > Main, click Restart.

Trying It Out

Directory Server Enterprise Edition is delivered with command line tools for accessing the directory service. For example, the ldapsearch tool installed here in C:\\Program Files\\Sun\\dsee7\\dsrk\\bin, allows you to see that the search functionality is working as expected.

First, search Directory Server on port 1389 to verify the data is there. Then, search through Directory Proxy Server on port 9389 to make sure the proxy is properly configured.

Try it out

Note that you can now access Directory Server data through Directory Proxy Server, and that you can manage both servers through Directory Service Control Center.


I think step 3 is dsccsetup cacao-reg.
Thanks for the post Mark.

Posted by Paul Dhanjal on December 02, 2009 at 01:14 PM CET #

Absolutely. Good eyes, Paul on catching that bad copy/paste. Thanks for your help. I'll fix the mistake inline.

Posted by Mark Craig on December 03, 2009 at 12:44 AM CET #

By the way, if you forget the Microsoft Visual C++ 2008 Redistributable Package, and an ldapsearch gives you an error like, "The application was unable to start correctly (0xc0150002)," you need to go back and install vcredist_x86.exe. (Thanks, Arnaud, who wrote this up at

Posted by Mark Craig on December 16, 2009 at 10:00 AM CET #

I have a problem here, may be I can get an reliable answer from you: I did not install application server. I create instance and suffix in command line.The default port DSCC registry on cacao is 3998.(Seems it can not modified?) Then I can search the entries with the ldapsearch tool which is installed with DSEE7.0. But LDAP browser on another machine can't connect to it with port 3998.

Does the application server is an obligatory part to DSEE7.0 installation?

Posted by Lisa zhao on March 05, 2010 at 03:28 AM CET #

Thanks for your comment.

An application server is required as a container for the Directory Service Control Center application. If you cannot deploy an application server, you can still use the command-line tools to manage Directory Server and Directory Proxy Server instances (for Directory Server: dsadm and dsconf; for Directory Proxy Server: dpadm and dpconf).

Directory Service Control Center lets you manage your entire service graphically from one place, so it can be quite an advantage if you often have administrative/configuration operations to perform. Directory Service Control Center uses the DSCC Registry to store information about your whole directory service. You do not need the DSCC registry if you do not use Directory Service Control Center. You also probably will not need the common agent container (cacao) if you do not use Directory Service Control Center.

Hope this helps,

Posted by Mark Craig on March 08, 2010 at 01:21 AM CET #

The version got pulled by Oracle/Sun. Anywhere else where this can be downloaded?


Posted by Da Mooli on July 26, 2010 at 12:05 PM CEST #

Hello Da Mooli,

Check out the link in the product management blog entry on the subject,

Hope this helps,

Posted by Mark Craig on July 27, 2010 at 04:57 AM CEST #

Awesome // Thanks
Got DSEE v7 and set it up on Apache Tomcat.

Posted by Da Mooli on July 28, 2010 at 09:33 AM CEST #

Small question. After a reboot, I have to run the following two commands to get the DSEE up and running;

C:/Sun/dsee7/ext/cacao_2/bin/cacaoadm.bat start
C:/Sun/dsee7/bin/dsadm.exe start C:/Sun/dsee7/var/dcc/ads

Any elegant way of getting these up automatically other than sticking them in a batch file set to auto run?


Posted by Da Mooli on August 05, 2010 at 08:01 AM CEST #

In theory it's possible to start these as Windows services, as described in another entry,

In practice, you may find that some things are not working. See the comment from Stefan at the end of the entry.

Posted by Mark Craig on August 16, 2010 at 04:31 AM CEST #

Can anyone tell me where to download DSEE-7. I tried to download it but i could not find it. OR anyone can can share this software for me.

Posted by vinu on November 24, 2010 at 02:50 PM CET #


You'll find links to the ODSEE 11g R1 download on the landing page at

ODSEE 11g R1 is essentially DSEE 7.0.1. That is 7.0 plus over 100 fixes and enhancements made in response to customers' experience with 7.0, plus Oracle branding. Documentation is currently viewable at

Hope this helps. Regards,

Posted by Mark Craig on November 25, 2010 at 01:23 AM CET #

Post a Comment:
  • HTML Syntax: NOT allowed

Mark Craig writes about Directory Services products and technologies. The views expressed on this blog are my own and do not necessarily reflect the views of Oracle.


« June 2016