Hi all I succesfully upgraded from DSPACE 1.8 to DSPACE 3.2
Through the following steps
1 reproducing the production environment Linux Redhat 6, Tomcat, Apache,
java, postgres, ant, maven, etc
2 copying the Dspace 1.8 to the new development environment (asset store
and everything)
3 Upgrading and Verifying.
Now that I have to bring the new upgraded DSPACE 3.2 to production Is it
SEO friendly to move the homeroot and database(Provided that the
assetstore is up to date and the database has a different name but
everything is Identical, handles, etc) and stopping the older 1.8
version?
Thank you very much for your thoughts,
France
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&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
