All Versions
- DSpace 7.x (Current Release)
- DSpace 8.x (Unreleased)
- DSpace 6.x (EOL)
- DSpace 5.x (EOL)
- More Versions...
...
Wiki Markup |
---|
*The installation directory*, referred to as {{\[dspace\]}}. This is the location where DSpace is installed and running off of it is the location that gets defined in the {{dspace.cfg}} as "dspace.dir". It is where all the DSpace configuration files, command line scripts, documentation and webapps will be installed to. |
Wiki Markup |
---|
*The source directory*, referred to as {{\[dspace-source\]}} . This is the location where the DSpace release distribution has been unzipped into. It usually has the name of the archive that you expanded such as {{dspace}}\-{{<version>}}\-{{release}} or {{dspace}}\-{{<version>}}\-{{src}}\-{{release}}. In the case of the sourceSource distributionRelease Itit is the directory where all of your "build" commands will be run. In the case of the binaryBinary distributionRelease all "build" commands will be run from the subdirectory {{\[dspace-source\]/dspace}}. |
Wiki Markup |
---|
*The web deployment directory*. This is the directory that contains your DSpace web application(s). In DSpace 1.5.x and above, this corresponds to {{\[dspace\]/webapps}} by default. However, if you are using Tomcat, you may decide to copy your DSpace web applications from {{\[dspace\]/webapps/}} to {{\[tomcat\]/webapps/}} (with {{\[tomcat\]}} being wherever you installed Tomcat‚ also known as {{$CATALINA_HOME}}). For details on the contents of these separate directory trees, refer to directories.html. _Note that the_ {{\[dspace-source\]}} _and_ {{\[dspace\]}} _directories are always separate\!_ |
...
Code Block |
---|
useradd -m dspace |
Code Block |
---|
unzip dspace-1.8-release.zip |
Code Block |
---|
gunzip -c dspace-1.8-release.tar.gz | tar -xf - |
Code Block |
---|
bunzip2 dspace-1.8-release.tar.bz | tar -xf - |
Wiki Markup |
---|
For ease of reference, we will refer to the location of this unzipped version of the DSpace release as _\[dspace-source\]_ in the remainder of these instructions. After unpacking the file, the user may which to change the ownership of the _dspace-1.6-release_ to the 'dspace' user. (And you may need to change the group). |
dspace}}database, owned by the {{dspace
PostgreSQL user (you are still logged in at 'root'): Code Block |
---|
createuser -U postgres -d -A -P dspace createdb -U dspace -E UNICODE dspace |
Code Block |
---|
mvn install:install-file -Dfile=ojdbc6.jar -DgroupId=com.oracle -DartifactId=ojdbc6 -Dversion=11.2.0.2.0 -Dpackaging=jar -DgeneratePom=true |
Wiki Markup |
---|
Edit the _\[dspace-source\]/dspace/config/dspace.cfg_ database settings: |
Code Block |
---|
db.name = oracle db.url = jdbc:oracle:thin:@//host:port/dspace db.driver = oracle.jdbc.OracleDriver |
Wiki Markup |
---|
*Initial Configuration:* Edit {{\[dspace-source\]/dspace/config/dspace.cfg}}, in particular you'll need to set these properties: |
Wiki Markup |
---|
{{dspace.dir}} \- must be set to the _\[dspace\]_ (installation) directory. |
dspace.url
- complete URL of this server's DSpace home page.dspace.hostname
- fully-qualified domain name of web server.dspace.name
- "Proper" name of your server, e.g. "My Digital Library".db.password
- the database password you entered in the previous step.mail.server
- fully-qualified domain name of your outgoing mail server.mail.from.address
- the "From:" address to put on email sent by DSpace.feedback.recipient
- mailbox for feedback mail.mail.admin
- mailbox for DSpace site administrator.alert.recipient
- mailbox for server errors/alerts (not essential but very useful!)registration.notify
- mailbox for emails when new users register (optional) Info |
---|
You can interpolate the value of one configuration variable in the value of another one. For example, to set feedback.recipient to the same value as mail.admin, the line would look like: |
Wiki Markup |
---|
*DSpace Directory:* Create the directory for the DSpace installation (i.e. {{\[dspace\]}}). As _root_ (or a user with appropriate permissions), run: |
Code Block |
---|
mkdir [dspace] chown dspace [dspace] |
Code Block |
---|
cd package in the {{\[dspace-source\]/dspace}} directory mvn package |
Code Block |
---|
cd [dspace-source]/dspace/ mvn package |
Info | ||
---|---|---|
| ||
Without any extra arguments, the DSpace installation package is initialized for PostgreSQL. _If you want to use Oracle instead, you should build the DSpace installation package as follows: |
Wiki Markup |
---|
*Build DSpace and Initialize Database:* As the _dspace_ UNIX user, initialize the DSpace database and install DSpace to {{\[dspace\]\_}}: |
Code Block |
---|
cd [dspace-source]/dspace/target/dspace-[version]-build.dir ant fresh_install |
Info |
---|
To see a complete list of build targets, run: |
Wiki Markup |
---|
_Technique A._ Simple and complete. You copy only (or all) of the DSpace Web application(s) you wish to use from the \[dspace\]/webapps directory to the appropriate directory in your Tomcat/Jetty/Resin installation. For example: \\ {{cp \-R \[dspace\]/webapps/\* \[tomcat\]/webapps\*}} (This will copy all the web applications to Tomcat). \\ {{cp \-R \[dspace\]/webapps/jspui \[tomcat\]/webapps\*}} (This will copy only the jspui web application to Tomcat.) |
Wiki Markup |
---|
_Technique B._ Tell your Tomcat/Jetty/Resin installation where to find your DSpace web application(s). As an example, in the {{\<Host\}}> section of your {{\[tomcat\]/conf/server.xml\}} you could add lines similar to the following (but replace {{\[dspace\]}} with your installation location: |
Code Block |
---|
<!-- Define the default virtual host Note: XML Schema validation will not work with Xerces 2.2. --> <Host name="localhost" appBase="[dspace]/webapps" .... |
Code Block |
---|
[dspace]/bin/dspace create-administrator |
http://dspace.myu.edu:8080/jspui
http://dspace.myu.edu:8080/xmlui
http://dspace.myu.edu:8080/oai/request?verb=Identify
(Should return an XML-based response)...
Wiki Markup |
---|
Update paths in _\[dspace-source\]\dspace\config\dspace.cfg_ |
Code Block |
---|
dspace.dir config.template.log4j.properties config.template.log4j-handle-plugin.properties config.template.oaicat.properties assetstore.dir log.dir upload.temp.dir report.dir handle.dir |
Code Block |
---|
cd from your _\[dspace-source\]/dspace/_ directory: mvn package |
Code Block |
---|
cd [dspace-source]/dspace/
mvn package
|
Wiki Markup |
---|
_Note #1:_ This will generate the DSpace installation package in your _\[dspace-source\]/dspace/target/dspace-\[version\]-build.dir/_ directory. |
Code Block |
---|
mvn -Ddb.name=oracle package |
Wiki Markup |
---|
Initialize the DSpace database and install DSpace to _\[dspace\]_ (e.g. _C:\DSpace_) by running the following from command line from your _\[dspace-source\]/dspace/target/dspace-\[version\]-build.dir/_ directory: |
Code Block |
---|
ant fresh_install |
ant help
Wiki Markup |
---|
Create an administrator account, by running the following from your _\[dspace\]_ (e.g. _C:\DSpace_) directory: |
Code Block |
---|
[dspace]\bin\dspace create-administrator |
Wiki Markup |
---|
Copy the Web application directories from _\[dspace\]\webapps_ to Tomcat's webapps dir, which should be somewhere like _C:\Program Files\Apache Software Foundation\Tomcat\webapps_ |
Wiki Markup |
---|
Alternatively, Tell your Tomcat installation where to find your DSpace web application(s). As an example, in the _<Host>_ section of your _\[tomcat\]/conf/server.xml_ you could add lines similar to the following (but replace _\[dspace\]_ with your installation location): |
Code Block |
---|
<!-- DEFINE A CONTEXT PATH FOR DSpace JSP User Interface --> <Context path="/jspui" docBase="[dspace]\webapps\jspui" debug="0" reloadable="true" cachingAllowed="false" allowLinking="true"/> <!-- DEFINE A CONTEXT PATH FOR DSpace OAI User Interface --> <Context path="/oai" docBase="[dspace]\webapps\oai" debug="0" reloadable="true" cachingAllowed="false" allowLinking="true"/> |
...