Documentation for Crowd 2.8. Documentation for earlier versions of Crowd is available too.

Skip to end of metadata
Go to start of metadata

The instructions below tell you how to install the Crowd distribution (not EAR-WAR), which includes Apache Tomcat. If you wish to deploy a WAR distribution of Crowd or CrowdID on your own existing application server instead, read the instructions on the Crowd WAR distribution.

Crowd versions 1.1 and later include CrowdID. Installing Crowd, as described below, will also install CrowdID.

Hint: If you are evaluating Crowd or you are unsure which version to install, just follow the simple instructions on this page.


On this page:

1. Prerequisites

  • Java. You will need to install a Java Development Kit (JDK) on your operating system before before proceeding with a Crowd installation. Please note that Crowd requires the full installation of a JDK. It is not enough to run Crowd on a Java Runtime Environment (JRE) alone. For instructions on installing the Sun JDK and setting JAVA_HOME, please refer to Supported Platforms.

2. Install Crowd

  1. Download Crowd (not the EAR-WAR distribution).
  2. Please check your unzip program before extracting the downloaded archive – see the note on the Crowd installation front page.
  3. Unzip the download archive into a directory of your choice. Note: Do not specify directory names that contain spaces.
    (info) We'll refer to this installation directory as {CROWD_INSTALL}.

  4. Specify your Crowd Home directory by editing the configuration file at: {CROWD_INSTALL}\crowd-webapp\WEB-INF\classes\ The Crowd Home directory is where Crowd will store its configuration information. If you are using the embedded HSQL database, supplied for evaluation purposes, Crowd will also store its database in this directory. (Note however that the CrowdID database will be in the installation directory, not the Home directory.) To specify the Crowd Home directory:
    • Open the file. This is found at <crowd_install_directory>/crowd-webapp/WEB-INF/classes/
    • Choose the appropriate line in the file, depending upon your operating system (see below).
    • Remove the # at the beginning of the line.
    • Enter the name of the directory you want Crowd to use as its Home directory. For example,
      • On Windows:

        Note: On Windows, make sure you use forward slashes as shown above, not backward slashes.

      • On Mac and UNIX-based systems:


        Please, ensure that the Crowd Home directory will not match the Crowd installation directory AND it is writable by the user executing the initialization script.

    • Save the file.

3. Prepare your Database

For evaluators

This step applies to production installations. If you are evaluating Crowd and are happy to use the database supplied, you can skip this step.

If you wish to set up Crowd and/or CrowdID with an external database, see:

4. Start Crowd and Complete the Setup Wizard

  1. Run the start-up script, found in your {CROWD_INSTALL} directory:
    • start_crowd.bat for Windows.
    • for Mac and Unix-based systems.
  2. Point a web browser at http://localhost:8095/crowd where you will see the Crowd Setup Wizard. Follow the instructions in the Wizard. You can also read more information about the Setup Wizard.

Next Steps



  1. Anonymous

    on your operating system before before proceeding with a Crowd installation

  2. Would be more useful if the instruction we broken up cleanly by operating system.

    Also how do you handle the situation when '' does not run?

  3. Hello everyone!
    I have some problem with 'start_crowd.bat'. I follow documentation, but Crowd not started. I use command panel with admin rules and write 'netstat -a', but i'm not looking '' or anyone service who listening '8095' port. 
    What's may be wrong? 

  4. I too had the same issue today when trying to install Crowd - I needed to setup the JAVA_HOME Environment Variable before the batch file would run.

    Setting JAVA_HOME 

  5. Because you have a period in the crowd.home variable, this has to be set in the manually every upgrade. If you removed the period - say CROWD_HOME to be like JAVA_HOME - this could be set as an environmental variable and make Linux upgrades simpler and abit more fool-proof. 


  6. The sequence of the described steps is not completely correct. I just followed the instructions and detected that the "Next Steps - run automatically..." instructions require that the previous step "4. Start Crowd..." has not yet been performed. This leads to a failure of the "mkdir" command in the preparations script of "Next Steps", because the database folder has already been created and filled by the previous step.