Royce,
Besides the explanation of 'could yield bad performance', did you ever get an explanation about why ESRI nixed this capability? I have a situation where I'd like to publish a map service which just does basic cartographic display control of embedded services at different scales so that the client doesn't have to inherit that responsibility. If you ever found an approach which you think is a decent substitute, I'd love to hear your opinion. You can email me directly at rick.sipin@intrado.com. Thanks in advance.
At 10.1, map service does not support any embedded service layer.
Thank you for the response. Just to be clear... the words that I heard at the UC by esri staff, that... "there is a workaround" is false and there is no way, no how to get 10.1 do do this?
Hi Royce,
I tested real quick with this service: http://mesonet.agron.iastate.edu/cgi-bin/wms/goes/east_ir.cgi?
This map can be added as an operational layer to an ArcGIS.com web map and projects properly. The best way to do this would be to add these layers client side.
Performance is a big reason for preventing 'cascading' map services, but there are also questions of service owership and attribution to consider.
I'm unsure the context, but I can say that at least with Esri-powered WMS from ArcGIS for Server, at 10.3 any cached map service also has the WMTS capability enabled. In this case, since its coming from the MapServer product, I'd definitely just add it client side using an app built with the JS API.
At 10.0, this could be worked around by publishing a 'Classic' map service instead of an 'Optimized' map service. At 10.1+, all services are optimized.