All Versions
- DSpace 7.x (Current Release)
- DSpace 8.x (Unreleased)
- DSpace 6.x (EOL)
- DSpace 5.x (EOL)
- More Versions...
...
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
Alternately, you may supply a configured connection pool out of JNDI. The object must be named jdbc/dspace
(the full path is java:comp/env/jdbc/dspace
). DSpace will always look up this name and, if found, will use the returned object as its database connection pool. If not found, the above db.*
properties will be used to create the pool.
If you are using Tomcat, then the object might be defined using a <Resource>
element, or connected to a <Resource>
child of <GlobalNamingResources>
using a <ResourceLink>
element. See your Servlet container's documentation for details of configuring the JNDI initial context.
Earlier releases of DSpace provided a configuration property db.jndi
to specify the name to be looked up, but that has been removed. The name is specified in config/spring/api/core-hibernate.xml
if you really need to change it.
The configuration of email is simple and provides a mechanism to alert the person(s) responsible for different features of the DSpace software.
...