Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Upgrading from 3.5+ to 3.

...

8

Warning
titleWork-in-progress

3.5 to 3.7 8 Upgrade Instructions are a work-in-progress.

...

  1. Shut down your old 3.5 repository
  2. Install the newer version of Fedora in a different location, but before starting it:
    1. Copy your old server/config/fedora.fcfg file into the new installation's server/config/ directory.
    2. Copy your old bean definitions under server/config/spring into the new installation's server/config/spring/ directory.
    3. Edit one of the bean definitions to include an object cache. An example can be seen in the 3.7.0 source at https://github.com/fcrepo/fcrepo/blob/master/fcrepo-server/src/main/resources/fcfg/server/doreader-cache.xml .
    4. If you have previously made changes to the repository-wide XACML policies, copy them into the new repository installation's data/fedora-xacml-policies directory (you will need to create this directory)
  3. Start the new instance of Fedora for the first time.
  4. If you are using FeSL and are using a different policy index configuration to your existing installation (i.e. you are no longer using DB XML, the only option available for 3.4.x)
    1. Shut down your repository
    2. Run the Policy Index Rebuilder.
    3. Restart your repository

Upgrading from 3.x to 3.

...

8

Warning
titleAkubra low-level storage

As of Fedora 3.4, Akubra is the default low-level storage implementation. Akubra is not backwards-compatible with the datastream and object storage from previous releases, so when upgrading ensure you use the same low-level storage implementation as your existing installation. Your existing install.properties file will specify llstore.type as either legacy-fs or akubra, the same option should be used for your new installation. A limited migration utility to migrate from legacy low-level storage to Akubra can be built from source available at https://github.com/fcrepo/fcrepo-store .

...