MXD best practices for publishing to a service
Hello,
Recently we have been having some difficulties publishing out our MXD's (overwritting a service) when we make updates to the data or layers. Basically the service gets "locked up" and then the it will not run. We have figured out a fix for this (not the cause just yet). It is a very long work around, but everytime I go to republish a service and overwrite what I have created, I am afraid it will "lock up again " and then my live sites will no longer work.
I was always told (some advice I got a log time ago) to keep all my operational layers/layer groups in one mxd and publish it out as one operational service. This service serves many apps (4 in total). so all my layers and layer groups are in ONE mxd...with various symbology and properties.
My question is ...should it be this way or should I save each layer group as its own MXD and then publish them out as individual serivces? Can an mxd be too big or have too much data in it?
Any best practice ideas or tips would be very much appreciated....I really just need to figure out why my mxd won't overwrite when I publish it out.
thanks
Larisa
-
My esri rep has told me that it's best to publish map documents in smaller groups instead of one mxd. How many layers are in your mxd? I've got about 190 layers published across 10 different map services that I grouped based on theme (housing, transportation, etc.). I've seen great performance in geocortex and when using the services in general. Trying to publish them all in one service would mean it would take a really long time to overwrite.
The only challenge I've had is managing drawing order with the service, but I've tried to take the geometry types (point, line, polygon) into account when organizing my layers too.
0 -
Thank you John!
That is exactly what I am looking for. I thinkI am going to have to do just that. I don't have quite as many layers as you do, but I do have a lot, and right now, the one MXD thing is just not working. Thanks for the advice.
Larisa
0 -
Best of luck. It's an extra level of complexity, but I think you'll find it's totally worth it.
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
3 Kommentare