screennanax.blogg.se - Dspace control desk user manual

DSPACE CONTROL DESK USER MANUAL SOFTWARE
DSPACE CONTROL DESK USER MANUAL LICENSE

If a change has been made, the configuration file is reloaded. By default, DSpace checks for changes to any of its runtime configuration files every 5 seconds. This is something we are working to correct in future versions of DSpace.īecause DSpace supports the Apache Commons Configuration, its configurations can now be reloaded without restarting your servlet container (e.g. This means that while the API layer may reload a new value, that new value may not always affect/change the behavior of your user interface (until you restart Tomcat). XMLUI and JSPUI) still cache some configuration settings. In DSpace 6.0, while the DSpace API supports dynamically reloading configurations, the user interfaces (e.g. Configuration Scheme for Reloading and Overriding This ability to include other files is also possible with the local.cfg file, should you want to subdivide your localized settings into several locally specific configuration files. This means that, in the above example, as far as DSpace is concerned, all the settings contained within the authentication*.cfg files "appear" as though they are specified in the main dspace.cfg. Be aware that this essentially causes DSpace to treat all included configurations as if they were part of the parent file. This ability to include properties files within others is very powerful, as it allows you to inherit settings from other files, or subdivide large configuration files. The property value may contain references to other configuration properties, in the form $/authentication-shibboleth.cfg This may cause the feature not to be enabled, or, cause a default property to be used.

DSPACE CONTROL DESK USER MANUAL SOFTWARE

That is, they have a "#" preceding them, and the DSpace software ignores the config property. Some property defaults are "commented out". See "Specifying Multiple Values for Properties" below.

Values assigned in the same *.cfg file are "additive", and result in an array of values.

See the "Special Characters" section below

Certain special characters (namely commas) MUST BE escaped.

Other settings appear as property/value pairs of the form: property.name = property value.

This syntax is very similar to a standard Java properties file, with a few notable enhancements described below. These same input conventions apply to all DSpace *.cfg files.Īll DSpace *.cfg files use the Apache Commons Configuration properties file syntax. We will use the dspace.cfg as our example for input conventions used throughout the system.

xmlui.xconf : Configuration for the XMLUI (see XMLUI Configuration and Customization)Īs most of these configurations are detailed in other areas of the DSpace documentation (see links above), this section concentrates primarily on the "*.cfg" configuration files (namely dspace.cfg and local.cfg).

workflow.xml : Configuration for the Configurable Workflow feature (not used by default).

news-xmlui.xml : News configuration file for the XMLUI homepage (see XMLUI Configuration and Customization).

news-side.html and news-top.html : HTML news configuration files for the JSPUI homepage (see JSPUI Configuration and Customization).

log4j.properties : The default logging settings for DSpace log files (usually placed in /log).

launcher.xml : The configuration of the DSpace command-line "launcher" ( /bin/dspace, see the DSpace Command Launcher documentation).

item-submission.xml : the default item submission process for DSpace (see Submission User Interface documentation).

input-forms.xml : The default deposit input forms for DSpace (see Submission User Interface documentation).

: The Hibernate class configuration for the DSpace database (almost never requires changing).

DSPACE CONTROL DESK USER MANUAL LICENSE

default.license : the default deposit license used by DSpace during the submission process (see Submission User Interface documentation).Additional feature-specific configuration files also exist under /config/, some of these include:./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)./config/modules/*.cfg : Module configuration files, which are specific to various modules/features within DSpace./config/dspace.cfg : The primary configuration file, which contains the main configurations for DSpace.In the following sections you will learn about the different configuration files that you will need to edit so that you may make your DSpace installation work.ĭSpace provides a number of textual configuration files which may be used to configure your site based on local needs.