This page last changed on Mar 21, 2007 by david.soul@atlassian.com.

Please review the system requirements before installing Confluence:

CLIENT REQUIREMENTS

Clients can access Confluence using:

SERVER REQUIREMENTS

Server load depends primarily on the number of users online at once and their usage of Confluence.

Under 25 Online Users

  • 1GHz+ CPU Pentium 4 or equivalent
  • 256MB RAM

Over 25 Online Users

  • Dual 2.4GHz CPU Pentium Xeon or equivalent
  • 512MB+ RAM

See Server Load Hardware Requirements for details.

OPERATING SYSTEM

Supported

  • Windows
  • Linux
  • Mac OS X
  • Solaris
  • AIX
  • Unix

Any OS that support J2EE 1.4

DISK SPACE

Confluence Install Directory - 250MB

  • Install files
  • Nightly site backups
  • Temporary files

Confluence Home Directory or External Database - 250MB minimum

  • Text content
  • File attachments
JAVA

Confluence requires JDK 1.4 or later.

DATABASE

Confluence is bundled with a pre-configured HSQL database for evaluation purposes only. For safe production use, it must be configured to use one of the following databases:

Fully Supported

Supported With Minor Workarounds

  • PostgreSQL 7.1+
  • Oracle 8i, 9i or later
  • Microsoft SQL Server 2000+
  • Sybase ASE 12.5.1+

If you have no preference, PostGreSQL is scalable, free and easy to setup. For database setup information, see Database Configuration.

SELECT CONFLUENCE EDITION

Confluence can be deployed in either:

Standalone Edition
  • Pre-packaged with Apache Tomcat
  • Recommended for all users
  • Ready for production with an external database
EAR-WAR Edition
  • Deploys into an existing application server
  • Suitable only for system administrators
  • Offers no production advantages over Standalone edition

Technical support recommends Standalone edition even for organisations with an existing application server environment.

NEXT

Standalone Install Guide or EAR-WAR Install Guide

OTHER TOPICS

Confluence Setup Guide
Confluence Cluster Installation
Confluence 2.0 User Guide
How to add Confluence to a JIRA Standalone installation
Documentation Home


nav_plain_red.png (image/png)
nav_plain_green.png (image/png)
nav_plain_blue.png (image/png)

JDK 5 is quickly gaining grounds especially among development shops (which many of your customers must be, I would assume). Any chances you might start supporting it more officially some time soon? Thanks.

Posted by oalaoui at Apr 17, 2006 13:31

JDK 5 (Java 1.5) is fully supported on all editions of Confluence.

There is, however, a known problem migrating a Confluence instance from JDK 1.4 to JDK 5: due to slight changes in the 1.5 object model, the contents {dynamictasklist} macros will be lost. (see Re: Dynamic Tasklist Macro)

Posted by cmiller at Apr 19, 2006 18:54

This is a significant problem for anybody with critical data in dynamic tasklists or other similar macros (any other dynamic macros affected?). Is there any way to export this data so it can be recovered? How does a Confluence admin know how much grief this will cause for users? What do you tell uses who lose the data and therefore lose confidence in Confluence?

Posted by bob.swift@charter.net at Apr 20, 2006 07:24

I raised the priority of this issue and we will take a look at it for the next release.

http://jira.atlassian.com/browse/CONF-4082

Cheers,
Jens

Posted by jens@atlassian.com at Apr 26, 2006 20:57

Suggestion:
the text "it must be configured to use:" should be changed to "it must be configured to use one of the following databases:".
Regards, Liberto

Posted by liberty_miller at Feb 12, 2007 23:58

done!
Ib

Posted by ivan@atlassian.com at Feb 13, 2007 16:00
Document generated by Confluence on Mar 22, 2007 20:56