Frequent Map Service Updates

Permanently deleted user

5. Juni 2013 00:33

Looking for some insight on how other may be handling frequent updates to published map services. 

We have numerous viewers throughout our company, through essentials manager we have been doing some configuration of specific layer items within the published maps services.  (Layer Icons, searchable fields, layer order, etc.)   Not sure if I am missing something obviously within Essentials but it seems when we have these updates it it breaking certain of these custom configured elements (especially global search) and is requiring us to remove the map service from Essentials and reload it and reconfigure everything. 

is there a best practice on handing frequent changes to our underlying map services that is less work intensive?

Thanks.

 

0

• 

  Permanently deleted user

  6. Juni 2013 04:08

  Hi Ted,

  After your map service changes, you should get a dialog in REST Manager that lets you remove or reassign missing layers.  A layer will go missing if its name changes or if the draw order has changed, and Essentials is no longer able to identify it.

  If you have added new layers then they will be available from the Add/Remove Layers tab from the map service management page.  If you have added sublayers to a group layer, then REST Manager will have a warning icon beside the current site action, which you can click to resolve the missing layers.

  You should not have to remove, add, and reconfigure the service just to get the site working again.  What sort of changes are happening to your services that preclude this operation?

  Regards,

  -Malcolm

  0
• 

  Permanently deleted user

  6. Juni 2013 05:14

  Ok thanks, the Add/Remove Layers is very useful and helps with part of our problem.      

   

  0

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