AnsweredAssumed Answered

Migration from 10.0 to 10.2.2: Overwiting a Service

Question asked by jborgion Champion on Jan 19, 2015
Latest reply on Jan 20, 2015 by jborgion

I have been running ArcGIS server on the 10.0 for a few years: due to a dependance on a third party application, I now have the opportunity to modernize to 10.2.2.


The primary function of ArcGIS Server within the organization I work for is to provide a geocoding service as well as a map service used in 9-1-1 dispatching.  The third party software mentioned is Computer Assisted Dispatch (CAD); a 9-1-1 call is received, and to verify the address of the caller, that information is passed via ArcGIS Engine where the address is validated (geocoded) and the appropriate responding zones (polygons in the map service) assigned.  That information is then passed back to the dispatcher.


Currently, I have two  "systems" available, and I use the slogan "when one is hot, the other is not" where Hot refers to it's connectivity to CAD and where the geocoding and zone assignments are made.  (See workflow image below)  Having two parallel systems allows me to shut one published composite geocoder down so I can rebuild it as new data is made available.  Both composites point to a single file geodatabse that is a child replica of an SDE (SQL Server) geodatabse.Capture.PNG


Once I rebuild one service and restart it, I toggle CAD over to it with no loss in service to dispatch.  I then shutdown the 'cold' service and rebuild the locators for it and restart it as well, leaving me with two refreshed services.


In ArcGIS 10.2.2 there is now the ability to Overwrite a service (see ArcGIS Help (10.2, 10.2.1, and 10.2.2) ) .  From the online help:


At 10.1 and later versions, edits made to the source data (such as feature classes displayed in a map) should be immediately visible in the service as long as a copy of the data was not placed on the server when publishing


I'm not exactly sure what this means.  Can someone please explain this passage?  I would also like to know what change(s) in the current workflow I should make in order to keep the services always available as I do now.