Updating your map caches automatically: The key to caching dynamic data

MapReduce for Large Geodatasets « The Memory Leak

MapReduce for Large Geodatasets « The Memory Leak — Thu, 10 Jan 2008 22:45:06 GMT

PingBack from http://ambergis.wordpress.com/2008/01/10/mapreduce-for-large-geodatasets/

re: Updating your map caches automatically: The key to caching dynamic data

Greg Matthews — Fri, 11 Jan 2008 17:30:18 GMT

If you want to run more than one map cache update can you just duplicate the code in the same file?

re: Updating your map caches automatically: The key to caching dynamic data

sterlingdq — Mon, 14 Jan 2008 16:54:55 GMT

Greg- Yes, you can run multiple updates in the script, in either sequential or looped form.

Sterling

re: Updating your map caches automatically: The key to caching dynamic data

Chris — Thu, 17 Jan 2008 21:40:17 GMT

This script is not working for me, I've tried this on 2 servers and my desktop (AGS 9.2 SP3) It reports: C:\ARCGIS~1\scripts>c:\python24\python.exe update.py Starting Cache Update Failed to generate cache. All server contexts failed to cache map. Failed to execute (UpdateMapServerCache). Failed to generate cache. All server contexts failed to cache map. Failed to execute (UpdateMapServerCache). Any thoughts? # This script updates all tiles in an ArcGIS Server 9.2 map cache # Access the geoprocessing tools import arcgisscripting gp = arcgisscripting.create() # Set up all of the variables for the update tool server_name = "L087XPx359" object_name = "test" data_frame = "Layers" layers = "parcels" constraining_extent = "" scales = "32000000;16000000;8000000;4000000;2000000" update_mode = "Recreate All Tiles" thread_count = "2" antialiasing = "NONE" # Run the Update Map Server Cache tool try: print 'Starting Cache Update' gp.UpdateMapServerCache(server_name, object_name, data_frame, layers, constraining_extent, scales, update_mode, thread_count, antialiasing) print 'Finished Cache Update' # Get the error messages if the tool fails except: gp.AddMessage(gp.GetMessages(2)) print gp.GetMessages(2)

re: Updating your map caches automatically: The key to caching dynamic data

sterlingdq — Thu, 17 Jan 2008 22:42:07 GMT

Chris- Some questions that might help troubleshoot:

-Are there any relevant messages in the server log files after the tool fails?

-Does the tool try to do something for a while then fail, or does it fail immediately?

-Do any tiles get updated?

-Can you successfully run UpdateMapServerCache from ArcToolbox with the same parameters?

Sterling

re: Updating your map caches automatically: The key to caching dynamic data

Chris — Fri, 18 Jan 2008 20:51:04 GMT

Sterling, thanks for your help! -Can you successfully run UpdateMapServerCache from ArcToolbox with the same parameters? Yes. -Are there any relevant messages in the server log files after the tool fails? Not really. In fact, I've compared the logs from my run with ArcCatalog with the script, both log outputs are the same, but the tools reports a failure and does not update any tiles. One of the really strange things that I have found after setting logging to level 5 is that if I specify a map services that does not exists, it seems to default to the first one and tries to update the cache for it (but also fails). -Does the tool try to do something for a while then fail, or does it fail immediately? It takes about 20-30 seconds and then fails. -Do any tiles get updated? No. Sterling

re: Updating your map caches automatically: The key to caching dynamic data

sterlingdq — Fri, 18 Jan 2008 21:16:17 GMT

Chris- I took a closer look at your script and was wondering the following:

- Does it work if you use layers = "" Leaving empty quotes should cache all layers. By the way, is this a fused or a multilayer cache?

- Are the scales in your script the same ones at which you originally built your cache? I ask because I noticed they are the same scales I used in the sample script. You should use your own scales.

Sterling

re: Updating your map caches automatically: The key to caching dynamic data

Chris — Sun, 20 Jan 2008 14:27:13 GMT

Sterling,
Thanks for the hint on the scales, I've been using the ones that ArcCatalog uses when I update it via the GUI.
Good news! I got the update to work, thanks much for your help. However, the only combo that I could get to work is multilayer cache with out specifying the layers to update. I can recreate all empty tiles or all tiles - no problem. When I specify a layer name, it reports the same problem
- Failed to generate cache. All server contexts failed to cache map. Failed to execute (UpdateMapServerCache).
Not being able to create the fused cache is not really a big problem, but it would be nice to specify which layers should be updated in the multilayer cache.
Do you think this is possible an issue with AGS 9.2 SP3 and I should try an upgrade or is there anything else you could suggest?
Thanks very much for your help, Chris

re: Updating your map caches automatically:one or more contexts failed

Tom — Sat, 02 Feb 2008 22:04:10 GMT

The script worked successfully when tesing small areas using few polycons. But we got failed error "Updating envelope: 38 .......... Completed with error. One or more server contexts failed." during creating real data. Any idea? Thank you for your halp.

re: Updating your map caches automatically: The key to caching dynamic data

Chris — Sat, 09 Feb 2008 23:36:15 GMT

OK, to get this working from an script, you will need to do a couple of things (or at least, this is what I had to do):
1) Change the default "Maximum time a client will wait for a service to something much higher than the default (Tom, I think that might fix your problem)
2) With my configuration (Windows 2003/XP & AGS 9.2 SP3) I had to supply an extent and that fixed my problem. I think the take home lesson here is that if you are having problems with your python script and you can get it working interactively with ArcCatalog, experiment with the values that ArcCatalog defaults to and use that as your starting template.
-Chris

Starting and Restarting of MapService

Govindarajan — Fri, 20 Mar 2009 17:52:20 GMT

I had developed a program in Python that does the task of reading extents record by record and for every record it updates the cache. This is scheduled to run every night. But i found the starting of mapservices before and after the call to gp.UpdateMapCaching to be extremely annoying. With no direct support for updating the cache in 9.2,I fail to understand as how ESRI folks designed the api to force a restart everytime a call is made to the UpdateMapServerCache. Imagine if i have to update a cache for 100 different extents. I hereby sincerely request ESRI to change the library so that the map service need not be started everytime.