topic Re: Ask : MSD and MXD map service in ArcGIS API for Silverlight Questions

Ask : MSD and MXD map service

HusnanM — Thu, 18 Oct 2012 05:11:56 GMT

Dear all..
I want to ask what is different between MSD and MXD Map service? I heard that ArcGIS not support MXD in the future, is it true?
I ask it because when i am developing editing feature in my application it's work fine in map service with MXD file, but not work in MSD. Am i missing some configuration for the service?

Many thanks for any suggestion and answer

Re: Ask : MSD and MXD map service

DominiqueBroux — Thu, 18 Oct 2012 06:24:57 GMT

I want to ask what is different between MSD and MXD Map service? I heard that ArcGIS not support MXD in the future, is it true?

MSD-based map services have been introduced with ArcGIS 9.3.1 in order to improve map display quality and server performances.

The advantages of MSD services were so great that
, from ArcGIS Server 10.1, only MSD-based optimized map services are supported.

That being said, MXD are still supported by ArcGIS desktop, and map services can still be created from MXD document.

Concerning the editing, I am not aware of any restriction concerning the MSD services.
It should be more tied to your ArcGIS server version and to the way you configure your services (you need to activate the 'FeatureServer' capability when publishing your service).

Which ArcGIS server version are you using? Did you activate the feature server capability?

Re: Ask : MSD and MXD map service

HusnanM — Sun, 12 Dec 2021 08:04:19 GMT

Thanks for reply.
I am using arcgis server 10 sp1.

All service capabilities are turn on both MSD and MXD, but save fail on MSD.

let say i have two feature layer

A : <esri:FeatureLayer ID="Jumper TM" Url="http://192.168.0.180/ArcGIS/rest/services/Emap/FeatureServer/2"/>
B : <esri:FeatureLayer ID="Jumper TR" Url="http://192.168.0.180/ArcGIS/rest/services/EmapMXD/FeatureServer/3"/>

and then i am binding each feature layer into editorWidget like in sample.

the result is A: can edit feature, but on save clicked fail to save into database
the result is B: work fine , can edit feature and save into database

So can i edit feature layer and save it into database with MSD map service? or it just work at MXD map service?

Re: Ask : MSD and MXD map service

DominiqueBroux — Thu, 18 Oct 2012 07:13:03 GMT

What are the metadata of your feature service?
You can get them with a request such as : http://192.168.0.180/ArcGIS/rest/services/Emap/FeatureServer/2?f=pjson

Also, could you use fiddler to look at the response returned by the server when the save is not working? Might give a clue.

Re: Ask : MSD and MXD map service

HusnanM — Sun, 12 Dec 2021 08:04:22 GMT

here is my feature service's metadata

{
  "currentVersion" : 10.01, 
  "id" : 2, 
  "name" : "Jumper TM", 
  "type" : "Feature Layer", 
  "displayField" : "TDATA_ID", 
  "description" : "", 
  "copyrightText" : "", 
  "relationships" : [
  ], 
  "geometryType" : "esriGeometryPoint", 
  "minScale" : 500, 
  "maxScale" : 0, 
  "extent" : {
    "xmin" : -929860.526832985, 
    "ymin" : 9021600.33307571, 
    "xmax" : 340171.723053823, 
    "ymax" : 9105709.71005005, 
    "spatialReference" : {
      "wkid" : 32750
    }
  }, 
  "drawingInfo" : {"renderer" : 
    {
      "type" : "simple", 
      "symbol" : 
      {
        "type" : "esriSMS", 
        "style" : "esriSMSCircle", 
        
        "color" : [
          255, 
          0, 
          0, 
          255
        ], 
        "size" : 2, 
        "angle" : 0, 
        "xoffset" : 0, 
        "yoffset" : 0, 
        "outline" : 
        {
          "color" : [
            0, 
            0, 
            0, 
            255
          ], 
          "width" : 1
        }
      }, 
      "label" : "", 
      "description" : ""
    }, 
    "transparency" : 0, 
    "labelingInfo" : null}, 
  "hasAttachments" : false, 
  "htmlPopupType" : "esriServerHTMLPopupTypeAsHTMLText", 
  "objectIdField" : "OBJECTID", 
  "globalIdField" : "GLOBALID", 
  "typeIdField" : "", 
  "fields" : [
    {
      "name" : "OBJECTID", 
      "type" : "esriFieldTypeOID", 
      "alias" : "OBJECTID", 
      "editable" : false, 
      "domain" : null
    }, 
    {
      "name" : "ENABLED", 
      "type" : "esriFieldTypeSmallInteger", 
      "alias" : "Enabled", 
      "editable" : true, 
      "domain" : 
      {
        "type" : "codedValue", 
        "name" : "EnabledDomain", 
        "codedValues" : [
          {
            "name" : "False", 
            "code" : 0
          }, 
          {
            "name" : "True", 
            "code" : 1
          }
        ]
      }
    }, 
    {
      "name" : "ANCILLARYROLE", 
      "type" : "esriFieldTypeSmallInteger", 
      "alias" : "AncillaryRole", 
      "editable" : true, 
      "domain" : 
      {
        "type" : "codedValue", 
        "name" : "AncillaryRoleDomain", 
        "codedValues" : [
          {
            "name" : "None", 
            "code" : 0
          }, 
          {
            "name" : "Source", 
            "code" : 1
          }, 
          {
            "name" : "Sink", 
            "code" : 2
          }
        ]
      }
    }, 
    {
      "name" : "TDATA_ID", 
      "type" : "esriFieldTypeDouble", 
      "alias" : "TDATA_ID", 
      "editable" : true, 
      "domain" : null
    }, 
    {
      "name" : "TTM_GEOID", 
      "type" : "esriFieldTypeDouble", 
      "alias" : "TTM_GEOID", 
      "editable" : true, 
      "domain" : null
    }, 
    {
      "name" : "UPI", 
      "type" : "esriFieldTypeString", 
      "alias" : "UPI", 
      "editable" : true, 
      "length" : 10, 
      "domain" : null
    }, 
    {
      "name" : "AP", 
      "type" : "esriFieldTypeString", 
      "alias" : "AP", 
      "editable" : true, 
      "length" : 10, 
      "domain" : null
    }, 
    {
      "name" : "UP", 
      "type" : "esriFieldTypeString", 
      "alias" : "UP", 
      "editable" : true, 
      "length" : 10, 
      "domain" : null
    }, 
    {
      "name" : "STATE_VALIDJARINGAN", 
      "type" : "esriFieldTypeString", 
      "alias" : "STATE_VALIDJARINGAN", 
      "editable" : true, 
      "length" : 50, 
      "domain" : null
    }, 
    {
      "name" : "FLAG_BONGKAR", 
      "type" : "esriFieldTypeSmallInteger", 
      "alias" : "FLAG_BONGKAR", 
      "editable" : true, 
      "domain" : null
    }, 
    {
      "name" : "FLAG_PINDAH", 
      "type" : "esriFieldTypeSmallInteger", 
      "alias" : "FLAG_PINDAH", 
      "editable" : true, 
      "domain" : null
    }, 
    {
      "name" : "GLOBALID", 
      "type" : "esriFieldTypeGlobalID", 
      "alias" : "GLOBALID", 
      "editable" : false, 
      "length" : 38, 
      "domain" : null
    }
  ], 
  "types" : [
  ], 
  "templates" : [
    {
      "name" : "Jumper TM", 
      "description" : "", 
      "drawingTool" : "esriFeatureEditToolPoint", 
      "prototype" : {
        "attributes" : {
          "ENABLED" : 1, 
          "ANCILLARYROLE" : 0, 
          "FLAG_PINDAH" : null, 
          "TDATA_ID" : null, 
          "TTM_GEOID" : null, 
          "UPI" : null, 
          "AP" : null, 
          "UP" : null, 
          "STATE_VALIDJARINGAN" : null, 
          "FLAG_BONGKAR" : null
        }
      }
    }
  ], 
  "capabilities" : "Query,Editing"
}

Basically Emap service and EmapMXD service are reference to same Map document( MXD file), but Emap service reference to published MXD file.

take a look at http://wiki.gis.com/wiki/index.php/Software_Performance_28th_Edition_%28Fall_2010%29#ArcGIS_Server_Optimized_Map_Service_Document_.28MSD.29
on ArcGIS Server Optimized Map Service Document (MSD) it say

There are some functional limitations with publishing with the MSD map document. Some of the nice features of the map publishing analysis report is that identified errors include hyperlinks to online Esri Help providing instructions for resolving errors and optimizing performance.

so the different between MXD and MSD based map service capabilities are

Network Analysis : MXD : Yes , MSD : no
Feature Layer Editing : in my context MXD : Yes , MSD : no . It's in my context, i don't know is it true or false.

but MSD is faster then MXD.
so.. is MSD really doesn't have capability for editing feature and save into database like MXD?