How can I move layers to a new map service without losing Manager layer properties?
I need to split my planning map service into two because it has too many layers to support coded value domain descriptions in query results (a 75-layer limit imposed by ArcGIS Server). The layers are presently configured in GE Manager as published from a single map service. If I move half of the layers to a new MXD and publish it as a new map service, how can I reconfigure the site to point to those layers in the new service without losing the GE Manager settings already applied to each?
I tried publishing the new map service a few weeks ago, and I then (foolishly, as I learned) deleted the layers from the original service and republished that. But then in GE Manager where I had hoped I would be prompted to link missing items to the layers in the new map service, the prompt uselessly limited my choices to layers in the original map service. I was unable to find any way to link to any layers outside of the original map service. So I undid my map service changes.
Now I'd like to try again. I've republished the second map service, so this time should I leave the original service unchanged at first and edit site.xml in some way to point to the new service? I do wish to maintain the attribute configuration without having to set it all up again in Manager. Please explain how I can achieve these objectives.
Thanks,
Justin
0
-
If you copy your original site.xml and then change the original service and then add the new one, you will be asked to delete from the original those layers that have moved. Go ahead and do that and then save. Then go into site.xml and look at the ID numbering of layers. Cut and paste from saved copy into new service, and then change the index numbers to match. I did this and it worked fine. 0 -
I gave this a try but became confused, so will have to try again Monday. I'm not sure I understand the steps, but thank you for replying, Mike. Hopefully it'll make sense on Monday. 0 -
We are about to embark on this same mission... I think Mike is suggesting:
Adding the new map services with the layers from the original map service.
Either rename/stop the original map service.
Open up the site in Manager and the manager will ask where the layers went from the original map service, which at this point, you could specify the layers in your new map services now included in your site XML.
This is a decent way of accomplishing this, but it requires modification of a service that may be in production in other applications. In this cause, it wouldn't be possible to stop/rename the original map service. It would be nice to manually decommission a service in Essentials Manager so that we could map the layers in the old service, to those in the new service.
We have the need to break-up a large map service into multiple smaller map services for performance reasons. I don't have a great way of doing this, without altering the existing/original map service.0 -
I need to split up one of the services I created from the previous split, and am having trouble. I've got both new services loaded into the site, and have stopped and deleted the original service in ArcGIS Server, but all GE Manager tells me is the deleted service appears to be offline. It's not prompting me for the location of the data so I can reconnect it. How can I make it do that? Can someone please help? 0 -
Hi Justin,
The layer migration prompt will only come up if Essentials is able to scan the source service and determine that the layers are no longer in it. Since the source service is stopped and deleted, it cannot determine that. I think your best bet here is to attempt the instructions that Mike supplied in the first reply in this thread.
If you're having trouble with that, please open a support case, and link to this thread, and we can assist you directly.
I think Erik was on to something though, it would be really nice if Essentials had a sort of "maintenance mode" or something similar for map services, that allowed you to migrate your layer configuration from one server to another. I would suggest posting that to the ideas section of the support center, so it can be considered for a future version of the product.
Thanks!
Danny0 -
Was this maintenance mode every implemented? I had to republish a feature layer and don't want to loose the configuration I already had if I don't have too. 0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
6 kommentarer