This documentation relates to an old version of DSpace, version 3.x. Looking for another version? See all documentation.
To upgrade from DSpace 1.0.1 to 1.1, follow the steps below. Your dspace.cfg does not need to be changed. In the notes below
[dspace] refers to the install directory for your existing DSpace installation, and [dspace-1.1-source] to the source directory for DSpace 1.1. Whenever you see these path references, be sure to replace them with the actual path names on your local system.
- Take down Tomcat (or whichever servlet container you're using).
- We recommend that you upgrade to the latest version of PostgreSQL (7.3.2). Included are some notes to help you do this (see the
postgres-upgrade-notes.txtfile). Note you will also have to upgrade Ant to version 1.5 if you do this.
- Make the necessary changes to the DSpace database. These include a couple of minor schema changes, and some new indexes which should improve performance. Also, the names of a couple of database views have been changed since the old names were so long they were causing problems. First run psql to access your database (e.g. psql -U dspace -W and then enter the password), and enter these SQL commands:
- Fix your JSPs for Unicode. If you've modified the site 'skin' (jsp/local/layout/header-default.jsp) you'll need to add the Unicode header, i.e.: to the <HEAD> element. If you have any locally-edited JSPs, you need to add this page directive to the top of all of them: (If you haven't modified any JSPs, you don't have to do anything.)
- Copy the required Java libraries that we couldn't include in the bundle to the source tree. For example:
Compile up the new DSpace code, replacing [dspace]/config/dspace.cfg with the path to your current, LIVE configuration. (The second line, touch `find .`, is a precaution, which ensures that the new code has a current datestamp and will overwrite the old code. Note that those are back quotes.)
- Update the database tables using the upgrader tool, which sets up the new >last_modified date in the item table:
- Run the collection default authorization policy tool:
Fix the OAICat properties file. Edit [dspace]/config/templates/oaicat.properties. Change the line that saysTo:
This is needed to fix the OAI-PMH 'Identity' verb response. Then run [dspace]/bin/install-configs.
- Re-run the indexing to index abstracts and fill out the renamed database views:
- Restart Tomcat. Tomcat should be run with the following environment variable set, to ensure that Unicode is handled properly. Also, the default JVM memory heap sizes are rather small. Adjust -Xmx512M (512Mb maximum heap size) and -Xms64M (64Mb Java thread stack size) to suit your hardware.