Upgrading Crowd via XML Data Transfer
Below are instructions on upgrading an existing Crowd installation to the latest version of Crowd, using the procedure that transfers your Crowd data via XML backup.
Before you being
- Decided on a recommended upgrade procedure for your database server and Crowd version
- Read the Release Notes for the version you are upgrading to.
- Read the Upgrade Notes for any versions you are skipping as well as the version you are upgrading to.
This method won't transfer the audit log to your upgraded version. To keep the audit log, use the automatic database upgrade instead.
Step 1. Export your Crowd Database to XML
- In the top-right corner, click > Backup.
- Follow the screen prompts to back up your Crowd database to an XML file. For full instructions, see our guide on backing up data.
Step 2. Shut down Crowd and All Integrated Applications
- Shut down Crowd and all Crowd-connected applications.
Step 3. Back Up your Crowd Files
- Use your database backup tools to back up your Crowd database and your CrowdID database. We highly recommend this step, in case something goes wrong during the upgrade process and you need to restore your data from backup.
Make backup copies of the following files:
- The crowd.properties file for the CrowdID application, located at
{CROWD_INSTALL}/crowd-openidserver-webapp/WEB-INF/classes/crowd.properties
— You will need to copy this file to your new Crowd installation. - Your Crowd JDBC Driver if you have configured Crowd with a database — You will need to copy this file to your new Crowd installation.
- Your Crowd Home directory, in the location specified in the
crowd-init.properties
file — Recommended in case something goes wrong during the upgrade process.
- The crowd.properties file for the CrowdID application, located at
- Rename your existing {CROWD_INSTALL} directory, because legacy files may cause problems if you unzip the new Crowd installation into an existing directory.
Step 4. Download and Re-Install Crowd
- Download Crowd.
- Unzip the downloaded archive into a directory of your choice.
- Make sure that your new {CROWD_INSTALL} directory has a different name from your old {CROWD_INSTALL} directory.
- Check your unzip program before extracting the downloaded archive – see the note on the Crowd installation front page.
- Do not use empty spaces in directory names.
- We will refer to this installation directory, where you unzipped the archive, as {CROWD_INSTALL}.
Specify a new Crowd Home directory for your new Crowd installation by editing the configuration file at {
CROWD_INSTALL}\crowd-webapp\WEB-INF\classes\crowd-init.properties
. The Crowd Home directory is where Crowd will store its configuration information. If you are using the embedded HSQL database, supplied for evaluation purposes, Crowd will also store its database in this directory. (Note however that the CrowdID database will be in the installation directory, not the Home directory.) To specify the Crowd Home directory:- Open the
crowd-init.properties
file. This is found at<crowd_install_directory>/crowd-webapp/WEB-INF/classes/crowd-init.properties
- Choose the appropriate line in the file, depending upon your operating system (see below).
- Remove the
#
at the beginning of the line. - Enter the name of the directory you want Crowd to use as its Home directory. For example,
Windows の場合
crowd.home=c:/data/crowd-home
Note: On Windows, make sure you use forward slashes as shown above, not backward slashes.
On Mac and UNIX-based systems:
crowd.home=/var/crowd-home
重要
Please, ensure that the Crowd Home directory will not match the Crowd installation directory AND it is writable by the user executing the initialization script.
- Save the
crowd-init.properties
file.
Make sure you point the new Crowd installation to a new Crowd Home directory, so that Crowd will do a clean installation. Do not point it at your existing Crowd Home directory.
- Open the
- Copy the following files, saved in Step 3 above, to your new Crowd installation folder:
- Copy the
crowd.properties
file for the CrowdID application to your new {CROWD_INSTALL}/crowd-openidserver-webapp/WEB-INF/classes
directory. - Copy your Crowd JDBC Driver if you have configured Crowd with a database.
- Copy the
Step 5. Start Crowd and Run the Setup Wizard
- Run the start-up script, found in your {CROWD_INSTALL} directory:
start_crowd.bat
(Windows)。start_crowd.sh
for Mac and Unix-based systems.
- Point a web browser at
http://localhost:8095/crowd
where you will see the Crowd Setup Wizard. - Enter your license key on the 'License' screen, as described in the instructions on the Setup Wizard.
- When asked for your Installation Type, choose 'Import data from an XML Backup'. This step is required, to import your Crowd data from the XML file which you created in Step 1 above.
- The Setup Wizard will now ask you to configure your database. Supply the JNDI datasource or JDBC connection details of a new database.
- The Import Existing Crowd Data screen will appear. Enter the location of your XML backup file and click 'Continue'.
- The Setup Wizard is now complete. You are now ready to log in to the Crowd Administration Console, using your administrator account from your earlier Crowd installation.
Step 6. Update your Integrated Applications
- If you have installed Crowd on a new server, or changed Crowd's URL or port number, you will also need to edit the
crowd.properties
file in each integrated application accordingly. - If you are using CrowdID with an external database, you will need to use the manual JNDI datasource configuration method to configure an external database connection.
- If you are using CrowdID with the default HSQL database, copy the
database/
directory from your old installation directory into your new installation directory. Please note that the HSQL database is not suitable for production environments. Connecting CrowdID to a Database describes how to migration to an enterprise database.
トラブルシューティング
If you have any problems during upgrade, please raise a support request at https://support.atlassian.com/ja/ and attach your atlassian-crowd.log
file so that we can help you find out what's gone wrong.