I assume you're planning on using the 'updatelayers' admin command to register the existing layers with GeoNode (it's what I would do and I recommend it for anyone else trying this.) One issue with this is that it reads in and saves back the configuration for every layer (a necessary step in setting the metadata and attribution links to point back to the GeoNode site.) Due to bugs in gsconfig.py, some parts of the GeoServer configuration may be destroyed in the process - I have heard of layers using SQL Views <http://docs.geoserver.org/stable/en/user/data/sqlview.html> in GeoServer having the SQL template deleted for example. I suggest making a backup of your datadir before attempting the import (which is a good idea anyway in case you find yourself needing to downgrade back to 2.0 - loading a geoserver 2.0 datadir in geoserver 2.1 makes it no longer valid for use with geoserver 2.0).
-- David Winslow OpenGeo - http://opengeo.org/ On Thu, Jun 30, 2011 at 10:40 AM, Ariel Nunez <[email protected]>wrote: > Hello guys, > > Soon I am going to have to convert an already existing GeoServer 2.0.2 > installation with GWC into GeoNode. I think some people have already > tried that in this list and I wonder how successful they were able to > be? Is there anything important to watch out for? > > Thanks in advance for any comments, > > Ariel. >
