Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3
Section
Column

Anchor
top
top

This document describes how to perform any of the following:

  • migrate/upgrade to
    Excerpt Include
    _Major Release Number
    nopaneltrue
    _Major Release Number
    nopaneltrue
    on different server hardware or in a different server environment — for example:
    • a new operating system that will run JIRA,
    • new locations for storing your index and/or attachments, or
    • a new database or database system that will store JIRA's data.
  • upgrade to
    Excerpt Include
    _Major Release Number
    nopaneltrue
    _Major Release Number
    nopaneltrue
    from a version of JIRA prior to 4.0.0.

(tick) If you are already using:

  • JIRA Standalone version 4.3.0 or later on Linux or Windows, please note the recommended procedure (see Upgrading JIRA) for upgrading to
    Excerpt Include
    _Major Release Number
    nopaneltrue
    _Major Release Number
    nopaneltrue
    .
  • JIRA Standalone version 4.0.0 – 4.2.x (or 4.3.x on Solaris) or JIRA WAR version 4.0.0 or later, please note the manual procedure (see Upgrading JIRA Manually) for upgrading to
    Excerpt Include
    _Major Release Numbernopaneltrue
    _Major Release Number
    nopaneltrue
    .
Include Page
_Upgrade Hint
_Upgrade Hint
Column
width500px
Panel

On this page:

Table of Contents
maxLevel4
minLevel1

...

Include Page
_Preparing to Upgrade JIRA
nopaneltrue
_Preparing to Upgrade JIRA
nopaneltrue

Anchor
backingup
backingup

2. Backing Up

...

Anchor
copyjirahome
copyjirahome
If your new
Excerpt Include
_Major Release Numbernopaneltrue
_Major Release Number
nopaneltrue
installation is on a new server, copy your existing JIRA Home Directory from the old server to the new server before proceeding.

If your new

Excerpt Include
_Major Release Numbernopaneltrue
_Major Release Number
nopaneltrue
installation is a Standalone distribution, you can:

  1. Open the JIRA Configuration Tool.
  2. Click the 'JIRA Home' tab.
  3. Update the 'JIRA Home Directory' field as follows:
    • If your
      Excerpt Include
      _Major Release Number
      _Major Release Number
      nopaneltrue_Major Release Number
      installation is on a new server, update the 'JIRA Home Directory' field to the path of your copied JIRA Home directory.
    • If your
      Excerpt Include
      _Major Release Numbernopaneltrue
      _Major Release Number
      nopaneltrue
      installation is on the same server, update the 'JIRA Home Directory' field to the path of your existing JIRA Home directory.
      (info) For more information about this directory, see JIRA Home Directory.

...

  1. Edit the jira-application.properties file located within the <jira-application-dir>/WEB-INF/classes subdirectory of your new
    Excerpt Include
    nopanel
    _Major Release Numbertrue
    _Major Release Number
    nopaneltrue
    Installation Directory JIRA Installation Directory.
  2. Update the jira.homeproperty in this file to the path of the new JIRA Home Directory:
    • If your
      Excerpt Include
      nopanel
      _Major Release Numbertrue
      _Major Release Number
      nopaneltrue
      installation is on a new server, update the jira.home property to the path of your copied JIRA Home directory.
    • If your
      Excerpt Include
      _Major Release Number
      nopaneltrue
      _Major Release Number
      nopaneltrue
      installation is on the same server, update the jira.home property to the path of your existing JIRA Home directory.
      (info) For more information about this directory, see JIRA Home Directory.
  3. Remove the '#' at the beginning of this line (so that JIRA no longer regards this line as a comment).
  4. Save your updated jira-application.properties file.

...

File

JIRA Standalone location

JIRA WAR location

Description

jira-application.properties

atlassian-jira/WEB-INF/classes

webapp/WEB-INF/classes

Location of the JIRA Home Directory and Advanced JIRA Configuration in JIRA 4.3.x and earlier.

Any custom property values defined in the jira-application.properties file of your existing JIRA 4.3.x (or earlier) installation must be migrated across to the jira-application.properties file of your new

Excerpt Include
_Major Release Numbernopaneltrue
_Major Release Number
nopaneltrue
installation before you start your new JIRA installation.

Upon starting your new JIRA installation, any custom property values in the jira-application.properties file will automatically be migrated across to either the JIRA database or jira-config.properties file. jira.home is the only property of the jira-application.properties file subsequently used by JIRA.

setenv.bat (Windows) or setenv.sh (Linux)

bin

Application Server's bin directory

Increasing JIRA Memory

osuser.xml
(not required if upgrading from JIRA 4.3.0 or later)

atlassian-jira/WEB-INF/classes

webapp/WEB-INF/classes

Modified if you have integrated LDAP with JIRA, integrated Crowd with JIRA, or if you are using a custom form of external user management or user authentication.

seraph-config.xml

atlassian-jira/WEB-INF/classes

webapp/WEB-INF/classes

Modified if you have integrated Crowd with JIRA.

server.xml

conf

Application Server's conf directory

Modified in the following situations:

...

Note
titleDo not restart your old JIRA installation...

If your new

Excerpt Include
_Major Release Numbernopaneltrue
_Major Release Number
nopaneltrue
installation is on the same server as your old one, it may still be configured to use the same JIRA Home directory as your new JIRA installation. Running two separate JIRA installations which share a common JIRA Home directory can lead to serious data corruption.

Nevertheless, we recommend that you do not delete any aspect (or backed up component) of your old JIRA installation, until you are satisfied that your upgraded JIRA installation is functioning as expected.

...

Include Page
_Post Upgrade Checks and Tasksnopaneltrue
_Post Upgrade Checks and Tasks
nopaneltrue

Congratulations! You have completed your JIRA migration/upgrade.

...