All Versions
- DSpace 7.x (Current Release)
- DSpace 8.x (Unreleased)
- DSpace 6.x (EOL)
- DSpace 5.x (EOL)
- More Versions...
Page History
...
[dspace]/config/dspace.cfg: The primary configuration file, which contains the main configurations for DSpace.[dspace]/config/modules/*.cfg: Module configuration files, which are specific to various modules/features within DSpace.[dspace]/config/local.cfg: A (optional, but highly recommended) localized copy of configurations/settings specific to your DSpace (see The local.cfg Configuration Properties File below)- Additional feature-specific configuration files also exist under
[dspace]/config/, some of these include:default.license: the default deposit license used by DSpace during the submission process (see Submission User Interface documentation)hibernate.cfg.xml: The Hibernate class configuration for the DSpace database (almost never requires changing)input-forms.xml: The default deposit input forms for DSpace (see Submission User Interface documentation)item-submission.xml: the default item submission process for DSpace (see Submission User Interface documentation)launcher.xml: The configuration of the DSpace command-line "launcher" ([dspace]/bin/dspace, see the DSpace Command Launcher documentation)log4jlog4j2.propertiesxml: The default logging settings for DSpace log files (usually placed in[dspace]/log)news-side.htmlandnews-top.html: HTML news configuration files for the JSPUI homepage (see JSPUI Configuration and Customization)news-xmlui.xml: News configuration file for the XMLUI homepage (see XMLUI Configuration and Customization)workflow.xml: Configuration for the Configurable Workflow feature (not used by default)xmlui.xconf: Configuration for the XMLUI (see XMLUI Configuration and Customization)
...
Property: |
| ||
Example Value: |
| ||
Informational Note: | This is where your logging configuration file is located. You may override the default log4j configuration by providing your own. Existing alternatives are:
| ||
Property: |
| ||
Example value: |
| ||
Informational Note: | This is where to put the logs. (This is used for initial configuration only) | ||
Property: | loglevel.dspace (defined in log4jlog4j2.propertiesxml) | ||
| Example value: | loglevel.dspace = INFO | ||
| Informational Note: | Log level for all DSpace-specific code (org.dspace.* packages). By default, DSpace only provides general INFO logs (in order to keep log sizes reasonable). As necessary, you can temporarily change this setting to any of the following (ordered for most information to least): DEBUG, INFO, WARN, ERROR, FATAL Please be aware we do not recommend running at the DEBUG level in Production for significant periods of time, as it will cause the logs to be extremely large in size. | ||
Property: | loglevel.other (defined in log4jlog4j2.propertiesxml) | ||
| Example value: | loglevel.other = INFO | ||
| Informational Note: | Log level for other third-party tools/APIs used by DSpace (non-DSpace specific code). By default, DSpace only provides general INFO logs (in order to keep log sizes reasonable). As necessary, you can temporarily change this setting to any of the following (ordered for most information to least): DEBUG, INFO, WARN, ERROR, FATAL Please be aware we do not recommend running at the DEBUG level in Production for significant periods of time, as it will cause the logs to be extremely large in size. |
...
. |
General Plugin Configuration
...
The CNRI Handle system is a 3rd party service for maintaining persistent URL's. For a nominal fee, you can register a handle prefix for your repository. As a result, your repository items will be also available under the links http://handle.net/<<handle prefix>>/<<item id>>. As the base url of your repository might change or evolve, the persistent handle.net URL's secure the consistency of links to your repository items. For complete information regarding the Handle server, the user should consult The Handle Server section of Installing DSpace.
...
Overview
Content Tools