Geocortex migration and upgrade

Permanently deleted user

5. September 2013 22:30

Hello everybody,

We are about to upgrade our GIS environment to ArcGIS Server 10.2 and Geocortex 3.15/Silverlight Viewer 1.10, on brand new servers. Our current environment runs ArcGIS Server 10.0 and Geocortex 3.14/SilverlightViewer 1.9.1. I had a bit of a play to figure out a way to get our existing Geocortex sites up and running on the new servers, and have come up with a migration path that I think should work OK, so I thought I'd share it in case others are about to do something similar. Also, I'm very new to Geocortex and may have missed something crucial that may come back to bite me, so I'd appreciate any pointers that would help me avoid disaster once I do the migration for real.

1. Install Geocortex Essentials 3.14 in the new environment
2. Copy all live site folders to the new environment
3. Install the Silverlight Viewer 1.10 with the "Install Using a Template" option
4. Install Geocortex Essentials 3.15, which will upgrade the copied sites
5. Open each site in REST Manager, go to viewers and fix broken reference to the 1.9.1 template, replacing it with the 1.10 viewer
6. Apply customizations to Geocortex Essentials and the viewer (e.g. Asset.config file, workflows, images etc.)
7. Update all sites to work with the new ArcGIS Server instance

Regarding step 4, do I have to re-authorize Geocortex Essentials after the upgrade? On my test machine I had 3.15 installed already and parallel-installed 3.14 to do the site upgrade, so followed a slightly different workflow.

If you can see anything wrong with this approach I'd appreciate a line or two on how to do it better, otherwise I hope this may be useful to others out there.

Cheers,

Jan

0

• 

  Permanently deleted user

  13. September 2013 02:03

  Hi Jan,

  This is a good plan, and is how we would typically recommend upgrading when moving to new servers. For future upgrades on the new server, if you have customizations in the Asset.config or either web.config file, be sure to make backups before you begin.

  Also, licensing is server-specific, so if you haven't already, you will need to authorize the new server either during or after the installation.

  -Victoria

  0
• 

  Permanently deleted user

  13. September 2013 15:19

  Thanks Victoria, thas gives me more confidence that everything is going to work out OK, and I'll add taking backups of the Asset.config and web.config files as a step.

   

  Cheers,

  Jan

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.