Page History

...

• Database: Make a snapshot/dump of the database. For the PostgreSQL database use Postgres' pg_dump command. For example: unmigrated-wiki-markup

  Code Block
  pg_dump -U [database-user] -f [backup-file-location] [database-name]

• Assetstore: Backup the directory ({{\[dspace\]/assetstore}} by  by default, and any other assetstores configured in the {{\[dspace\]/config/dspace.cfg}} "assetstore.dir" and "assetstore.dir.#" settings)
• Wiki MarkupConfiguration: Backup the entire directory content of {{\[dspace\]/config}}.
• Customizations: If you have custom code, such as themes, modifications, or custom scripts, you will want to back them up to a safe location.

...

1. Download DSpace 1.8.2 Either download DSpace 1.8.2 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.
2. Merge any customizations. If you have made any local customizations to your DSpace installation they will need to be migrated over to the new DSpace. Customizations are typically housed in one of the following places:
   unmigrated-wiki-markup
   • JSPUI modifications: {{\[dspace-source\]/dspace/modules/jspui/src/main/webapp/}}unmigrated-wiki-markup
   • XMLUI modifications: {{\[dspace-source\]/dspace/modules/xmlui/src/main/webapp/}}
   • Wiki MarkupConfig modifications: {{\[dspace\]/config}}
3. Build DSpace. Run the following commands to compile DSpace:

   No Format
   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 ('package'), 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.
4. Stop Tomcat. Take down your servlet container. For Tomcat, use the $CATALINA_HOME/shutdown.sh script. (Many Unix-based installations will have a startup/shutdown script in the /etc/init.d or /etc/rc.d directories.)
5. Update DSpace.
   1. Update the DSpace installed directory with the new code and libraries. Issue the following commands:

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

      Note
      title Changes to the behavior of the 'ant update' script
      The ant update script has changed slightly as of DSpace 1.8. It now defaults to replacing your existing configuration files (after backing them up first). See the Changes to the DSpace 1.8 Upgrade / Configuration Process note at the top of this page for more details.

   2. No database changes have been made in either 1.8.1 or 1.8.2. So there is no need to update your existing 1.8 database.
6. Update your DSpace Configurations.
   1. There are no new configurations for the 1.8.1 or 1.8.2 releases. Your existing 1.8 configuration files should work fine
7. Refresh Browse and Search Indexes. Though there are not any database changes, it is a 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): *

   Code Block
   [dspace]/bin/dspace index-init
   Wiki Markup

8. Deploy Web Applications*. If necessary, copy the web applications files from your {{\[dspace\]/webapps}} directory to the subdirectory of your servlet container (e.g. tomcat):

   Code Block
   cp -R [dspace]/webapps/* [tomcat]/webapps/

   See the installation guide for full details.
9. Restart servlet container. Now restart your Tomcat/Jetty/Resin server program and test out the upgrade.