手動による Jira アプリケーションのアップグレード

• Read about the new version - Review the release notes and upgrade notes for the version of Jira that you are upgrading to. See our Release notes for Jira Server. If you plan to skip a few Jira versions during your upgrade, we strongly recommend that you read the upgrade guides for all major versions between your current version and the version to which you are upgrading.
• ライセンスの確認 – お客様の ライセンスサポート期間 が有効期間内であることを確認します。
• 既知の問題の確認 - 影響を与える新しいバージョンの問題点を検索するには、JIRA ナレッジベースを利用します。
• 互換性の確認:
  
  • Confirm that your operating system, database, other applicable platforms and hardware still comply with the requirements for Jira 7.1. The End of Support Announcements page also has important information regarding platform support for future versions of Jira.
  • If you have installed Jira plugins (i.e. not included with Jira), verify that they will be compatible with the version of Jira you are upgrading to. You can find a plugin's compatibility information from the plugin's home page on the Atlassian Marketplace.
  • Some anti-virus or other Internet security tools may interfere with the Jira upgrade process and prevent the process from completing successfully. If you experience or anticipate experiencing such an issue with your anti-virus/Internet security tool, disable this tool before proceeding with the Jira upgrade.
• Prestaging and testing your new version of Jira - We strongly recommend performing your upgrade in a test environment first. Do not upgrade your production Jira server until you are satisfied that your test environment upgrade has been successful.
  • テスト環境におけるアップグレードで解決できない問題がある場合、弊社サポートサイトで課題を作成してサポートを受けてください。
  • If you have any problems during the upgrade of your production Jira server, do not allow your users to start using this server. Instead:
    
    • Continue to use your old Jira server — this will help ensure that you do not lose production data.
    • また、サポートサイトで課題を作成していただくことで、弊社はアップグレードに伴う様々な問題をお客様が解決できるよう支援できます。
    事前ステージングとテストに関する説明

    1. If you want to use a copy of your production data when you test the upgraded Jira system, make a copy of your production database using your native database backup tools. See Backing up data. You can alternatively skip this step and use a new database for testing.

    2. Install the version of Jira you want to upgrade to onto a system you can use for testing (use either a test server or a separate directory on an exisitng system). This will become your new production system after you complete the upgrade process. Follow the instructions here to install a new version of Jira: Installing Jira applications.

    3. Migrate any customizations you use in your production system. Follow the instructions in step 3.4 (Migrate your existing Jira configurations over to your new Jira installation) in the "Migrating Jira to another server" page.
    4. Connect the new version of Jira to the copy of the production database (not the existing production database) or a new testing database. See Connecting Jira to a database.
    5. Start the new version of Jira. See this Knowledge Base article about how to test mail settings without accidentally sending notifications to users from the test system: How to Prepare a Development Server's Mail Configuration.
    6. Install any plugins that you use in your existing production version of Jira. Some plugins have different compatibility for different Jira vesions, so this step will ensure that your plugins are updated for this new Jira version.
    7. Re-index Jira so the new plugin information is captured in the index.
    8. Check out the features and functionality you use in the new version to understand how they behave and how any changes will impact your team. It can be very helpful to have a group of users look at the new system and carry out their usual tasks to make sure they won't run into any issues when the new version is in production.
       When you are ready to begin the process of migrating your production data to this new version, shut down Jira (for example, by executing either the /bin/stop-jira.sh or \bin\stop-jira.bat file in your Jira application installation directory, or by stopping the Jira service).

2.1 Stop users from updating Jira data

During the upgrade process, you'll export Jira's database from your existing Jira installation (via an XML backup) and then restore this backup into a new Jira installation. To ensure that the data in the XML backup is consistent with the latest data in the system, you must temporarily restrict access to Jira so users can't update the data. Refer to the Preventing users from accessing Jira applications during backups page for more information.

 注意してください！整合性のない XML バックアップを使って復元することはできません！

2.2 データベースのバックアップ

Perform an XML backup of your existing Jira installation's external database. For large Jira installations, this process may require several hours to complete.

2.3 Back up your Jira home directory

1. Jira をシャットダウンします。
2. Locate the Jira home directory. You can find information about the location of the directory by navigating to the <jira-application-dir>/WEB-INF/classes/jira-application.properties file in your Jira application installation directory. Alternatively, you can open the Jira configuration tool to see the directory that is set as your Jira Home.
3. 設定ファイルに記録されているディレクトリに移動して、別のディレクトリにそのバックアップを作成します。
4. バックアップの完了直後に元のフォルダーから <jira-home>/dbconfig.xml ファイルを削除します。

2.4 Back up your attachments and index directories if located outside your Jira home directory

添付ファイルとインデックス ディレクトリが JIRA ホーム ディレクトリ外にある場合は、この２つのディレクトリのバックアップをそれぞれ作成する必要があります。ご使用の実装でこれらのディレクトリの場所を見つける方法については、次のページで説明しています。

• Your attachments directory — Refer to Configuring file attachments page in the documentation for your version of Jira.
• Your index directory — Refer to Search indexing page in the documentation for your version of Jira.

Also refer to Backing up data for more information about backing up attachments in Jira.

2.5 Back up your Jira installation directory

The 'Jira Installation Directory' is the directory into which the Jira application files and libraries were extracted when Jira was installed.

ディストリビューションのセットアップ方法

1. Open the Jira configuration tool.
2. Click the Jira Home tab.
3. Update the Jira Home Directory field:
   
   • If your Jira 7.1 installation is on a new server, update the Jira Home Directory field to the path of your copied Jira Home directory.
   • If your Jira 7.1 installation is on the same server, update the Jira Home Directory field to the path of your existing Jira Home directory.
     For more information about this directory, see Jira home directory.

You can also set your Jira Home Directory's location by defining an operating system environment variable JIRA_HOME. This value of this variable takes precedence over the value of the jira.home property in the jira-application.properties file in your Jira installation directory. See Setting your Jira home directory for details.

Follow the appropriate 'Connecting Jira to...' instructions for your database from stage 2, although from stage 4 of that procedure, be aware of the yellow note below:

• Connecting Jira to PostgreSQL
• Connecting Jira to MySQL
• Connecting Jira to Oracle
• Connecting Jira to SQL Server 2008

組み込み H2 データベースを使用中の場合は、新しいデータベースを作成する必要はありません。

For each file you have modified in your existing Jira installation, you need to manually edit each equivalent file in your new Jira installation and re-apply your modifications. If a file is not present in your new Jira installation (for example, osuser.xml in recent Jira versions), then simply copy that file over to your new Jira installation.

The table below lists the most commonly modified files and their locations within your Jira Installation Directory:

バージョン固有のアップグレードに関する注意事項には、一般的に変更されるファイルで変更された可能性のあるプロパティに関する詳細も含まれます。

上記のファイル以外にも、アップグレードのプロセスにて以下の設定を考慮・実行する必要があります。

• Using Jira with Atlassian's Crowd? — If you are using Crowd with Jira, configure your new Jira to talk to Crowd as described in Integrating Crowd with Jira.
  • Remember to configure Crowd to grant Jira's new hostname/IP access.
• Allocating additional memory to Jira — If you had previously allocated additional memory to Jira, do the same for your new Jira instance. For more information refer to Increasing Jira memory.
• Plugins — For any plugins that you had installed in your old Jira, download the plugin version for your new version of Jira from the http://plugins.atlassian.com site.
• Character encoding — Ensure that character encoding (i.e. locale) is the same on the new and old locations. Your new version of Jira may not function correctly if attachments are moved between two system with incompatible encoding.
• Customizations — If you had made any customizations (code, templates or configuration files), copy over compatible versions of these changes to the new Jira. (The developers within your organization who made the customizations to your old version will need to build and test equivalent changes for the new version, and provide you with the files to copy to your upgraded Jira installation.)
• (Optional) Running Jira on a different port — If your new Jira is installed on the same machine as your old Jira, you may wish to make sure it runs on a different port (in case you ever need to restart your old Jira). See Changing Jira's TCP ports for details.

1. Verify that your old Jira installation is shut down — if this Jira server is still operating, shut it down.
2. Start up your new version of Jira by follow the Starting Jira instructions.

To import your old Jira data into your new Jira:

1. Restore the attachments directory that you backed up previously into the attachments directory of your new Jira. (See Restoring data.)
2. Jira を起動します。
3. セットアップ ウィザードで [Import existing data (既存のデータをインポート)] を選択します。
4. In the File name field, specify the XML backup file you created previously during the export process (above). The zipped file should contain two xml files: activeobjects.xml and entities.xml. Both of these files must be included in the zipped file for the import process to work.
    Avoid passing through a proxy when performing an XML restore, especially if your Jira instance is very large. Using a proxy may cause timeout errors.
5. Access Jira via your web browser again and log in using a username from your previous Jira installation.
6. Take a quick look around your Jira site to confirm that your projects and issues are present and everything looks normal. You should see the new Jira version number in the page footer.