Fedora Upgrade and Migration Guide

1. Upgrading from Fedora 2.2.1 to Fedora 2.2.2

We have developed a utility to make this process as quick as possible.

1. Download fedora-2.2.2-upgrade.jar from Sourceforge.
2. Stop the webapp container in which Fedora is running.
3. Run the upgrade utility: java -jar fedora-2.2.2-upgrade.jar and follow the prompts.
4. Restart the webapp container.

NOTE: Although the Fedora Administrator Java application will be upgraded as part of this process, existing tools and services that use fedora-client.jar version 2.2.1 do not need the updated version of this library in order to continue working properly with your upgraded server.

1. Upgrading from Fedora 2.2 to Fedora 2.2.2

For this upgrade, you will need to download and run two separate upgrade utilities, as follows:

1. Download fedora-2.2.1-upgrade.jar from Sourceforge.
2. Download fedora-2.2.2-upgrade.jar from Sourceforge.
3. Stop the webapp container in which Fedora is running.
4. Run the first upgrade utility: java -jar fedora-2.2.1-upgrade.jar and follow the prompts.
5. Run the second upgrade utility: java -jar fedora-2.2.2-upgrade.jar and follow the prompts.
6. Restart the webapp container.

NOTE: Although the Fedora Administrator Java application will be upgraded as part of this process, existing tools and services that use fedora-client.jar version 2.2 or 2.2.1 do not need the updated version of this library in order to continue working properly with your upgraded server.

2. Upgrading from Fedora 2.1.1 to Fedora 2.2.2

Upgrading from Fedora 2.1.1 to Fedora 2.2.2 does not require migration of objects or rebuilding of the Resource Index. However, there are important changes to the packaging and configuration between 2.1.1 and 2.2.2. Notably, neither the Fedora Configuration File (fedora.fcfg) nor Fedora Web Deployment Descriptor (web.xml) are compatible with Fedora 2.2.2.

1. Backup

   It is highly recommended you backup your existing Fedora repository.

2. Use your database's administrative tool or SQL command line utility to rename the "do" table to "dobj". This is normally done via the SQL command: ALTER TABLE do RENAME TO dobj
3. Install Fedora 2.2.1

   Review the Installation and Configuration Guide. Note the following critical steps of the installation process:

   1. When prompted for the installation type, select "custom".

   2. When prompted for the Fedora home directory, DO NOT select the Fedora home directory of your previous installation: select a new directory.

   3. When prompted for the Servlet engine, if you select an existing Tomcat installation, DO NOT select the servlet container of your previous Fedora installation.

      If you select an existing servlet container, please make sure it is not running (or, ensure that it is not configured to automatically deploy web applications).

   4. When prompted for the Database, select the database (i.e., mysql, oracle, etc.) you used with your previous installation of Fedora.

      Use the same database username, password, JDBC url, and Driver Class used in the previous Fedora installation (refer to your old fedora.fcfg if needed).

4. Post install, edit your new Fedora Configuration File ($FEDORA_HOME/server/config/fedora.fcfg).

   Copy the following parameter values from your old fedora.fcfg to your new fedora.fcfg:

   1. module.fedora.server.storage.lowlevel.ILowlevelStorage.object_store_base
   2. module.fedora.server.storage.lowlevel.ILowlevelStorage.datastream_store_base
   3. module.fedora.server.resourceIndex.ResourceIndex.level
   4. datastore.localKowariTriplestore.path

If you made any customizations to your previous fedora.fcfg, you may apply them now.

3. Upgrading From Fedora 2.1 to Fedora 2.2.2

Follow the same steps as above for upgrading from 2.1.1.

4. Upgrading From Fedora 2.0 to Fedora 2.2.2

When moving from Fedora 2.0 to Fedora 2.2.1, you will be able to do a simple software upgrade without having to migrate digital objects via a mass export and ingest. After installing Fedora 2.2.2, you can configure it to point to your existing repository datastores (both the existing repository directory storage locations and the existing relational database). This involves changing parameters in the Fedora 2.2.2 server configuration file (fedora.fcfg) that define the storage directory paths and database location.

Note that the Resource Index model changed between 2.0 and 2.1, hence a rebuild of the Resource Index is necessary if upgrading from 2.0 to 2.2.2. See the instructions for rebuilding the Resource Index.

5. Upgrading from versions prior to 2.0

To upgrade from a Fedora version prior to 2.0, you must first migrate to version 2.0, then follow the appropriate upgrade steps above.