This page describes the supported platforms and hardware requirements for Crowd 2.7.
Key:
= Supported. 
= Not SupportedJava Version |
|
|---|---|
Oracle JDK (1) |
|
| OpenJDK | 1.7 |
Operating Systems |
|
Microsoft Windows (2) |
|
Linux / Solaris (2) |
|
Apple Mac OS X (2) |
|
Application Servers |
|
Apache Tomcat (3) |
|
Databases |
|
MySQL (4) |
|
Oracle |
|
PostgreSQL |
|
Microsoft SQL Server |
|
HSQLDB (5) |
|
Web Browsers |
|
| Chrome | Latest stable version supported |
Microsoft Internet Explorer (Windows) |
|
Mozilla Firefox (all platforms) |
|
Safari |
|
Opera |
|
1.6 (deprecated),
Notes:
1. JDK:
- It is not enough to have the JRE only. Please ensure that you have the full JDK. You can download the Java SE Development Kit (JDK) from the Oracle website.
- Once the JDK is installed, you will need to set the JAVA_HOME environment variable, pointing to the root directory of the JDK. Some JDK installers set this automatically (check by typing 'echo %JAVA_HOME%' in a DOS prompt, or 'echo $JAVA_HOME' in a shell). If it is not set, please see Setting JAVA_HOME.
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.
There are also a number of practical reasons why we do not support deploying multiple Atlassian applications in a single Tomcat container. Firstly, you must shut down Tomcat to upgrade any application and secondly, if one application crashes, the other applications running in that Tomcat container will be inaccessible.
Finally, we recommend not deploying any other applications to the same Tomcat container that runs Crowd, especially if these other applications have large memory requirements or require additional libraries in Tomcat's lib subdirectory.
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.
Vote for more supported application servers
If you are interested in support for other application servers, please make your requests via our issue tracker. In particular, you can vote for the following existing requests:
Hardware Requirements
The hardware required to run Crowd depends significantly on the number of applications and users that your installation will have, as well as the maximum number of concurrent requests that the system will experience during peak hours.
During evaluation Crowd will run well on any reasonably fast workstation computer (eg. 1.5+Ghz processor). Memory requirements depend on how many applications and users you will store, but 256MB is enough for most evaluation purposes.
Most users start by downloading Crowd, and running it on their local computer. It is easy to migrate Crowd to your enterprise infrastructure later.
We would appreciate if you let us know what hardware configuration works for you. Please create a support request in JIRA with your hardware specification and mention the number of applications and users in your Crowd installation.
While some of our customers run Crowd on SPARC-based hardware, Atlassian only officially supports Crowd running on x86 hardware and 64-bit derivatives of x86 hardware.