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:
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 your spring context configuration files, WEB-INF/classes/*.xml. Note that these files are in the source tree under fcrepo-webapp/src/main/resources/spring and copied to WEB-INF/classes upon build.
- here you can specify the repository.json file to be loaded as the repositoryConfiguration, as well as the bean for repository factory and metrics
- bean implementation for InternalIdentifierConverter (identifier translationChain), StoragePolicyDecisionPointImpl, SessionFactory, and base-packages to auto scan into spring
- bean implementation for eventing - observer, filter, event bus
- here you can specify the implementation for processing events
- Specify the config for transactions
- bean implementation for minting identifiers
- config for message broker
- Config for the Messaging Toolkit JGroups to transfer state between nodes in a Fedora Cluster.
- logging configuration (logging can also be configured with System properties)
Modeshape repository configuration
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.
Repository Config Options
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.
- Configuration for file-based object store for testing, not recommended for production.
- Configuration for MySQL-based object store.
- Configuration for PostgreSQL-based object store.
- Configuration with servlet authentication enabled.
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.
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.
|leveldb with async persistence||0.0610||0.0550||0.0220|
|leveldb with file binary store *||0.0644||0.0570||0.0196|
* default configuration
Other module resources
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
- policy set that prevents all repository-changing actions by all but those a localhost or on an internal network.
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