You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
Fedora Repository 3 Documentation
Page not found
|
Upgrading from 3.5 to 3.6
Version 3.6 does not require a database or resource index rebuild, nor does it require an upgrade to your configuration. In order to "swap in" the new version of the software, you may:
- 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 server/config/spring/akubra-llstore.xml into the new installation's server/config/spring/ directory.
- 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.6
- 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
|
#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))