All Versions
- DSpace 7.x (Current Release)
- DSpace 8.x (Unreleased)
- DSpace 6.x (EOL)
- DSpace 5.x (EOL)
- More Versions...
...
Note: You should replace the contact-information "dspace-help@myu.edu or call us at xxx-555-xxxx
" with your own contact details in:
config/emails/change_password
config/emails/register
Info |
---|
Beginning with DSpace 6, your file storage location (aka bitstore) is now defined in the |
DSpace supports multiple DSpace supports two distinct options for storing your repository bitstreams (uploaded files). The files are not stored in the database in which Metadata, user information, ... are stored. An assetstore is , instead they are provided via a configured "assetstore" or "bitstore".
By default, the assetstore is simply a directory on your server , on which the bitstreams are stored and consulted afterwards. The usage of different assetstore directories is the default "technique" in DSpace. The parameters below define which assetstores are present, and which one should be used for newly incoming items. As an alternative, DSpace can also use SRB (Storage Resource Brokerage) as an alternative. See SRB File Storage for details regarding SRB.([dspace]/assetstore/
) under which bitstreams (files) are stored by DSpace.
At this time, DSpace supports two primary locations for storing your files:
[dspace]/assetstore/
directoryMore information on configuring or customizing the storage location of your files can be found in the Storage Layer documentation.
Property: |
| ||
Example Value: |
| ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | This is Asset (bitstream) store number 0 (Zero). You need not place your assetstore under the /dspace directory, but may want to place it on a different logical volume on the server that DSpace resides. So, you might have something like this: | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | This property specifies extra asset stores like the one above, counting from one (1) upwards. This property is commented out (#) until it is needed. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | Specify the number of the store to use for new bitstreams with this property. The default is 0 [zero] which corresponds to the 'assestore.dir' above. As the asset store number is stored in the item metadata (in the database), always keep the assetstore numbering consistent and don't change the asset store number in the item metadata. |
Info | ||
---|---|---|
| ||
In the examples above, you can see that your storage does not have to be under the |
assetstore.dir = /storevgm/assetstore
assetstore.dir.1 = /storevgm2/assetstore
assetstore.incoming = 1
...
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 | |
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 | |
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. |
An alternate to using the default storage framework is to use Storage Resource Brokerage (SRB). This can provide a different level of storage and disaster recovery. (Storage can take place on storage that is off-site.) Refer to http://www.sdsc.edu/srb/index.php/Main_Page for complete details regarding SRB.
The same framework is used to configure SRB storage. That is, the asset store number (0..n) can reference a file system directory as above or it can reference a set of SRB account parameters. But any particular asset store number can reference one or the other but not both. This way traditional and SRB storage can both be used but with different asset store numbers. The same cautions mentioned above apply to SRB asset stores as well. The particular asset store a bitstream is stored in is held in the database, so don't move bitstreams between asset stores, and do not renumber them.
Property: |
| ||
Example value: |
| ||
Property: |
| ||
Example value: |
| ||
Property: |
| ||
Example value: |
| ||
Informational Note: | Your SRB Metadata Catalog Zone. An SRB Zone (or zone for short) is a set of SRB servers 'brokered' or administered through a single MCAT. Hence a zone consists of one or more SRB servers along with one MCAT-enabled server. Any existing SRB system (version 2.x.x and below) can be viewed as an SRB zone. For more information on zones, please check http://www.sdsc.edu/srb/index.php/Zones. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | Your SRB domain. This domain should be created under the same zone, specified in srb.mcatzone. Information on domains is included here http://www.sdsc.edu/srb/index.php/Zones. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | Your default SRB Storage resource. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | Your SRB Username. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | Your SRB Password. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | Your SRB Homedirectory | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | Several of the terms, such as mcatzone, have meaning only in the SRB context and will be familiar to SRB users. The last, |
The 'assetstore.incoming' property is an integer that references where new bitstreams will be stored. The default (say the starting reference) is zero. The value will be used to identify the storage where all new bitstreams will be stored until this number is changed. This number is stored in the Bitstream table (store_number column) in the DSpace database, so older bitstreams that may have been stored when 'asset.incoming' had a different value can be found.
In the simple case in which DSpace uses local (or mounted) storage the number can refer to different directories (or partitions). This gives DSpace some level of scalability. The number links to another set of properties 'assetstore.dir', 'assetstore.dir.1' (remember zero is default), assetstore.dir.2', etc., where the values are directories.
To support the use of SRB DSpace uses the same scheme but broaden to support:
If SRB is chosen from the first install of DSpace, it is suggested that 'assetstore.dir' (no integer appended) be retained to reference a local directory (as above under File Storage) because build.xml uses this value to do a mkdir
. In this case, 'assetstore.incoming' can be set to 1 (i.e. uncomment the line in File Storage above) and the 'assetstore.dir' will not be used.
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: |
| ||
Example Value: |
| ||
Informational Note: | If your DSpace instance is protected by a proxy server, in order for log4j to log the correct IP address of the user rather than of the proxy, it must be configured to look for the X-Forwarded-For header. This feature can be enabled by ensuring this setting is set to true. This also affects IPAuthentication, and should be enabled for that to work properly if your installation uses a proxy server. |
...