Fedora Upgrade and Migration Guide

1. Upgrading from Fedora 2.2.2

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

1. Stop the webapp container in which Fedora is running.
2. Download fedora-2.2.3-upgrade.jar and run it with the command: java -jar fedora-2.2.3-upgrade.jar
3. Restart the webapp container.

NOTE: One of the changes with Fedora 2.2.3 was to update the bundled Tomcat instance to version 5.5.26, due to a shutdown bug with Tomcat. The simple process above will not automatically make this change to your existing installation. It is not required, but if you would like to upgrade to Tomcat 5.5.26, we recommend performing a full install of Fedora 2.2.3 instead.

2. Upgrading from Fedora 2.2.1

Follow the instructions for upgrading from 2.2.2 above, but prior to step 2:

• Download fedora-2.2.2-upgrade.jar and run it with the command: java -jar fedora-2.2.2-upgrade.jar

3. Upgrading from Fedora 2.2

Follow the instructions for upgrading from 2.2.2 above, but prior to step 2:

• Download fedora-2.2.1-upgrade.jar and run it with the command: java -jar fedora-2.2.1-upgrade.jar
• Download fedora-2.2.2-upgrade.jar and run it with the command: java -jar fedora-2.2.2-upgrade.jar

2. Upgrading from Fedora 2.1.1

Upgrading from Fedora 2.1.1 does not require a rebuild. However, there are important changes to the packaging and configuration between 2.1.1 and 2.2.3. Notably, the Fedora Configuration File (fedora.fcfg) and the Fedora Web Deployment Descriptor (web.xml) have changed.

1. Backup

   It is highly recommended that 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.3

   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

Follow the same steps as above for upgrading from 2.1.1.

4. Upgrading From Fedora 2.0

Follow the same steps as above for upgrading from 2.1.1.

If you use the Resource Index, you will need to run a rebuild when finished. For instructions, see 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.