Home > ForgeRock, IDM, LDAP, Open Source, Tools > Installing and Configuring ForgeRock OpenDJ on Windows

Installing and Configuring ForgeRock OpenDJ on Windows

Unfortunately I’m currently out of business while being home sick. But this gives me the chance to get hands-on on some tools I have on my list to discover them during this year. The first of them is the OpenDJ LDAP Server of ForgeRock.

I’ve used the nightly build of OpenDJ 2.7 and ran through the MSI installation wizard first.



For the initial shot I’ve used the default installation directory.



The installation is done pretty quick. What I’m missing here is to start the configuration wizard directly out of the installation wizard. @ForgeRock: Maybe this might be a good add-on to future releases of OpenDJ.

To start the graphic installation you’ve to execute the setup.bat file located in the installation directory without any additional command line parameter.


This I the upcoming configuration wizard.


The first configuration screen comes up with the FQDN of the server we’re currently running on, asking for the LDAP Listener Port (default 389, my configuration will be 1028 as there are other LDAP servers already running on my current machine). I’ve left the administration port at 4444 as I’ve no service bound on this port yet.

For testing purposes I’ve not configured LDAP secure access yet, I’ll add that in a later blog post.

Last step on this configuration screen is to define the root user DN and password for the administration account.


The next screen is to configure replication if needed. I’m planning to set up a Linux server in parallel hosting a OpenDJ LDAP Server as well and to have it replicating with my current server. So I’ve left the default replication port, configured it as secure but left the replication information empty as this is my first OpenDJ LDAP Server so far.


Next configuration step is the definition of the Directory Base DN. I’ve chosen


for this initial shot (you might see different DNs in later blog posts).

There are some options to load data initially using a LDIF file or to import sample data for testing purposes as well. I’ve decided to just create the base entry so far and to set up the remaining LDAP structure later on.


The next screen is to define specific Java runtime options. I’ve used default here.


The next screen allows to review all settings before finishing the installation.


The configuration wizard is now taking care of creating my LDAP instance as I’ve configured it in the screens before.

In the end we do have a running instance of the ForgeRock OpenDJ LDAP Server. Pretty simple, isn’t it?

Categories: ForgeRock, IDM, LDAP, Open Source, Tools
  1. Ludo
    February 4, 2015 at 11:12 am

    Nice post, appreciated !
    I think there are 2 improvements to add to the MSI installer for OpenDJ, but I don’t know yet if both are doable.
    The first one, you pointed out, would be to launch the graphical configuration wizard.
    The second one is required to do the first one, we need to check for the availability of the JVM, and if not present, possibly force an installation… I’d be interested to learn if it’s possible with MSI, and if there are open source projects or products that are automatically doing it.

    • February 4, 2015 at 12:12 pm

      Hi Ludo
      Thanks for dropping a comment. Starting a configuration tool can be done, I’ve seen it being implemented with other tools (closed source) as well.
      Checking for the existing JVM might be a interesting feature as well. Both options will surely depend on the framework that is being used to build the MSI packages.
      I’m not a real packaging specialist, but if you’re looking for someone to testdrive potential results, just drop me a note and i’d be more than happy to try it.

      • February 18, 2015 at 8:48 pm

        We can definitely look for JVMs in the registry, and I think we could then set the OPENDJ_JAVA_HOME environment variable to an appropriate value – and perhaps even fail the install if we can’t find a JVM.

        The only trouble with doing this is when you update your JVM it might mean you have to update your OPENDJ_JAVA_HOME.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: