Sue, I would keep a backup of anything you are running in production.
The documentation for upgrade in 1.5.1 is wrong because rather than allowing the ant script to backup the config directory / or merge the differences between the source and your installation (the way I changed the ant build in 1.5.2) the documentation recommends editing the [dspace]/config/dspace.cfg (and entire config directory) piece-meal and adding in all the new changes in 1.5 to it. Its much much simpler to actually work in the opposite direction and identify your changes to the installed [dspace]/config and migrate them to [dspace-source]/dspace/config/... and on top of this is sets your configuration up to be closer to the next releases configuration, its better to deal with dramatically different dspace.cfg restructuring between 1.4 and 1.5 now in your upgrade rather than doing the mistakes the documentation recommends. If you do what your recommending below you will also need to run "ant init_configs" in 1.5.1 to recreate the "/dspace/config" directory. I would recommend keeping around /dspace/history, /dspace/logs, /dspace/reports so you can retain that historical info on your dspace instance. -Mark On Fri, May 8, 2009 at 9:53 AM, Thornton, Susan M. (LARC-B702)[RAYTHEON TECHNICAL SERVICES COMPANY] <susan.m.thorn...@nasa.gov> wrote: > I’m thinking maybe I’ll just save our current 1.4.2 /dspace directory > somewhere I’ll have access to it if I need to, and then completely wipe all > subdirectories out of /dspace and let them get built “new” from the 1.5.1 > maven and ant steps. I’m thinking that should work fine since, if I was > doing a first-time installation, we wouldn’t have an existing /dspace > directory anyway and it would get built from the /dspace-source files > too…oh, and yes I think I’ll move assetstore to a different location rather > than under /dspace so that won’t be an issue either. Does my plan sound > prudent to you? > > Thanks Mark! > > Sue > > p.s. If you can think of any other 1.4.2à1.5.1 TestàProduction migration > tips that might help me out, I’d appreciate that as well!!! J > > > > ________________________________ > > From: Mark Diggory [mailto:mdigg...@gmail.com] > Sent: Friday, May 08, 2009 9:28 AM > To: Thornton, Susan M. (LARC-B702)[RAYTHEON TECHNICAL SERVICES COMPANY] > Cc: DSpace Tech; Kimbrough, Glenn W. (LARC-B7)[NCI] > Subject: Re: [Dspace-tech] Question about /dspace directory when upgrading > from 1.4.2 to 1.5.1 > > > > Susan, > > I try to answer inline... > > On Thu, May 7, 2009 at 3:35 PM, Thornton, Susan M. (LARC-B702)[RAYTHEON > TECHNICAL SERVICES COMPANY] <susan.m.thorn...@nasa.gov> wrote: > > What is the best way to get your /dspace directory correctly > upgraded in Production? It seems to me that I’ve been unclear on this in > previous releases and have had problems as a result. My confusion arises > from the following factors: > > 1. The directory/file structure in DSpace 1.5.1 under > /dspace is different: > > a. /jsp directory resides under /dspace in 1.4.2; no /jsp directory in > 1.5.1 > > the jsp directory that goes into /dspace was never used outside the source > tree in 1.4.2 so you should feel comfortable removing it. > > b. The /bin directory never got overlaid when you recompiled the > application in 1.4.2; in 1.5.1, the /bin directory gets rebuilt from > /dspace-source/dspace/bin every time you reassemble/recompile the > application > > not only the bin, but files do get added to the "config", and the "lib", > "webapp" and "etc" directories are backed up each build so that they can be > recovered if necessary. > > c. /assetstore resides under /dspace in 1.4.2 and 1.5.1, however I do > NOT want to copy over my test (1.5.1) /assetstore over my prod (1.4.2) > assetstore b/c I only have a subset of data in Test > > An option, change the dspace.cfg assetstore location outside the /dspace > directory and maintain it separately. > > 2. When I first started our 1.5.1 implementation in Test, > I copied everything under /dspace/bin in 1.4.2 to /dspace-source/dspace/bin; > however we have added new files and modified some old files in /dspace/bin > in 1.4.2 since then – very confusing as to which /dspace/bin files are the > “correct” ones > > You should take all your changes in the /dspace/bin and try to maintain them > in your [dspace-source]/dspace/bin rather than maintaining them directly in > the installation. Next time you need to upgrade, you'll have them in the > [dspace-source]. If you maintain your [dspace-source] in a version control > system, then you can keep track of those changes as if they are "source" > just like all your other changes. > > > The documentation for upgrading from 1.4.2 to 1.5.1 does not specifically > address this issue. > > I caution the documentation needs updating to address such issues and that > we need volunteers to work on this documentation from the community. > > Mark > > -- > > Mark R. Diggory > @mire NV USA > http://www.atmire.com -- Mark R. Diggory http://purl.org/net/mdiggory/homepage - Bio ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
