Page History

...

If you are upgrading across multiple versions: You should perform all of the steps of each upgrade between the version from which you are starting and the version to which you are upgrading. You do not need to install each intervening version, but you do need to carry out all of the configuration changes and additions, and all of the database updates, for each one.

Upgrading from 1.7 to 1.7.x

In the notes below 

In the notes below {{\[dspace\]}}

 refers to the install directory for your existing DSpace installation,

 and {{\[dspace-source\]}}

 to the source directory for DSpace 1.7.1. Whenever you see these path references, be sure to replace them with the actual path names on your local system.

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).

   • Wiki Markup
     The asset store (_\[dspace\]/assetstore_  by default)

   • Your configuration files and customizations to DSpace (including any customized scripts).
2. Download DSpace 1.7.1 Retrieve Retrieve the new DSpace 1.7.1 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 Chapter 3.3.3 Installation, Step 3 for unpacking directives.
3. Stop Tomcat. Take down your servlet container. For Tomcat, use the  $CATALINA/shutdown.sh  script. (Many installations will instead use 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:

   1. Wiki Markup
      JSPUI modifications: _{{\[dspace-source\]/dspace/modules/jspui/src/main/webapp/_}}

   2. Wiki Markup
      XMLUI modifications: _{{\[dspace-source\]/dspace/modules/xmlui/src/main/webapp/_}}

5. Build DSpace. Run the following commands to compile DSpace:

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

   You will find the result in 

   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.

6. Update DSpace. Update Update the DSpace installed directory with the new code and libraries. Issue the following commands: unmigrated-wiki-markup

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

7. Generate Browse and Search Indexes*. Though there are not any database changes between 1.7 and 1.7.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):

   Code Block
   _\[dspace\]/bin/dspace index-init_

8. 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): _

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

9. *Restart servlet container.  Now Now restart your Tomcat/Jetty/Resin server program and test out the upgrade.

...