Good Afternoon,
I'm trying to migrate Geonetwork 2.10.4 to 3.0.0 beta.
how do I migrate data directory and database (postgresql)?
Thanks.
Regards.
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Migrate-Geonetwork-2-10-4-to-3-0-0-beta-tp5202539.html
Sent from the GeoNetwork users mailing list archive at Nabble.com.
Hi,
2015-04-22 21:18 GMT+02:00 cbeltran <cbeltran@anonymised.com>:
Good Afternoon,
I'm trying to migrate Geonetwork 2.10.4 to 3.0.0 beta.
how do I migrate data directory and database (postgresql)?
Once the db configured, the application should migrate the 2.10.4 db to a
3.0.0 version on startup.
Another option is to run SQL migration scripts manually
https://github.com/geonetwork/core-geonetwork/tree/develop/web/src/main/webapp/WEB-INF/classes/setup/sql/migrate/v2110
and
https://github.com/geonetwork/core-geonetwork/tree/develop/web/src/main/webapp/WEB-INF/classes/setup/sql/migrate/v300
The datadir is the same. You could drop the index and it will be created on
startup.
Cheers.
Francois
Thanks.
Regards.
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Migrate-Geonetwork-2-10-4-to-3-0-0-beta-tp5202539.html
Sent from the GeoNetwork users mailing list archive at Nabble.com.------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live
exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork
Hi,
can somebody actually participate clear instructions how to upgrade to
GeoNetwork version 3.0.0?
If at the moment the version used is 2.10.4, ran with tomcat7, deployed by
geonetwork.war in //var/lib/tomcat6/webapps/ - How do I achieve the
migration as François has proposed?
To be clear, what do I do with the geonetwork 2.10.4 folder
//var/lib/tomcat6/webapps/geonetwork/ and how do I add the latest 3.0.0?
Should I delete the old one? And if yes, should I simply store a copy of the
database folder? How do I reintegrate the database after redeployment?
dropping the index
doesn't mean nothing to me. So, here, again, voilà - how the heck do I drop
the index?
Can I deploy a new version simultaneously with a previous version, for
example by changing the name of the /geonetwork.war/ to /geonetwork3.war/,
restart tomcat and run both version at the same time, one in
//var/lib/tomcat6/webapps/geonetwork/ and the new one in
//var/lib/tomcat6/webapps/geonetwork3/ ? How do I migrate the database in
this case?
And this, for example is also unclear:
Francois Prunayre wrote
Once the db configured, the application should migrate the 2.10.4 db to a
3.0.0 version on startup.
How can I "pre-configure" the database if I haven't yet deployed a new
version? Migrate from which location to which location? Where is that
defined? At the moment when the 3.0.0 starts up - how it is related to
2.10.4, how/where is that configured?
I know these might be ridiculous questions for all those advanced in
development, but for many of users there is no consistent step-by-step
online resource available. Most of the help is related to old versions (eg:
< 2.6.x) and therefore all is mixed up. And the posts which actually apply
to later versions (> 2.10.3) are very partial and incomplete, understood
amongst a few administrators whose job is anyway to maintain a catalogue -
meaning that's their principal daily activity.
Here, another very useful resource to update and adapt for the new version:
https://trac.osgeo.org/geonetwork/wiki/HowToRunMultipleGeonetworkInstancesUnderTomcat
Running two instances could be an advantage as explained on the link
provided. Making a fresh set of clean instructions how to do that would
simplify the process for many users.
I hope this post won't stay unanswered. I know there is a completely new
help documentation on the way, but I guess there are some procedures which
should be on the priority list. Thanks for any kind of feedback.
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Migrate-Geonetwork-2-10-4-to-3-0-0-beta-tp5202539p5206675.html
Sent from the GeoNetwork users mailing list archive at Nabble.com.
So, this must be the index folder:
//var/lib/tomcat7/webapps/geonetwork/WEB-INF/data/index/
I suppose migrating the db then means that its contents should be dropped
into //var/lib/tomcat7/webapps/geonetwork3/WEB-INF/data/index/ right after a
freshly deployed geonetwork3.war. And by overwriting whatever exists under
the new ../index/?
However, for the moment I'm getting http status 404 - "The requested
resource is not available", while Tomcat configuration hasn't changed and
version 2.10.4 still runs impeccable.
I also tried with removing the version 2.10.4, deploying 3.0.0 and letting
tomcat with the same configuration. Nothing changed, same status 404. Then I
placed back the 2.10.4 and it ran with no issues.
Should I reconfigure something in tomcat to be able to run ver3.0.0 from
//var/lib/tomcat7/webapps/geonetwork3/WEB-INF/data/index/ ?
Thanks again for any possible hints.
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Migrate-Geonetwork-2-10-4-to-3-0-0-beta-tp5202539p5206954.html
Sent from the GeoNetwork users mailing list archive at Nabble.com.
Hi,
What i recommand to you is to save your actual geonetwork instance (webapp
+ DB).
Deploy the new one.
If you have a remote DATA_DIR, you should remove the index and spatial
index in data/index. You will have to do other steps in this case (upgrade
the schemas for example).
If your DATA_DIR is in the webapp, you don't need to remove the index, it
will be freshly built on startup.
For the database, the first run of geonetwork (if the DB config is the same
as for your 2.10), will detect the gn version in the DB, then apply a SQL
script to process the migration. So yes, your data base will be upgraded.
If you want to have your 2.10 instance at the same time, i recommand to
clone the DB, and make the gn3 point to the new one, this way, you'll have
2 DB, one for each instance.
Make sure you configured gn3 to access your postgres DB
Hope it helps
On Thu, May 21, 2015 at 5:44 PM, zer0mode <otoncopi@anonymised.com> wrote:
So, this must be the index folder:
//var/lib/tomcat7/webapps/geonetwork/WEB-INF/data/index/
I suppose migrating the db then means that its contents should be dropped
into //var/lib/tomcat7/webapps/geonetwork3/WEB-INF/data/index/ right after
a
freshly deployed geonetwork3.war. And by overwriting whatever exists under
the new ../index/?However, for the moment I'm getting http status 404 - "The requested
resource is not available", while Tomcat configuration hasn't changed and
version 2.10.4 still runs impeccable.I also tried with removing the version 2.10.4, deploying 3.0.0 and letting
tomcat with the same configuration. Nothing changed, same status 404. Then
I
placed back the 2.10.4 and it ran with no issues.Should I reconfigure something in tomcat to be able to run ver3.0.0 from
//var/lib/tomcat7/webapps/geonetwork3/WEB-INF/data/index/ ?Thanks again for any possible hints.
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Migrate-Geonetwork-2-10-4-to-3-0-0-beta-tp5202539p5206954.html
Sent from the GeoNetwork users mailing list archive at Nabble.com.------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
Application Monitoring Software and Tool - ManageEngine Applications Manager
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
geonetwork-users List Signup and Options
GeoNetwork OpenSource is maintained at
GeoNetwork - Geographic Metadata Catalog download | SourceForge.net
--
Florent Gravin
Camptocamp - Chambéry
0479444492