Hi all, I have several published map services that have data that is updated once or twice a year. Many of the map services may contain the same layers that we serve to end-users that have different needs. When a layer is updated in our enterprise geodatabase, I have been manually searching for and re-publishing up to 6 or 7 different map services that are stored in different folders on the network. This is sort of tedious and often gets put on a lower priority and our users may not have the most up-to-date data as a result of this. Does anybody have tips to share that they use to keep track of layers that are in published map services? Maybe I am doing things wrong, but I haven't been able to find anything online that suggests that I am.
Thanks for your time!
Are you on Map or Pro? We have a sort of similar situation where I work, and we keep all the maps in a single Pro package. With a carefully written python script, you can even iterate through all the maps in a project and republish them, and schedule that script to run at select intervals.
I am also trying to move my publishing from ArcMap to ArcGIS Pro but I have found the update workflow needs to change.
When publishing from ArcMap, I used a feature class in a registered file geodatebase. To update I would:
This worked great for several years and the service was down for less than a minute when I updated.
I also found that the service published from ArcGIS Pro is much slower than the one published from ArcMap. Has anyone else encountered any of this?
Good idea. My web.config file already has this header. I'm using IIS. Anything else I should check?
<add name="Cache-Control" value="no-store, no-cache, must-revalidate " />