...
fcrepo4 references purged from pom files? | Property Name | Description | Default Value | Constraints | ||||||
---|---|---|---|---|---|---|---|---|---|---|
fcrepo.config.file | The path to a properties file containing any property name value pair specified below. If the file does not exist, Fedora will silently ignore it. | None | ||||||||
fcrepo.home | The home directory for all Fedora generated output and state. Unless otherwise specified, all logs, metadata, binaries, and internally generated indexes, etc. | <cwd/fcrepo-home> | ||||||||
fcrepo.spring.configuration | The path to the spring configuration. While it is generally not recommended to use this option, in some cases you may need to make adjustments to the default spring configuration. This can be set to a path (relative to the current working directory or absolute) to which Fedora repository content will be written. | <classpath:/config/spring/fcrepo-config.xml> | file:/path/to/fcrepo-config.xml | |||||||
java.io.tmpdir | This specifies the directory for writing temp files. You may need to set this property to a larger disk/filesystem to upload large files, particularly on Linux where /tmp is sometimes on a small partition. | </tmp on Linux, $TMPDIR on MacOSX, and %TEMP% on Windows> | ||||||||
fcrepo.dynamic.jms.port | This specifies the ports used by the embedded JMS-based message broker for OpenWire protocol. Note: If you have multiple instances of Fedora running, this property must be set to avoid messaging port conflicts. | 61616 | ||||||||
fcrepo.dynamic.stomp.port | This specifies the ports used by the embedded JMS-based message broker for STOMP protocol. Note: If you have multiple instances of Fedora running, this property must be set to avoid messaging port conflicts. | 61613 | ||||||||
fcrepo.activemq.directory | Contains the reliable messaging information maintained by ActiveMQ. | <fcrepo.home>/data/ActiveMQ/kahadb | ||||||||
fcrepo.external.content.allowed | This provides the path to a file defining a list of allowed external binary content paths. If this parameter is not provided, then clients will be disallowed from creating external binary resources. See the external content allowed paths configuration for more details. | </path/to/allowed.txt> | ||||||||
fcrepo.autoversioning.enabled | This results in every change to Fedora resources being persisted in the OCFL "mutable-head" extension, as opposed in a new OCFL version. | true | ||||||||
Database Config | ||||||||||
fcrepo.db.url | This parameter allows you to set the database connection url. In general the format is as follows:
Fedora currently supports H2, PostgresQL 12.3, MariaDB 10.5.3, and MySQL 8.0 So using the default ports for the supported databases here are the values we typically use:
MariaDB: jdbc:mariadb://localhost:3306/fcrepo If you wish to configure h2, there are a variety of options detailed in the H2 Reference docs. | By default Fedora uses an embedded H2 database. | ||||||||
fcrepo.db.user=<database_username> - | The database username | None - H2 doesn't require it | ||||||||
fcrepo.db.password=<database_password> | The database password | None - H2 doesn't require it | ||||||||
fcrepo.jms.baseUrl | This specifies the baseUrl to use when generating JMS messages. You can specify the hostname with or without port and with or without path. If your system is behind a NAT firewall you may need this to avoid your message consumers trying to access the system on an invalid port. If this system property is not set, the host, port and context from the user's request will be used in the emitted JMS messages. | <http://localhost:8080/fcrepo/rest> | ||||||||
fcrepo.velocity.runtime.log | The HTML template code uses Apache Velocity, which generates a runtime log called velocity.log . By default this is placed inside fcrepo.home , but it is possible to override the location to have it written to an alternate location. | <$fcrepo.home/velocity.log> | ||||||||
Persistence | ||||||||||
fcrepo.session.timeout | This sets the duration for which a transaction will stay active before auto-rolling back. Defaults to 180000 ms, or 3 minutes. | 180000 | ||||||||
fcrepo.persistence.defaultDigestAlgorithm | This sets the default digest algorithm on ingested binary resources. Valid values: [sha512|sha256] | sha512 | ||||||||
OCFL
| ||||||||||
fcrepo.ocfl.root | Sets the root directory of the OCFL. | <fcrepo.home>/data/ocfl-root | ||||||||
fcrepo.ocfl.temp | Sets the temp directory used by OCFL. | <fcrepo.home>/data/ocfl-temp | ||||||||
fcrepo.ocfl.staging | Sets the staging directory used by OCFL. | <fcrepo.home>/data/ocfl-staging |
This results in every change to Fedora resources being persisted in the OCFL "mutable-head" extension, as opposed in a new OCFL version. (default is "true")
No Format |
---|
<!-- Containment Index DB -->
<bean id="containmentIndexDataSource" class="org.springframework.jdbc.datasource.DriverManagerDataSource">
<property name="driverClassName" value="org.h2.Driver" />
<property name="url" value="jdbc:h2:mem:index" />
</bean> |
Within Fedora's fcrepo-config.xml file, the value of "url" can be changed to support a wide range of connection modes and connection settings. Reference
No Format |
---|
-Dfcrepo.session.timeout=<milliseconds> |
This sets the duration for which a transaction will stay active before auto-rolling back. Defaults to 180000 ms, or 3 minutes
No Format |
---|
-Dfcrepo.persistence.defaultDigestAlgorithm=[sha512|sha256] |
This sets the default digest algorithm on ingested binary resources (default: sha512)
Databases
By default, Fedora uses h2 for storing internal indices derived from the persistent application state. Alternatively, Fedora can be configured to use MySQL, MariaDB or PostgresQL instead. Insert the values appropriate to your database configuration in the parameters specified below in brackets (<>).
No Format |
---|
-Dfcrepo.db.url=jdbc:<database_type>://<database_host>:<database_port>/<database_name> -Dfcrepo.db.user=<database_username> -Dfcrepo.db.password=<database_password>
|
Below is are examples for mysql, mariadb, and postgresql using the default ports.
...
Configuration Chain
The standard configuration chain is as follows:
...