Migrate mapserv services to portal

[stdavis]

Benefit

The number of services and related traffic on the mapserv machine has shrunk significantly in recent years and will continue to do so. We believe that it is down to a point that the services could be migrated to the portal instance. This would save UGRC the cost of a hosted server as well as an ArcGIS Server license. This will also save maintenance time and cost in the future with one less server to work on.

Acceptance Criteria

• Inventory the existing services on mapserv and associated applications
• Repoint forklift to ship data to the portal machine (this may take some firewall requests)
• Republish the mapserv services to portal
• Repoint the applications to the new portal services
• Shut down and decommission the mapserv machine
• Remove the mapserv ArcGIS Server license from our Esri maintenance

Notes

This may take some coordination with @MichaelAGRC.

Risks

Portal may not have enough resources to handle the additional traffic

We can beef up the machine(s) if needed but we don't think that mapserv traffic is significant anymore.

Forklift data shipping may be negatively affected by cloud networking. We may need to change the shipping model. As an example and possible solution, the locator pallet pushes data to GCS and published a topic that the target can scan for and download and ship.

Issue Reference

• Portal Collaboration for Address Points #409
• GCVE exit planning #489

[steveoh]

services

• locate (BBEcon/Mapservice, /GenerateReport)
• raster (/Raster)
• vista (/Vista)
• broadband (Broadband/ExportWebMap, /FixedCache, /MobileCached, /ProviderCoverage, /WerelineCached)
• spills (DEQSpills/MapService, /ReferenceLayers)
• DOC (DOC/FieldMap [feature and map server])

UDOT RCE is being deprecated
Surface water quality is also being deprecated