3. Connecting Crowd to a Database

By default, Crowd 'Standalone' is shipped preconfigured with HSQL. This is fine for evaluation purposes, but for production installations, you should connect Crowd to an enterprise database. This also lets you take advantage of existing database backup and recovery procedures.

The following instructions will allow you to configure Crowd to an external database:

• 3.1 HSQL DB
• 3.2 MS SQL Server
• 3.3 MySQL
• 3.4 Oracle
• 3.5 PostgreSQL

Database Overview

The Crowd distribution includes the Apache Tomcat application server and an in-memory HSQL database engine. This JNDI reference (CrowdDS) can be adjusted to use your custom database and driver by editing the crowd.xml deployment description.

You will also need to edit the file build.properties, and run the script  build.xml, as described in 2. Installing and Configuring Crowd. The two relevant properties in the build.properties file are:

• hibernate.dialect
• hibernate.transaction.factory_class

These are described as follows.

hibernate.dialect

Below is a list of supported databases and their Hibernate configurations. You will need to edit the  hibernate.dialect property to correspond to whichever database you are using:

hibernate.transaction.factory_class

You will need to edit the  hibernate.transaction.factory_class  property to correspond to whichever application server you are using:

関連トピック

• 1. System Requirements
• 2. Installing and Configuring Crowd
  • 2.1 Changing the Port that Crowd uses
• 3. Connecting Crowd to a Database
  • 3.1 HSQL DB
  • 3.2 MS SQL Server
  • 3.3 MySQL
  • 3.4 Oracle
  • 3.5 PostgreSQL
• 4. Running the Setup Wizard