Page History
...
Main DSpace Configurations
Property: |
|
Example Value: |
|
Informational Note: | Root directory of DSpace installation. Omit the trailing '/'. Note that if you change this, there are several other parameters you will probably want to change to match, e.g. |
Property: |
|
Example Value: |
|
Informational Note: | Fully qualified hostname; do not include port number. |
Property: |
|
Example Value: | |
Informational Note: | Main URL at which DSpace Web UI webapp is deployed. Include any port number, but do not include the trailing ' |
Property: |
|
Example Value: |
|
Informational note | DSpace base URL. URL that determines whether JSPUI or XMLUI will be loaded by default. Include port number etc., but NOT trailing slash. Change to |
Property: |
|
Example Value: |
|
Informational note: | The base URL of the OAI webapp (do not include /request). |
Property: |
|
Example Value: |
|
Informational Note: | Short and sweet site name, used throughout Web UI, e-mails and elsewhere (such as OAI protocol) |
...
Many of the database configurations are software-dependent. That is, it will be based on the choice of database software being used. Currently, DSpace properly supports PostgreSQL and Oracle.
Property: |
|
Example Value: |
|
Informational Note: | Both |
Property: |
|
Example Value: |
|
Informational Note: | The above value is the default value when configuring with PostgreSQL. When using Oracle, use this value: |
Property: |
|
Example Value: |
|
Informational Note: | In the installation directions, the administrator is instructed to create the user "dspace" who will own the database "dspace". |
Property: |
|
Example Value: |
|
Informational Note: | This is the password that was prompted during the installation process (cf. 3.2.3. Installation) |
Property: |
|
Example Value: |
|
Informational Note: | If your database contains multiple schemas, you can avoid problems with retrieving the definitions of duplicate objects by specifying the schema name here that is used for DSpace by uncommenting the entry. This property is optional. |
Property: |
|
Example Value: |
|
Informational Note: | Maximum number of Database connections in the connection pool |
Property: |
|
Example Value: |
|
Informational Note: | Maximum time to wait before giving up if all connections in pool are busy (in milliseconds). |
Property: |
|
Example Value: |
|
Informational Note: | Maximum number of idle connections in pool. (-1 = unlimited) |
Property: |
|
Example Value: |
|
Informational Note: | Determines if prepared statement should be cached. (Default is set to true) |
Property: |
|
Example Value: |
|
Informational Note: | Specify a name for the connection pool. This is useful if you have multiple applications sharing Tomcat's database connection pool. If nothing is specified, it will default to 'dspacepool' |
Property: | db.jndi |
Example Value: | db.jndi = jdbc/dspace |
Informational Note: | Specify the name of a configured connection pool to be fetched from a directory using JNDI. If this property is not configured or no such pool can be retrieved, then DSpace will fall back to creating its own pool using the other db.* properties. db.name must still be specified. |
...