Documentation for Crowd 1.0. Documentation for other versions of Crowd is available too.
start_crowd.bat
for Windows;start_crowd.sh
for Unix environment.You can configure Crowd to suit your environment, as described in:
When configuring Crowd, there are two important files to be aware of:
build.properties
— this is a configuration file that stores various deployment properties of Crowd and the demo application.build.xml
— this is an Ant script that loads properties from the build.properties configuration file.When you change the port that Crowd uses or connect Crowd to an external database, you will need to edit build.properties
and run build.bat
(or build.sh)
.
build.properties
The default build.properties
file will look similar to the following:
# Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See .\etc\hibernate.properties for a list of supported dialects. hibernate.dialect=org.hibernate.dialect.HSQLDialect # The Hibernate transaction factory to use. See .\etc\hibernate.properties for a list of supported dialects. hibernate.transaction.factory_class=org.hibernate.transaction.JTATransactionFactory # Crowd context root crowd.url=http://localhost:8080/crowd # Demo context root crowd.url=http://localhost:8080/demo
パラメーター |
説明 |
|
---|---|---|
hibernate.dialect |
This parameter controls the database dialect the Hibernate persistence system will use when executing commands versus your database server. |
|
hibernate.transaction.factory_class |
This parameter controls the transaction factory to use when executing transactions at run-time:
|
|
crowd.url |
The path and port for the root of the Crowd Administration Console web-application. |
|
demo.url |
The path and port for the door of the Crowd demo web-application |
|
build.xml
If configuring Crowd and/or the demo application to run on a port and context path other than the default, you will need to run the command build.sh
(or build.sh)
against the build.xml
configuration file. This process will then edit all of the necessary Crowd configuration files for your deployment.
The sample output from running build.xml
will look similar to the following:
jstepka-osx:~/atlassian-crowd-1.0.1 $ ./build.sh Buildfile: build.xml init: assistant: [echo] Configuring the Crowd Console [echo] Copying crowd.properties to: crowd-webapp/WEB-INF/classes [copy] Copying 1 file to /Users/jstepka/Projects/crowd/releases/atlassian-crowd-1.0.1/crowd-webapp/WEB-INF/classes [echo] Configuring the Crowd hibernate configuration [echo] Copying hibernate.properties to: crowd-webapp/WEB-INF/classes [copy] Copying 1 file to /Users/jstepka/Projects/crowd/releases/atlassian-crowd-1.0.1/crowd-webapp/WEB-INF/classes [echo] Configuring the demo application [echo] Renaming and copying demo.properties to: demo-webapp/WEB-INF/classes/crowd.properties [copy] Copying 1 file to /Users/jstepka/Projects/crowd/releases/atlassian-crowd-1.0.1/demo-webapp/WEB-INF/classes BUILD SUCCESSFUL Total time: 0 seconds