This page last changed on Jan 12, 2010 by asridhar.
Please note that Atlassian Support no longer recommends or supports this configuration. Choose either the EAR/WAR installation or two separate stand-alone installations.

Alternatives

Separate Stand-Alone Installations

A preferable configuration is to run JIRA and Confluence in separate Tomcat instances running behind an Apache frontend server (see guides for Confluence and JIRA).

Advantages
  • Each app can be restarted without affecting the other.
  • If one webapp hangs for any reason (eg. running out of memory), it doesn't affect the other.
  • Any problems can be debugged more easily. Logs are separate and product-specific, rather than everything going to catalina.out. Thread and heap dumps are smaller and more relevant.
  • It reduces the likelihood of jar conflicts (eg. jars that must be installed in common/lib or lib for Confluence running off Apache Tomcat version 6 or above), particularly if you later want to install a third webapp not from Atlassian.
Disadvantages

Offsetting this is the extra complexity of having to run Apache.

Two WAR files in One Application Server

Alternatively, you can use the WAR deployment for both applications in one application server.

Advantages
  • The additional memory required by the application server would be shared.
Disadvantages
  • The disadvantage is that poor performance in one application would affect the other.
If you are deploying JIRA and Confluence on same web server then please apply the fix described in this KB article to fix the bug with Confluence Browse Menu

See Installing the Confluence EAR-WAR Edition and Installing JIRA WAR-EAR for details.

Document generated by Confluence on Mar 28, 2010 19:33