Scott, There is no requirement to look at the IdentifyWidget.xml for anything, I will just helping you diagnose your issue. What it all boils down to is that you can not use localhost in one place and the machine name in another and have the code understand that both are pointing to the same layer (even though they are). The identify widget checks if the layers that you have configured exist in the map as a base map or operational layer and the means that it does this is by comparing the URLs. The fact that flex is a CaSe sensitive language means that Valhalla and valhalla are NOT equal and thus the widget does not detect that the layer is in the map and obviously the comparison of localhost and valhalla are not equal so same issue. If you have a map service added as an operational layer and its type is dynamic then the widget check if the configured identify layer is a sub layer of that parent map service. So there is the in-depth explanation of what is going on under the hood.So what are you next steps.You do need to check into the issue with the fact that you have the web adaptor installed and you still have to use 6080. I would call tech support on this one.You should start a new configuration of the Identify widget by deleting the old one from the "Widgets in this application" and re-adding it and use "http://valhalla:6080/arcgis/rest/services/WebMap/MapServer" when you browse for layers to add, or if you get number one done then use your new url.
Scott, So you have several issue that you would have also seen if you were trying to manually edit the IdentifyWidget.xml yourself.You have '>http://localhost:6080/arcgis/rest/services/WebMap_v2/MapServer. You should not be using localhost in any of your urls unless you have also added the layer using localhost in your main config.xml.You have '>http://Valhalla:6080/arcgis/rest/services/WebMap_v2/MapServer/6 You can not mix CaSe in your URLs as Flex is a CaSe sensitive language. Your main config.xml has http://valhalla:6080 (with a lower case "v") so your IdentifyWidget.xml needs the same. Next is I am not sure at all how the /6 got on the end of the url as that is normally part of the id tag and not the url that is written to the IdentifyWidget.xml.
Scott, There are no layers listed at all in the IdentifyWidget_1.xml?... Did you save your edits after you configured yur changes? Do you have a IdentifyWidget_#.xml with a higher number like 2 or 3 in your C:\inetpub\wwwroot\flexviewers\WQv3\widgets\Identify\ folder?
Scott, Having the map service added to the map as a dynamic map service is fine. So Can you provide me your main config.xml and your IdentifyWidget_1.xml to look at?
Scott, The difference is that the eSearch does not need the layer to exist in the map as an operational layer or basemap and the identify widget DOES. So the question is do you have that map service added as an operational layer (either the whole mapservice as a dynamic layer or a specific layer of the map service as an feature layer)?
Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.