-
Notifications
You must be signed in to change notification settings - Fork 63
Upgrade from Geportal Server 1.x to 2.x
zguo edited this page Jul 8, 2020
·
4 revisions
If you have an existing Esri Geoportal Server 1.x instance that needs to be migrated to Esri Geoportal Server 2.6.4, following are the steps:
- Install the Esri Geoportal Server 2.6.4 by following instruction at Installing-Geoportal-Server-2.6.4
- Install the Esri Geoportal Harvester 2.6.4 by following instruction at https://github.com/Esri/geoportal-server-harvester/wiki/Installation-guide
- Harvest the metadata from the geoportal 1.x instance to the new geoportal instance:
- Create an output broker for geoportal 2.x in Harvester
- Create an input broker, there are multiple options:
- You can create a "Catalog Service for the Web" type input broker.
- You can create a "Migration Tool" type input broker, the JNDI is the geoportal 1.x instance JNDI information (make sure you have the proper JDBC driver). more instruction at https://github.com/Esri/geoportal-server-harvester/wiki/Migration-tool
- You can export the metadata in Geoportal 1.x to a folder, then create an "UNC Path" type input broker.
- Create a harvest task that matches the input and output destination
- Click "run" on the Harvester task list to harvest the metadata records.
More information on Geoportal Server Harvester is available at https://github.com/Esri/geoportal-server-harvester/wiki
For INSPIRE metadata administrators/publishers, it is possible to edit the harvested INSPIRE metadata in geoportal 2.x to make it compliant to INSPIRE Metadata 2.0.1 standard.
Please note that user info from geoportal 1.x cannot not be migrated, however if you are using LDAP or other authentication mechanisms in Geoportal 1.x, you can configure geoportal 2.x to use the same as well.