This page last changed on Mar 16, 2007 by david.soul@atlassian.com.
This document will assist you in adding Confluence to your existing JIRA Standalone.
Step 0 - Consider alternatives
This guide is for experts only. If you run into any difficulties with this process, Atlassian technical support may provide limited assistance outside of helping users switch to running Confluence Standalone separately.
Before embarking on this process, consider whether you could not rather run JIRA and Confluence in separate Tomcat instances running behind an Apache frontend server (see guides for Confluence and JIRA). There are some benefits to keeping them separate:
- 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), particularly if you later want to install a third webapp not from Atlassian.
Offsetting this is the extra complexity of having to run Apache.
If you wish to proceed, please follow these instructions:
Step 1 - Download and extract WAR
- Download the Confluence WAR file
- Extract the downloaded zip file. It should extract to a folder called confluence-<version>. Inside this folder you'll find a folder called "confluence". Make a note of the absolute path to this directory (as you will need to use it later). Note: Do not copy the confluence folder to the webapps folder inside tomcat - this may cause Confluence to be deployed more than once.
- Open confluence/WEB-INF/classes/confluence-init.properties in a text editor
- 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 3 - Edit tomcat context descriptors
If you are deploying to JIRA version 3.3 or higher:
- Create a file called confluence.xml in your JIRA standalone's conf/Catalina/localhost directory (if you have set up a different hostname for your JIRA tomcat instance, please specify that instead of localhost)
- Open confluence.xml and add these lines:
<Context path="/confluence" docBase="c:/applications/confluence-2.1.3/confluence" debug="0" reloadable="true"> <Logger className="org.apache.catalina.logger.FileLogger" prefix="atlassian-confluence." suffix=".log" timestamp="true"/> </Context>
- For docBase specify the value you noted down earlier.
This is the full path to the confluence folder in your confluence-<version> installation folder, not the confluence home folder. It should look like: c:/<path to confluence installation>/confluence-<version>/confluence.
Otherwise (for older versions of JIRA):
- Open conf/server.xml in a text editor
- Find the block that begins: <Context path="" docBase="../atlassian-jira" debug="0" reloadable="true"> and ends with </Context> block.
- After the </Context>, append the following:
<Context path="/confluence" docBase="c:/applications/confluence-2.1.3/confluence" debug="0" reloadable="true"> <Logger className="org.apache.catalina.logger.FileLogger" prefix="atlassian-confluence." suffix=".log" timestamp="true"/> </Context>
- For docBase specify the value you noted down earlier.
This is the full path to the confluence folder in your confluence-<version> installation folder, not the confluence home folder. It should look like: c:/<path to confluence installation>/confluence-<version>/confluence.
- Remove the commons-logging-1.0.4.jar file from the confluence\WEB-INF\lib directory
Do not delete the existing Jira <Context> block. Insert the code above after the Jira <Context> block.
Step 4 - Modify your setenv.sh/bat (ONLY IF YOU ARE RUNNING A SUN MICROSYSTEMS JVM)
- Open JIRA's bin/setenv.sh/bat (.sh on unix, .bat on windows) in a text editor.
- Find the line that says: "... JAVA_OPTS=... " and add -XX:MaxPermSize=128m to its end.
The Java Virtual Machine sets aside a portion of memory as the "permanent space", for objects that it never expects to have to garbage-collect. Because JIRA and Confluence are both quite large applications, it is possible that this permanent space will be filled up. Increasing the application heap size will not help, because the permanent generation size is a separate setting.
 |
This flag is only supported on JVM's created by Sun Microsystems. If you include this flag while running another vendors JVM (such as JRocket, or IBM's JVM) they will not start. |
Step 5 - Restart the Server
- Shut down, and then restart the standalone server
- Confluence should now be accessible on the same server as your existing JIRA standalone, under the confluence directory.
For example, if your JIRA is running at http://jira.example.org:8080/, Confluence will be running on http://jira.example.org:8080/confluencereuse
When setting up the Confluence database do not reuse the JIRA database. Create a new database for Confluence.
Troubleshooting
When I try to send a test mail from Confluence, I get javax.mail.NoSuchProviderException: smtp
In some circumstances, Confluence will be unable to send email after being deployed in the same application-server as JIRA. If, when you try to send a test mail from the administration tool, you get the error: "javax.mail.NoSuchProviderException: smtp", please follow these instructions to fix it.
I have installed JIRA and Confluence in some other application server than Tomcat
These instructions only apply to the standalone Tomcat version of JIRA. Other application servers have not been tested in this configuration, and users have specifically reported difficulties deploying the two applications together in Orion Server and JBoss. We hope to resolve these issues soon.
Confluence is slow, and dumps enormous amounts of information to its logfiles
If you are seeing a large amount of DEBUG logging output, then ensure that you have removed the commons-logging-1.0.4.jar file from the confluence\WEB-INF\lib directory
The description for the installations works. BUT!
After restarting JIRA all the entries which have been contained (Users, Issues, Projects, ...) before installinge Confluence were gone. We had to import the data from a backup.

Posted by at Jan 19, 2005 09:50
|
Is there a companion document for adding JIRA to a standalone version of Confluence?

Posted by djsmitherman at Aug 15, 2005 16:33
|
There is currently no such document. For various reasons of configuration, adding Confluence to a JIRA standalone is generally easier and preferable to adding JIRA to a Confluence standalone.

Posted by cmiller at Aug 15, 2005 23:19
|
OK, I can do that. I think. How DO I do this? Is it something like this:
1. Shutdown Confluence and Tomcat
2. Install JIRA standalone
3. Start up JIRA standalone
4. Follow instructions for adding Confluence
That easy?

Posted by djsmitherman at Aug 16, 2005 14:09
|
Yes, that's the process to follow.

Posted by tom@atlassian.com at Aug 16, 2005 22:42
|
At least with JIRA 3.3.1, removing commons-logging-1.0.4.jar from confluence/WEB-INF/lib does not seem necessary. JIRA 3.3.1 uses Tomcat 5.5.9, which has the same commons-logging version as Confluence 1.4.3. If the commons-logging jar is removed from confluence/WEB-INF/lib, I find a huge amount of INFO logging in catalina.out. With commons-logging present, log messages are reduced to a reasonable level.

Posted by mccarrick at Sep 17, 2005 20:00
|
I did not want confluence to be under JIRA because, in my case, the audiences are different. I chose to do the following:
<Engine name="Catalina" defaultHost="wiki.mydomain.com">
<Host name="jira.mydomain.com" appBase="webapps" unpackWARs="true" autoDeploy="true">
<Context path="" docBase="${catalina.home}/atlassian-jira" reloadable="false">
<Resource name="jdbc/JiraDS" auth="Container" type="javax.sql.DataSource"
username="jirauser"
password="jira_password"
driverClassName="net.sourceforge.jtds.jdbc.Driver"
url="jdbc:_url_:jiradb"
validationQuery="Select 1"/>
<Resource name="UserTransaction" auth="Container" type="javax.transaction.UserTransaction"
factory="org.objectweb.jotm.UserTransactionFactory" jotm.timeout="60"/>
<Manager pathname=""/>
</Context>
</Host>
<Host name="wiki.mydomain.com" appBase="webapps" unpackWARs="true" autoDeploy="true">
<Context path="" docBase="${catalina.home}/../confluence-2.1.5a/confluence" reloadable="false">
<Logger classname="org.apache.catalina.logger.FileLogger" prefix="atlassian-confluence." suffix=".log" timestamp="true"/>
</Context>
</Host>
</Engine>
I have hooked both JIRA and Confluence to authenticate against our Active Directory (LDAP).
I hope this won't cause any integration problems.

Posted by awhitford at Apr 13, 2006 09:11
|
Is there a method to allow Confluence and Jira to share users?

Posted by pborowicz at Jun 12, 2006 15:08
|
Yes there is. Full instructions can be found here
Cheers,
Dave

Posted by dave@atlassian.com at Jun 12, 2006 20:30
|
I'd like a setup like that too, but I'm not sure if I can do the same on a Jira 3.6 standalone. Should I just wrap the <context> tag in confluence.xml with a <host> tag?

Posted by ingeman at Jun 20, 2006 07:18
|
Sure, that should work. You need to make sure the name in the host tag maps to your application server in your DNS.
If you have any issues, please raise a support request at http://support.atlassian.com.

Posted by mryall at Jun 23, 2006 03:12
|
I run JIRA standalone with a context path of "/jira", and I have the context path of Confluence set to "/confluence". The setup here works for me when I am access both JIRA and Confluence via "http://localhost:8080/...". However, I normally run JIRA behind Apache, with the appropriate ProxyPass settings and with "proxyHost" and "proxyPort" set in JIRA's "server.xml".
I expected this would also work for Confluence, that by changing "/jira" to "/confluence" in the URL, I would get Confluence instead of JIRA. However, it isn't working that way. JIRA works OK, but the Confluence URL returns an error 503 page (Service unavailable).
I'm a bit lost as to how to debug this any further. Can anyone suggest what is the appropriate way to have Apache running in front of both JIRA and Confluence? Thanks a lot in advance,
Cheers, Tony.

Posted by abcoates at Aug 29, 2006 17:27
|
Hi Tony,
You can try following our guide to using Apache and mod_proxy with Confluence. It should work pretty much as you say, but the configuration needs to be done in Apache's httpd.conf not server.xml.
If this doesn't help, please raise a support request, and we can help you from there.
Regards,
Matt

Posted by mryall at Sep 03, 2006 22:49
|
Hi Dave,
I think the link is dead...

Posted by blsof8bc at Dec 31, 2006 10:31
|
In Step 3 above it is not clear whether "2. Remove the commons-logging-1.0.4.jar file from the confluence\WEB-INF\lib directory" refers to JIRA version 3.3 & higher OR older versions of JIRA. This should be perhaps clarified better.

Posted by blsof8bc at Dec 31, 2006 10:49
|
Hi Martin,
Apologies for that, we've recently moved around/consolidated a lot of our documentation.
Here's the correct link: http://confluence.atlassian.com/display/DOC/Delegate+user+management+to+use+JIRA+logins.
Cheers,
Michelle

Posted by michelle@atlassian.com at Jan 01, 2007 18:21
|
Hi Martin,
Thanks for catching that.
I've now fixed that section on 'Otherwise (for older versions of JIRA):' for Step 3.
Hopefully that makes a little more sense now.
Please let us know otherwise.
Cheers,
Michelle

Posted by michelle@atlassian.com at Jan 01, 2007 18:53
|
Step 3 has typos. After a <Context ... /> tag that ends in "/>", you can't have "</Context>". You can only do that after a <Context ...> tag that ends in ">" rather than "/>".

Posted by abcoates at Jan 02, 2007 12:18
|
Sorry, please ignore that comment, I misread the XML. You *do* need the closing "</Context>" (of course) because of the "<Logger>" element within. Apologies. Cheers, Tony.

Posted by abcoates at Jan 02, 2007 12:38
|
I have installed JIRA version 3.7.1-#185 stand alone [evaluation license]. I then added the Confluence 2.3 WAR. I started the server using startup.bat and then configured both JIRA and Confluence. I then stopped the server using shutdown.bat and then started it again just to be sure everything was working fine.
I then ran service.bat install JIRA and the tomcat5 //US//JIRA --Startup auto and memory setting command so that the server will become a service.
Finally I started the service. Using the same URL's that I used for the manually started server, JIRA works fine but I get a 404-page not found error for Confluence.
I stopped the service, used the batch startup command, and not problems. Stop using the batch command and restart the service, JIRA but no Confluence.
So obviously I've missed a key step, but do not have a clue as to what it might be. Any suggests would be appreciated.

Posted by arvidj at Jan 09, 2007 17:27
|
Solved the problem. I had created a user specifically to run the service but had not granted the user full access to the drive where the Confluence data, attachments, etc., were located. This requirement is found at the bottom of the instructions for installing Confluence as a service.
So all is well now.

Posted by arvidj at Jan 09, 2007 17:44
|
Hi Arvid,
Glad to hear that you got it working.

Posted by dchui at Jan 09, 2007 19:36
|
We currently have separate installation of JIRA and Confluence on the same server. The way it was installed was that both have their own database tables on the same MySQL server, which prompts us to logon separately to JIRA and Confluence. What we want to achieve is to be able to get authenticated in Confluence when already logged in in JIRA, and vice versa. Is there a way to achieve this with our current setup, or do we have to install Confluence into JIRA to be able to have a single-sign to both?
Thanks

Posted by dudester at Mar 03, 2007 06:26
|
Hi,
You can achieve single sign-on in your current setup. When you talk of seperate databases, it sounds like your talking about Jira and Confluence sharing a user database http://confluence.atlassian.com/x/Ugs , but that isn't single sign on. For that, there is a product: Crowd. Please go here for more information: http://www.atlassian.com/software/crowd/

Posted by nicholas@atlassian.com at Mar 07, 2007 18:05
|
|