Upgrading From 1.6 to 1.6.x

Upgrade Steps

1. Backup Your DSpace. First, and foremost, make a complete backup of your system, including:
   • A snapshot of the database. To have a "snapshot" of the PostgreSQL database, you need to shut it down during the backup. You should also have your regular PostgreSQL Backup output (using pg_dump commands).
   • The asset store ([dspace]/assetstore by default)
   • Your configuration files and customizations to DSpace (including any customized scripts).
2. Download DSpace 1.6.2 Retrieve the new DSpace 1.6.2 source code either as a download from DSpace.org or check it out directly from the SVN code repository. If you downloaded DSpace do not unpack it on top of your existing installation. Refer to Installation Instructions, Step 3 for unpacking directives.
3. Stop Tomcat. Take down your servlet container. For Tomcat, use the $CATALINA/shutdown.sh script. (Many installations will have a startup/shutdown script in the /etc/init.d or /etc/rc.d directories.
4. 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/
5. Update Configuration Files. There are no additions to this release. So you do not have to update the configuration files.
6. Build DSpace. Run the following commands to compile DSpace.:

   cd /[dspace-source]/dspace/
   mvn -U clean package

   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.
7. Update DSpace. Update the DSpace installed directory with the new code and libraries. Issue the following commands:

   cd [dspace-source]/dspace/target/dspace-[version]-build.dir
   ant -Dconfig=[dspace]/config/dspace.cfg update

8. 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
9. Update the Database. If you are using Creative Commons Licenses in your DSpace submission process, you will need to run the 1.5.x to 1.6.x database upgrade script again. In 1.6.0 the improper mime-type was being assigned to all CC Licenses. This has now been resolved, and rerunning the upgrade script will now assign the proper mime-type to all existing CC Licenses in your DSpace installation. NOTE: You will receive messages that most of the script additions already exist. This is normal, and nothing to be worried about.
   • 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:

     psql -U dspace -f
        /dspace-1.6-1-src-release/dspace/etc/postgres/database_schema_15-16.sql dspace

     (The line break above is cosmetic. Please place your command in one line.
   • For Oracle: Execute the upgrade script, e.g. with sqlplus, recording the output:
     1. Start SQL*Plus with sqlplus [connect args]
     2. Record the output: SQL> spool 'upgrade.lst'
     3. Run the upgrade script SQL> @[dspace-source]/dspace/etc/oracle/database_schema_15-16.sql
     4. Turn off recording of output: SQL> spool off
     5. Please note: The final few statements WILL FAIL. That is because you have run some queries and use the results to construct the statements to remove the constraints, manually‚ Oracle doesn't have any easy way to automate this (unless you know PL/SQL). So, look for the comment line beginning:

        --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.
10. 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
11. 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/
12. Restart servlet. Now restart your Tomcat/Jetty/Resin server program and test out the upgrade.