Documentation for JIRA 4.3. Documentation for other versions of JIRA is available too.

To move JIRA from one application server to another, for example from WebSphere to Tomcat, use one of the following methods:

Note

Regardless of which method you use, backup 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 Upgrading JIRA instructions, installing the new version of JIRA on your new application server.

Method 2. Use your existing database

If you are using the same major version (e.g. 4.0.x) of JIRA on the old and new application server, you do not have to export your data. 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 old JIRA EAR/WAR version in the old application server to the new application server. This will not work.

Follow these instructions:

  1. Install JIRA on your new application server (see Installing JIRA WAR-EAR). As part of these instructions:
    • When you configure the JDBC datasource in your new server, use the settings for your existing database.
    • Check that the JNDI location of the UserTransaction as declared in the entityengine.xml file is correct for your server.
  2. 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.
  3. Make sure you shutdown the old server before you startup the new one.
  4. 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:



See our Getting Help page for details.



Raise an issue for our developers.



See answers from the community.



Tweet, blog and update our documentation.

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