Here is found details of the locations and purposes of the Fedora 4 configuration files. For details on how to enable and configure these options, see this page. |
Fedora RESTful HTTP API uses the open source Jersey RESTful Web Services framework that provides support for JAX-RS APIs and serves as a JAX-RS (JSR 311 & JSR 339) Reference Implementation. The jersey servlet dispatcher is configured in web.xml as follows:
<servlet>
<servlet-name>jersey-servlet</servlet-name>
<servlet-class>org.glassfish.jersey.servlet.ServletContainer</servlet-class>
<init-param>
<param-name>javax.ws.rs.Application</param-name>
<param-value>org.fcrepo.http.commons.FedoraApplication</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet> |
The following spring files exist in a directory as configured in web.xml, which contains a context-param element with param-name "contextConfigLocation". The param-value points to a spring context configuration file "WEB-INF/classes/spring/repository.xml". This configuration file imports a settings file located in the same directory or the file specified by system property {{fcrepo.spring.configuration}}. Note that these files are in the source tree under fcrepo-webapp/src/main/resources/spring and copied to WEB-INF/classes upon build.
fcrepo.spring.configuration or the provided configuration file fcrepo-config.xml <!-- Master context for fcrepo4. -->
<import resource="${fcrepo.spring.configuration:classpath:/spring/fcrepo-config.xml}"/> |
This is where you configure your Fedora instance, including:
fcrepo.modeshape.configuration system property.It is recommended to use the provided fcrepo-config.xml as a starting point for your customization.
Fedora 4 uses Modeshape, a JCR implementation. We distribute a handful of known-good configurations for Modeshape and Infinispan, although we anticipate configuration tuning for deployment environments will be common.
http://docs.jboss.org/infinispan/5.3/configdocs/
These configuration files are copied to WEB-INF/classes from fcrepo-configs/src/main/resources upon build.
Configuration for clustered repositories with a centralized MySQL object store.
Fedora 4 will store object properties to the configured backend datastore. These probably won't be very large, and should be stored on fast disk. The object properties are stored as binary JSON documents within the given cache store configuration.
fcrepo.binary.directory:target/binaries |
Fedora 4 stores binary content separately (to one of the above paths, depending on configuration). These files are stored hashed by the content SHA-1 hash.
Different Infinispan configurations can also have an impact on repository performance.
| Infinispan Configuration | Average | Median | Standard Deviation |
|---|---|---|---|
| filecachestore | 0.1121 | 0.105 | 0.0313 |
| leveldb | 0.0736 | 0.0630 | 0.0445 |
| leveldb with async persistence | 0.0610 | 0.0550 | 0.0220 |
| RAM | 0.0517 | 0.0480 | 0.0148 |
| leveldb with file binary store * | 0.0644 | 0.0570 | 0.0196 |
| Total | 0.0703 | 0.0590 | 0.0318 |
* default configuration
This XACML Authorization Delegate Module is based on the design documented here: XACML Authorization Delegate
policy set for the admin role
define the policies for the admin role
policy set for the basic role
define the policies for the basic role
policy set that prevents access to any files with the mime type "image/tiff" that have the "http://example.com/mixins#master" type (example-mixins:master mixin)
policy set for reading normal nodes
define the policies for the reader role
policy set for writing normals nodes.
define the policies for writing the normal nodes
namespace properties to enable XACML authorization