Documentation for Crowd 2.0.x. Documentation for other versions of Crowd is available too.
Below is a summary of the steps required to install the Crowd WAR distribution.
The Crowd and CrowdID WAR distributions are intended for deployment onto an existing J2EE application server. This documentation assumes that you already know how to deploy a web application onto your chosen application server. If not, please contact your system administrator to assist you, or consider installing the Crowd Standalone distribution instead.
The standard Crowd installation guide tells you how to install the Standalone distribution of Crowd, which includes Apache Tomcat. Instead, you may wish to deploy Crowd or CrowdID onto your own existing application server. For this purpose, we provide WAR (Webapp ARchive) distributions of the Crowd and CrowdID server applications.
Please check that your database and server are supported and make sure that all dependencies are installed as described below, otherwise Crowd will not run properly.
Key: = Supported.
= Not Supported
Java バージョン |
|
---|---|
JDK (1) |
|
OS |
|
Microsoft Windows (2) |
|
Linux / Solaris (2) |
|
Apple Mac OS X (2) |
|
アプリケーションサーバー |
|
Apache Tomcat (3) |
|
データベース |
|
MySQL (4) |
|
Oracle |
|
PostgreSQL |
|
Microsoft SQL Server |
|
HSQLDB (5) |
|
ウェブブラウザー |
|
Microsoft Internet Explorer (Windows) |
|
Mozilla Firefox (すべてのプラットフォーム) |
|
Safari |
|
Opera |
|
Notes:
1. JDK:
2. Operating systems: Crowd is a pure Java application and should run on any platform provided the Java runtime platform requirements are satisfied.
3. Tomcat: Deploying multiple Atlassian applications in a single Tomcat container is not supported. We do not test this configuration and upgrading any of the applications (even for point releases) is likely to break it. There are also a number of known issues with this configuration. See this FAQ for more information.
In addition, there are practical reasons for recommending that you do not deploy multiple Atlassian applications in a single Tomcat container. Firstly, you will need to shut down Tomcat to upgrade any application and secondly, if one application crashes, the other applications running in the Tomcat container will be inaccessible.
4. MySQL: Please ensure that you set transaction isolation to 'read-committed' instead of the default 'repeatable-read', as described in the database configuration guide.
5. HSQLDB: Crowd ships with a built-in HSQL database, which is fine for evaluation purposes but is somewhat susceptible to data loss during system crashes. For production environments we recommend that you configure Crowd to use an external database.
lib
folder on the application server:
The JTA specifies standard Java interfaces between a transaction manager and the parties involved in a distributed transaction system: the resource manager, the application server and the transactional applications. Refer to the Sun documentation for more information.
activation-1.1.jar
, jta-1.0.1B.jar
and mail-1.4.jar
. You will find them in {CROWD_INSTALL}\apache-tomcat\lib
(for Crowd 2.0.2 or later) or in {CROWD_INSTALL}\apache-tomcat\common\lib
(for Crowd 2.0.1 or earlier). Below is a summary of the Crowd WAR installation steps:
CROWD-INSTALLATION
in the rest of these instructions. CROWD-INSTALLATION/WEB-INF/classes/crowd-init.properties
. 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:
crowd-init.properties
file.#
at the beginning of the line.crowd.home=c:/data/crowd-home
crowd.home=/var/crowd-home
重要
Please, ensure that the Crowd Home directory will not match the Crowd installation directory.
crowd-init.properties
file.CROWD-INSTALLATION
directory or the WAR file into your application server's deployment directory. Please consult your application server's documentation on this point. crowd.xml
that contains the following context:
<Context path="/crowd" docBase="/path/to/atlassian-crowd-war-directory" reloadable="false"/>
/path/to/atlassian-crowd-war-directory
' in the above element to reflect the actual path to your Crowd WAR distribution. To avoid problems with your deployment, this should NOT be Tomcat's webapps
directory. If you are installing Crowd on Windows, make sure that the paths you specify for the location of the WAR file and database are full paths including drive letters.conf/Catalina/localhost/
directory. conf/server.xml
file. For example, you need to do this if your user directory allows for internationalised characters in usernames.
conf/server.xml
file, find the connector definition for your HTTP protocol. The connector definition looks very much like this:
<Connector port="8080" maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" maxSpareThreads="75" enableLookups="false" redirectPort="8443" acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true"/>
URIEncoding="UTF-8"
property to the connector:
<Connector port="8080" maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" maxSpareThreads="75" enableLookups="false" redirectPort="8443" acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" URIEncoding="UTF-8"/>
This setting affects all web applications
Because you must define this property at the connector level, this setting will affect all web applications you have deployed under the connector. This should not adversely affect the other web applications, but please be aware of this fact. Crowd and CrowdID will run fine without this property set, but you will run into issues if a username or group contains internationalised characters.
http://localhost:8080
). The Crowd Setup Wizard will start.