Has anyone else been successful in deploying the JavaScript API on their own 10.1 server? Any ideas on what I might have done wrong?!
Yes.Check if you have adjusted the two files for each build (normal and compact) the right way.It has to look like this in init.jshttp:' : location.protocol) + '//' + "mymachine/arcgis_js_api/library/3.3/jsapi/js/dojo/dojo",hasCache
in dojo.jslocation.protocol) + '//' + "mymachine/arcgis_js_api/library/3.3/jsapi/js/dojo/dojo",hasCache
Check if the url works (with init.js in the end):http://mymachine/arcgis_js_api/library/3.3/jsapi/init.js
Check the API with the Test code provided in the install docu. If you get any error to this point, you don't have to adjust the Services Directory. Check the same after you set Default.ashx as the Default document. Check in IIS, if there is something inherited or not. Sometimes IIS made some problems for me, if someone has defined the Default.ashx as default document up at the C:/inetpub/wwwroot/arcgis_js_api level.And check the test code with different browsers. Maybe you simply have to put your domain to the trusted sites in IE. Depending on your company security levels, IE behaves differently.Someone pointed out here in the forums, that there is a simple step to get the >3.2 versions running for the REST services directory: Create a new css where you import the two css files (tundra.css and esri.css) and point the CSS value in the rest-config file to that css file.
/* used for the ArcGIS REST Services Directory View in ArcGIS
JavaScript. combines the two required CSS files */
@import "http://mymachine/arcgis_js_api/library/3.3/jsapi/js/dojo/dijit/themes/tundra/tundra.css"
@import "http://mymachine/arcgis_js_api/library/3.3/jsapi/js/esri/css/esri.css";
I can open the SDK documentation without problems. Unfortunetaly the samples still point to the internet URL but you can change that quickly on all files with an editor (or with a grep and sed command).HTH.