(info) The Confluence EAR-WAR edition is intended for deployment into an existing J2EE application server. It is assumed that you already know how to deploy a web application on the application server of choice. If not, please contact your system administrator to assist you, or consider installing the Confluence Standalone edition instead.

Confluence EAR-WAR requirements

In addition to the Confluence requirements, the EAR-WAR edition requires an application server:

Compatible & Supported
  • Apache Tomcat (4.1 and 5.5)
  • Weblogic (8.1 SP3 and above)
  • Resin (2.11.11 and above)
  • JBoss
  • Orion (2.0.2 and above)
  • Websphere (5.1.1.3 and above)

Potentially Compatible But Untested & Unsupported

  • Macromedia JRun
  • Microsoft IIS Server
  • Oracle Application Server

Incompatible

Setup Notes and List of Known Issues for Application Server Configuration can be found here

How to install Confluence EAR-WAR on Tomcat


Step 1 - Download and extract WAR

  1. Download the Confluence EAR/WAR zip file. (You need to click the 'Show advanced downloads' link to get access to the EAR/WAR zip file.)
  2. Extract the downloaded zip file:
    • Windows users must avoid Win XP's built-in unzip as it doesn't extract all the files. Use a 3rd party zip extractor like WinZip.
    • Solaris users will need to use GNU tar to handle the long filenames.
    • Tomcat users must not unzip their Confluence install to inside the Tomcat webapps folder as this may cause Confluence to be deployed more than once.
  3. It will unzip your Confluence install directory, which should contain the version number e.g. confluence-2.2.9 or confluence-2.5.0. This directory will be later referred to as the Confluence install directory. Inside is a confluence subdirectory, referred to later as the Confluence WAR directory. Record the absolute path to the Confluence WAR directory.

Step 2 - Check for patches

Review the Release Notes for your Confluence version and apply any patches listed.

Step 3 - Check for application server issues


ラベル別コンテンツ

指定したラベルを持つコンテンツはありません。



Step 3 - Configure confluence-init.properties

  1. Inside the Confluence install directory, edit ...confluence/WEB-INF/classes/confluence-init.properties in a text editor
  2. Set the confluence.home property to a directory of your choosing. This is the directory that will contain all of Confluence's configuration, backup and attachment files.

Step 4 - Edit Tomcat context descriptors

If you are using Tomcat 5.5.x:

  1. Create a file called confluence.xml in your Tomcat installation's conf/Catalina/localhost directory. (If you have set up a different hostname for your tomcat instance, please specify that instead of localhost.)
  2. Open confluence.xml and add these lines: 
    <Context path="/confluence" docBase="c:/applications/confluence-2.1.3/confluence" debug="0" reloadable="false">
</Context>

    (info) Note: The file atlassian-confluence.log will no longer be created as <Logger> is no longer a valid nested element of <Context> element. See Scott Prater's comments below .
  3. For docBase specify the value you noted down earlier.

If you are using Tomcat 5.0.x:

  1. Create a file called confluence.xml in your Tomcat installation's conf/Catalina/localhost directory. (If you have set up a different hostname for your tomcat instance, please specify that instead of localhost.)
  2. Open confluence.xml and add these lines: 
    <Context path="/confluence" docBase="c:/applications/confluence-2.1.3/confluence" debug="0" reloadable="false">
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="atlassian-confluence." suffix=".log" timestamp="true"/>
</Context>

  3. For docBase specify the value you noted down earlier.

If you are using Tomcat 4.x

  1. Open conf/server.xml in a text editor.
  2. Add the following: 
    <Context path="/confluence" docBase="c:/applications/confluence-2.1.3/confluence" debug="0" reloadable="false">
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="atlassian-confluence." suffix=".log" timestamp="true"/>
</Context>

  3. For docBase specify the value you noted down earlier.

Step 5 - Configure Your application server

Review any documentation associated with your web server here. If your application server requires deploying Confluence as a EAR/WAR, follow these instructions to build the WAR file:

  1. Open the command line prompt
  2. Navigate to the Confluence installed directory
  3. コマンド build war を実行します。
  1. Open a terminal window
  2. Navigate to the Confluence installed directory
  3. Add executable mode to build.sh - chmod +x build.sh
  4. build.sh を実行します。
  5. The WAR file is now located in the dist subfolder in your Confluence installed directory

Step 6 - Restart Server

  1. Shut down, and then restart Tomcat
  2. Confluence should now be accessible on http://host:port/confluence



次のステップ

Setup Confluence

General Tips & Information

トラブルシューティング


Solutions to common issues with installing Confluence. Review your logs by opening the Confluence install directory and checking the /logs/catalina.out and /logs/catalina.out files for errors described below. Click on a problem to show the solution.

An error is preventing Confluence from starting.

  1. Open a command prompt. On Windows, do this by clicking on your Start menu, then click Run. In the Run box, type cmd and press OK
  2. From the command prompt, go to your Confluence install directory
  3. Go into the bin subdirectory
  4. Run startup.bat and read the error message
  5. Find the solution to that error below

If you are seeing "java.lang.NoClassDefFoundError: com/atlassian/confluence/pages/persistence/dao/hibernate/AbstractHibernateAttachmentDao$IntraHibernateAttachmentCopier", you have unzipped Confluence using a program that cannot handle long filenames. You must delete your install directory and go back to the point in the instructions that covers unzipping Confluence using a third-party unzip program.

If http://localhost:8080 goes to an error page when you run Confluence, go to the install directory and find the /logs/catalina.out. If this file contains a single line error starting with "Exception in thread "main" java.lang.NoClassDefFoundError", your install path may contain spaces. The solution is to rename your install directory path so that there are no spaces, then restart Confluence.

The confluence.home variable specified in confluence-init.properties cannot be created. To fix this, edit /confluence/WEB-INF/classes/confluence-init.properties and check the path specified exists. Make sure all the directory slashes use / and that the # has been removed. If you're stuck, try using confluence.home=c:/confluence/data

You have not installed the Java Development Kit, or not set the %JAVA_HOME% to the directory of the JDK. You should re-check your steps in Stage 2.

If you have another Tomcat running on the same machine, you must edit <INSTALL>/conf/server.xml and change both 8080 and 8005 to ports that do not conflict with your other Tomcat instance according to these instructions.

You will need to adjust your system time.

If you did not use one of the recommended unzipping tools, and happened to use for instance the default Windows XP extractor, one of the classes required for starting up Confluence may not be located due to the lengthy file-path. This is due to the reason that the default Windows tool silently fails to extract files with long names. We suggest you to use other tools such as WinZIP and 7zip and redo the deployment process.

Cause:
org.springframework.beans.factory.BeanDefinitionStoreException: Error registering bean with name 'fileSystemAttachmentDataDao' defined in class path resource applicationContext.xml: Class that bean class com.atlassian.confluence.pages.persistence.dao.FileSystemAttachmentDataDao depends on not found; nested exception is java.lang.NoClassDefFoundError: com/atlassian/confluence/pages/persistence/dao/FileSystemAttachmentDataDao$FileSystemAttachmentNamingStrategy
at org.springframework.beans.factory.xml.DefaultXmlBeanDefinitionParser.parseBeanDefinition(DefaultXmlBeanDefinitionParser.java:366)
caused by: java.lang.NoClassDefFoundError: com/atlassian/confluence/pages/persistence/dao/FileSystemAttachmentDataDao$FileSystemAttachmentNamingStrategy
at java.lang.Class.forName0(Native Method)

Check the server logs for errors. If you are running Confluence Standalone on Windows, error messages will be printed to the console window that opened when you ran startup.bat. On Unix systems, Confluence will log messages to logs/catalina.out.

The CATALINA_HOME environment variable is set to another instance of Tomcat. You should run shutdown.sh, remove the CATALINA_HOME reference to the other Tomcat version, and run startup.sh again.

If you try to login with the correct username and password but are always returned to the login screen without any error messages, and you are running Zone Alarm, please check that it is not blocking the Confluence server




関連トピック

Confluence Cluster Installation
Confluence 2.6 Configuration Guide
Confluence Setup Guide
Confluence 2.6 Documentation Home
Confluence Main FAQ

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.