On Thu, Aug 1, 2013 at 4:39 PM, Joseph Sayah <[email protected]> wrote:
> Currently we have DSPACE version 1.6.0 and we are planning to upgrade
> to the latest version, my question is the following: is it possible to
> upgrade directly form version 1.6.0 to the latest version, and can you
> provide me with the necessary documents of the upgrade…

Hi Joseph,
  I have just been dealing with the same issue myself and I would suggest that 
you follow Helix's advice about moving to a machine with the latest version of 
your preferred OS if possible.  If you don't have that luxury then make sure 
that your server meets all the minimum requirements before doing the actual 
upgrade.  Things that I discovered that I needed to bring up to date, on our 
RedHat Enterprise Linux 5 server, before moving to 3.2 from 1.6.2 were:

  * Postgresql - We were still on 8.1 and had to upgrade to 8.4.  To upgrade we 
needed to export the full database, remove the old version of postgress, 
install the newer 8.4 version, initialise the database and finally import the 
exported database.  
(http://www.postgresql.org/docs/8.4/static/install-upgrading.html was very 
helpful when doing this).

  * Maven and Ant - just grab the latest binaries from apache and make sure 
they appear at the start of your path.

  * Java - while java 1.6 will work for almost everything if you need to be 
able to harvest from DSpace via OAI-PMH then you will need version 1.7 at least 
(also make sure that tomcat is using the 1.7 java and not an older 1.6 java).

  Definitely follow Helix's advice about starting fresh with the configuration 
files as there are a lot of changes to the structure them between 1.6 and 3.2.  
Some bits are broken out into their own config files and a lot of the config 
entries usualy altered have been pulled out into the build.properites file.

  Now the usual advice; Run through the whole upgrade on your test instance to 
make sure that you know what needs doing and in what order (Write it down as 
you go, so you can repeat it on your live server without forgetting a step); 
and finally make sure you have a full backup before you do it, just to be on 
the safe side.

Regards,
  Jason Cooper
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Reply via email to