All Versions
- DSpace 7.x (Current Release)
- DSpace 8.x (Unreleased)
- DSpace 6.x (EOL)
- DSpace 5.x (EOL)
- More Versions...
...
Wiki Markup |
---|
The asset store (_\[dspace\]/assetstore_ by default) |
Wiki Markup |
---|
*Apply any customizations.* If you have made any local customizations to your DSpace installation they will need to be migrated over to the new DSpace. These are housed in one of the following places:JSPUI modifications: _\[dspace-source\]/dspace/modules/jspui/src/main/webapp/_XMLUI modifications: \_\[dspace-source\]/dspace/modules/xmlui/src/main/webapp_ |
Code Block |
---|
cd /[dspace-source]/dspace/ mvn -U clean package |
Wiki Markup |
---|
You will find the result in _\[dspace-source\]/dspace/target/dspace-\[version\]-build.dir_ . Inside this directory is the compiled binary distribution of DSpace. Before rebuilding DSpace, the above command will clean out any previously compiled code ('clean') and ensure that your local DSpace JAR files are updated from the remote maven repository. |
Code Block |
---|
cd [dspace-source]/dspace/target/dspace-[version]-build.dir ant -Dconfig=[dspace]/config/dspace.cfg update |
Wiki Markup |
---|
*Run Registry Format Update for CC License.* Creative Commons licenses have been assigned the wrong mime-type in past versions of DSpace. Even if you are not currently using CC Licenses, you should update your Bitstream Format Registry to include a new entry with the proper mime-type. To update your registry, run the following command: _dspace\]/bin/dspace registry-loader \-bitstream \[dspace\]/etc/upgrades/15-16/new-bitstream-formats.xml_ |
Wiki Markup |
---|
For PostgreSQL: _psql \-U \[dspace-user\] \-f \[dspace-source\]/dspace/etc/postgres/database_schema_15-16.sql \[database name\]_ (Your database name is by default 'dspace'). Example: |
Code Block |
---|
psql -U dspace -f /dspace-1.6-1-src-release/dspace/etc/postgres/database_schema_15-16.sql dspace |
Wiki Markup |
---|
Start SQL*Plus with "_sqlplus \[connect args\]_" |
Wiki Markup |
---|
Run the upgrade script _SQL> @\[dspace-source\]/dspace/etc/oracle/database_schema_15-16.sql{_}{_}SQL> spool off_ |
Code Block |
---|
"--You need to remove the already in place constraints" and follow the instructions in the actual SQL file. Refer to the contents of the spool file "upgrade.lst" for the output of the queries you'll need. |
Wiki Markup |
---|
*Generate Browse and Search Indexes*. Though there are not any database changes in the 1.6 to 1.6.1 release, it makes good policy to rebuild your search and browse indexes when upgrading to a new release. To do this, run the following command from your DSpace install directory (as the dspace user):_\[dspace\]/bin/dspace index-init_ |
Wiki Markup |
---|
*Deploy Web Applications*. Copy the web applications files from your _\[dspace\]/webapps_ directory to the subdirectory of your servlet container (e.g. tomcat):_cp \-R \[dspace\]/webapps/\* \[tomcat\]/webapps/_ |
...
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. |
Wiki Markup |
---|
Copy the PostgreSQL driver JAR to the source tree. For example: _cd \[dspace\]/lib{_}{_}cp postgresql.jar \[dspace-1.2.2-source\]/lib_ |
Wiki Markup |
---|
Remove the old version of _xerces.jar_ from your installation, so it is not inadvertently later used:_rm \[dspace\]/lib/xerces.jar_ |
Wiki Markup |
---|
Install the new config files by moving _dstat.cfg_ and _dstat.map_ from _\[dspace-1.3.x-source\]/config/_ to _\[dspace\]/config_ |
Wiki Markup |
---|
You need to add new parameters to your _\[dspace\]/dspace.cfg_: |
Code Block |
---|
###### Statistical Report Configuration Settings ###### # should the stats be publicly available? should be set to false if you only # want administrators to access the stats, or you do not intend to generate # any report.public = false # directory where live reports are stored report.dir = /dspace/reports/ |
Wiki Markup |
---|
Build and install the updated DSpace 1.3.x code. Go to the _\[dspace-1.3.x-source\]_ directory, and run:_ant \-Dconfig=\[dspace\]/config/dspace.cfg update_ |
Wiki Markup |
---|
You'll need to make some changes to the database schema in your PostgreSQL database. _\[dspace-1.3.x-source\]/etc/database_schema_12-13.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: _psql \-f etc/database_schema_12-13.sql \[DSpace database name\] \-h localhost_ |
Wiki Markup |
---|
Initialize the statistics using: _\[dspace\]/bin/stat-initial{_}_\[dspace\]/bin/stat-general{_}_\[dspace\]/bin/stat-report-initial{_}_\[dspace\]/bin/stat-report-general_ |
Wiki Markup |
---|
Rebuild the search indexes: _\[dspace\]/bin/index-all_ |
Wiki Markup |
---|
Copy the _.war_ Web application files in _\[dspace-1.3.x-source\]/build_ to the _webapps_ sub-directory of your servlet container (e.g. Tomcat). e.g.:_cp \[dspace-1.3.x-source\]/build/*.war \[tomcat\]/webapps_ |
...
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], as well as [this post to the dspace-tech mailing list\|#\|this post to the dspace-tech mailing list|].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: |
...