Upgrading from 3.5+ to 3.
...
7
Warning | ||
---|---|---|
| ||
3.5 to 3.6 7 Upgrade Instructions are a work-in-progress. |
...
- Shut down your old 3.5 repository
- Install the newer version of Fedora in a different location, but before starting it:
- Copy your old server/config/fedora.fcfg file into the new installation's server/config/ directory.
- Copy your old bean definitions under server/config/spring /akubra-llstore.xml into the new installation's server/config/spring/ directory.
- 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 .
- 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)
- Start the new instance of Fedora for the first time.
- 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)
- Shut down your repository
- Run the Policy Index Rebuilder.
- Restart your repository
Upgrading from 3.x to 3.
...
7
Warning | ||
---|---|---|
| ||
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 will be provided in a future releasecan be built from source available at https://github.com/fcrepo/fcrepo-store . |
- Shut down your old 3.x repository
- Install the newer version of Fedora, but before starting it, modify the new fedora.fcfg so that:
- It points to your previous 3.x database
- The object and datastream paths point to your previous 3.x locations
- Note: Due to the Mulgara version upgrade, if you have enabled the Resource Index previously, it will need to be rebuilt. Therefore, it is unnecessary to point the resource index configuration to the old location.
- If you were using Akubra in 3.5, copy your old server/config/akubra-llstore.xml file into the new installation's server/config/spring/ directory.
- If you are using FeSL AuthZ, configure the Policy Index
- Start the new repository for the first time.
- Shut down the new repository.
- If you have previously made changes to the repository-wide XACML policies, copy them into the new repository's XACML directory.
- If you previously enabled messaging, and there were messages from your old repository that have not yet been delivered, copy its activemq-data directory over the new activemq-data directory in your new install.
- Run the Resource Index Rebuilder.
- If you are using FeSL and are using a different policy index configuration to your existing installation, run the Policy Index Rebuilder.
- Restart the new repository