All Versions
- DSpace 7.x (Current Release)
- DSpace 8.x (Unreleased)
- DSpace 6.x (EOL)
- DSpace 5.x (EOL)
- More Versions...
...
Note |
---|
The process for upgrading to 1.2 from either 1.1 or 1.1.1 is the same. If you are running DSpace 1.0 or 1.0.1, you need to follow the instructions for upgrading from Upgrading From 1.0.1 to 1.1 before following these instructions. Note also that if you've substantially modified DSpace, these instructions apply to an unmodified 1.1.1 DSpace instance, and you'll need to adapt the process to any modifications you've made. |
Wiki Markup |
---|
Step one is, of course, to *back up all your data* before proceeding\!\! Include all of the contents of {{\[dspace\]}} and the PostgreSQL database in your backup. |
Code Block |
---|
cd [dspace]/lib cp activation.jar servlet.jar mail.jar [dspace-1.2-source]/lib |
Wiki Markup |
---|
You need to add the following new parameters to your _\[dspace\]/dspace.cfg_: |
Code Block |
---|
##### Media Filter settings ##### # maximum width and height of generated thumbnails thumbnail.maxwidth = 80 thumbnail.maxheight = 80 |
Code Block |
---|
config.template.oai-web.xml = [dspace]/oai/WEB-INF/web.xml |
Wiki Markup |
---|
The layout of the installation directory (i.e. the structure of the contents of {{\[dspace\]}}) has changed somewhat since 1.1.1. First up, your 'localized' JSPs (those in jsp/local) now need to be maintained in the _source_ directory. So make a copy of them now\! Once you've done that, you can remove _\[dspace\]/jsp_ and _\[dspace\]/oai_, these are no longer used. (.war Web application archive files are used instead). Also, if you're using the same version of Tomcat as before, you need to *remove the lines from Tomcat's conf/server.xml file that enable symbolic links for DSpace.* These are the _<Context>_ elements you added to get DSpace 1.1.1 working, looking something like this: |
Code Block |
---|
<Context path="/dspace" docBase="dspace" debug="0" reloadable="true" crossContext="true"> <Resources className="org.apache.naming.resources.FileDirContext" allowLinking="true" /> </Context> |
Code Block |
---|
ant -Dconfig= [dspace]/config/dspace.cfg update |
Code Block |
---|
cp [dspace-1.2-source]/config/news-* [dspace-1.2-source]/config/mediafilter.cfg [dspace-1.2-source]/config/dc2mods.cfg [dspace]/config |
Wiki Markup |
---|
You'll need to make some changes to the database schema in your PostgreSQL database. _\[dspace-1.2-source\]/etc/database_schema_11-12.sql_ contains the SQL commands to achieve this. If you've modified the schema locally, you may need to check over this and make alterations. To apply the changes, go to the source directory, and run: |
Code Block |
---|
psql -f etc/database_schema_11-12.sql [DSpace database name] -h localhost |
Code Block |
---|
[dspace]/bin/dsrun org.dspace.administer.Upgrade11To12 |
Code Block |
---|
[dspace]/bin/index-all |
Wiki Markup |
---|
Delete the existing symlinks from your servlet container's (e.g. Tomcat's) _webapp_ sub-directory. Copy the _.war_ Web application files in _\[dspace-1.2-source\]/build_ to the _webapps_ sub-directory of your servlet container (e.g. Tomcat). e.g.: |
Code Block |
---|
cp [dspace-1.2-source]/build/*.war [tomcat]/webapps |
Code Block |
---|
# Run the media filter at 02:00 every day 0 2 * * * [dspace]/bin/filter-media |
Wiki Markup |
---|
As noted in note 1, every item has been 'touched' and will need re-harvesting. The above means that, if already registered and harvested, you will need to re-register your repository, effectively as a 'new' OAI-PMH data provider. You should also consider posting an announcement to the [OAI implementers e-mail list|http://www.openarchives.org/mailman/listinfo/OAI-implementers|OAI implementers e-mail list] so that harvesters know to update their systems. Also note that your site may, over the next few days, take quite a big hit from OAI-PMH harvesters. The resumption token support should alleviate this a little, but you might want to temporarily whack up the database connection pool parameters in _\[dspace\]/config/dspace.cfg_. See the _dspace.cfg_ distributed with the source code to see what these parameters are and how to use them. (You need to stop and restart Tomcat after changing them.)I realize this is not ideal; for discussion as to the reasons behind this please see relevant posts to the OAI community: [post one|http://openarchives.org/pipermail/oai-implementers/2004-June/001214.html|post one], [post two|http://openarchives.org/pipermail/oai-implementers/2004-June/001224.html|post two]. If you really can't live with updating the base URL like this, you can fairly easily have thing proceed more-or-less as they are, by doing the following: |