Page History

...

If you don't want to use the default implementation or configuration options, you must configure the LLStore module before starting Fedora for the first time. Configuration is done within the server/config/fedora.fcfg file, by modifying the class and param values as appropriate for the LLStore implementation you are plugging in:

<module role="fedora.server.storage.lowlevel.ILowlevelStorage"
        class="org.example.SomeLLStoreModule">
  <param name="someParam" value="someValue"/>
  <!-- etc -->
</module>

...

To use this plug-in, replace the existing LowlevelStorage module in fedora.fcfg with the following:

<module role="fedora.server.storage.lowlevel.ILowlevelStorage"
   class="fedora.server.storage.lowlevel.akubra.AkubraLowlevelStorageModule"/>

Then modify the akubra-llstore.xml file as appropriate. This is a Spring bean configuration file and is where you tell Fedora which Akubra BlobStore implementation to use and how it should be configured.

...

The S3 Low Level Storage is not distributed in binary form. You may obtain it from our legacy Subversion repository via:

svn co https://svn.fedora-commons.svn.sourceforge.net/svnroot/fedora-commons/incubator/AmazonS3Storage

...

Fedora's Rebuild Utility (fedora-rebuild) provides repository administrators with an automated way to reconstitute Fedora's higher-level indexes (the SQL database and the Resource Index) when upgrading Fedora, migrating to another SQL database, or recovering from inconsistencies.

Historically, the only Low Level Storage implementation that supported this utility was the Filesystem Low Level Storage module that came bundled with Fedora. As of Fedora 3.2, the rebuilder now works with any LLStore implementation that supports the new IListable interface.

Currently, the only known LLStore implementations that support this interface (and thus can be used with the rebuild utility) are the Akubra and Filesystem LLStore modules released with Fedora 3.2.