Documentation for JIRA 6.3 EAP developer (EAP) releases only. Not using this? See below:
(JIRA 6.2.x documentation | JIRA OnDemand documentation | earlier versions of JIRA)

Skip to end of metadata
Go to start of metadata

To move JIRA from a non-Tomcat application server to Apache Tomcat, use one of the following methods:

Note

Icon

Regardless of which method you use, back up your data first and make sure you test JIRA on the new server before deploying it in production.

Method 1. Export and import the database

Follow the Migrating JIRA to Another Server instructions, installing the new version of JIRA on your new application server.

Method 2. Use your existing database

If you are using the same version of JIRA on the old and new (Apache Tomcat) application server, you do not have to export and re-import your JIRA database (as described in the instructions for Migrating JIRA to Another Server). You can use your existing database with the new application server.

However, you cannot simply copy the WAR file or expanded WAR directory from an existing JIRA WAR installation in the old application server to the new application server. This will not work.

To switch to a new (Apache Tomcat) application server, follow these instructions:

  1. Install JIRA on the new application server. (Refer to the instructions for your version of Apache Tomcat in the Installing JIRA WAR section.)
  2. Check that the JNDI location of the UserTransaction as declared in the entityengine.xml file is correct for Apache Tomcat.
  3. From System Info, check the modified files to see what customisations, if any, exist from the original installation. Consider these changes in your new server.
  4. Make sure you shut down the old server before you start up the new one.
  5. If you are running the new application server on a different machine to the old one, carry out the following actions as soon as you start the new server: