Confluence のアップグレード

This document outlines the procedures you need to follow to upgrade from one version of Confluence to another. You can download the latest version of Confluence from here. Note that only users with current software maintenance may perform the upgrade.

If you are running Confluence on a cluster, please see Upgrading a Confluence Cluster instead of this document.

If you are planning to change to a different database, we recommend that you complete the upgrade first. Then follow the instructions on migrating to a different database.

Step 1: Backing up

Before you begin the upgrade, you must back up the following:

1. Your Confluence Home Directory (see Important Directories and Files for how to locate this).
2. Your Confluence Install Directory (if you are using Confluence Standalone) or your Confluence webapp (if you are using Confluence EAR-WAR).
3. If you are not using the embedded database, perform a manual backup of your database before proceeding with the upgrade.

Step 2: Things you need to check

1. Check the release notes for the new version of Confluence you are installing, plus the release notes for any major versions you are skipping, to see if there are any upgrade instructions specific to the new version(s).
2. If you are not using Confluence Standalone, check the Application Server Configuration Guide for your specific application server, to see if there is anything extra you will need to do to get Confluence running. For example:
   • Resin 3 users will need to update web.xml.
3. Note which plugins are currently installed/enabled.

Step 3: Performing the upgrade

1. Confluence をシャットダウンします。
2. Download Confluence Standalone or Confluence EAR-WAR. (For information about the difference between the two, please see the Installation Guide.)
3. Unzip the downloaded file. You should now have a new directory called confluence-<version>, e.g. confluence-2.6.0-std. We will now refer to this as the <Install-Directory>.
4. Edit the <Install-Directory>\confluence\WEB-INF\classes\confluence-init.properties file and update 'confluence.home' to point to your existing Confluence Home directory. (Make sure you have first backed this up as described in Step 1 above.) For more details about editing the confluence-init.properties file, please see 'Set Your Home Directory' in the Standalone Installation Guide.
5. If you are using Confluence EAR-WAR, and are using Tomcat, you need to update either your confluence.xml or server.xml (depending on where you have defined the Confluence context descriptor) to point to the location of the new Confluence installation.
6. If you are using the standalone version of Confluence and:
   1. you are running it as a Windows service: use bin\tomcat5w.exe to remove and re-install the Tomcat service.
   2. you are not using the embedded database: copy the jdbc driver jar file from your old standalone Confluence installation to the new Confluence standalone installation. The jdbc driver jar should be in either the <Install-Directory>/common/lib directory or the <Install-Directory>/confluence/WEB-INF/lib directory.
7. If you have delegated your user management to JIRA, LDAP or any other external user management system, copy the following files from your old Confluence installation to your new Confluence installation:
   • <Install-Directory>/confluence/WEB-INF/classes/osuser.xml.
   • <Install-Directory>/confluence/WEB-INF/classes/atlassian-user.xml (if you are upgrading from Confluence 2.2 or later).
8. If you are using Confluence EAR-WAR, restart your application server.
9. Launch your new Confluence. (You should not see the Setup Wizard.)
   Please note that Confluence will need to re-index attachments and this can take 5-10 minutes. Please wait until Confluence has finished indexing the attachments before trying to access Confluence via your web browser.
10. Run the attached set of SQL statements against your Confluence database to create indexes. These indexes are important for good performance. It is recommended that you pass this file to your DBA to run. If you do not have a DBA, please refer to our basic instructions. If your database reports that any of these indexes already exists, you can safely ignore these warnings.
11. Access Confluence via your web browser and confirm that all your spaces and pages are present and everything looks normal. You should see the new Confluence version number in the page footer.

次のステップ

Consider any customisation you have applied to your system and other special configuration:

• If you had previously installed Confluence/Tomcat as a Windows service, un-install the service (to ensure that the old Confluence cannot start automatically when the server restarts) and reinstall the new one. For details please see Start Confluence automatically on Windows as a Service.
  
  
• If you were previously running Confluence on a non-standard port, edit your new  <Install-Directory>\conf\server.xml  file as described in Change listen port for Confluence Standalone.
  
  
• If you were previously using any plugins, install the latest compatible version and disable any plugins that are incompatible with your new version of Confluence. The easiest way to do this is to use the Plugin Repository in the Confluence Administration console.
  
  
• If you are using any customised themes, please check that they are displaying as expected. Some further customisation may be required to ensure compatibility with your new version of Confluence.
  
  
• If you had previously customised the default site or space layouts, you will need to reapply your changes to the new defaults as described here.
  
  
• If you had previously modified the Confluence source code, you will need to reapply your changes to the new version.
  
  
• If you were previously running Confluence over SSL, you will need to reapply your configuration as described in Adding SSL for Secure Logins and Page Security.
  
  
• If you had previously modified the memory flags (Xms and Xmx) in either the <Install-Directory>\bin\setenv.sh or setenv.bat file, you may want to make the modifications in your new installation. The parameters are specified in the JAVA_OPTS variable.

トラブルシューティング

If you need assistance with the upgrade, please log a support request at http://support.atlassian.com.

Related documentation

Confluence 2.6 Installation Guide
Important Directories and Files
Site Backup and Restore
Database Configuration
How to run a SQL script on your database