topic Re: config.xml service url format question in ArcGIS Viewer for Flex Questions

config.xml service url format question

ScottBackstrom — Wed, 26 Dec 2012 20:58:55 GMT

Greetings!

Using flexviewer 2.5 and I have been testing on our internal IP and all is good, however, when i test outside the network it won't display the layers.

http://www.ottertailcounty.net/flexviewers/lakes/

I am guessing this is a format issue of how I am calling the services, for example i am using layer:

inside config.xml

<layer type="tiled" label="Terrain" url="http://INTERNAL_IP:6080/ArcGIS/rest/services/Terrain/MapServer" visible="true"/>

Works inside the network but not outside, so my question is: For the outside world to see the maps, do i need to change all references to my domain name? Public IP? with or without the :6080?

I have tried the following but they wont resolve:

<layer type="tiled" label="Terrain" url="http://www.ottertailcounty.net:6080/ArcGIS/rest/services/Terrain/MapServer" visible="true"/>

<layer type="tiled" label="Terrain" url="http://www.ottertailcounty.net/ArcGIS/rest/services/Terrain/MapServer" visible="true"/>

<layer type="tiled" label="Terrain" url="http://66.228.239.237:6080/ArcGIS/rest/services/Terrain/MapServer" visible="true"/>

<layer type="tiled" label="Terrain" url="http://66.228.239.237:6080/ArcGIS/rest/services/Terrain/MapServer" visible="true"/>

none seem to work.

Maybe another question would be: How do I access my Manager from outside the network?
From inside it is: LOCALIP:6080/arcgis/manager/
If I am getting there from outside, what would i use? Domain name? Domain name + :6080?

Any suggestions?

Re: config.xml service url format question

RobertScheitlin__GISP — Wed, 26 Dec 2012 21:19:21 GMT

Scott,

If you install the web adaptor that is on the ArcGIS Server disk than you will be able to use a URL that does not have the :6080 in it. The other major issue you are hving is you need to use the eternal URL in each layers urls in your config.xml be cause if you mix and match urls then you will get security sandbox issues (assuming you do not have the proper crossdomain.xml setup).

Re: config.xml service url format question

ScottBackstrom — Thu, 27 Dec 2012 12:42:44 GMT

Robert, Thanks for the quick reply!

So to clarify, I need to change my code to point to the EXTERNAL ip address once I get the Web Adapter installed?

Now running into a new issue when attempting to install the web adapter ArcgGIS for Server Enterprise 10.1

Error 2878. On the dialog WebSiteList the control
ListBox1 has a possible value:Default Web Site,80,1.
This is an invalid or duplicate value.

Re: config.xml service url format question

ScottBackstrom — Sat, 11 Dec 2021 23:23:59 GMT

Scott,
(assuming you do not have the proper crossdomain.xml setup).

My crossdomain.xml file located in c:\inetpub\wwwroot\

<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM "http://www.adobe.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
    <site-control permitted-cross-domain-policies="all"/>
    <allow-access-from domain="*"/>
</cross-domain-policy>

Which i believe is correct.

Re: config.xml service url format question

RobertScheitlin__GISP — Thu, 27 Dec 2012 12:47:53 GMT

Scott,

My current install does not use the web adaptor but I use a apache reverse proxy server (basically the same as the web adaptor) and yes you use the external server urls in the main config.xml. As far as the error you are running into... You need to give support a call.

Re: config.xml service url format question

ScottBackstrom — Thu, 27 Dec 2012 13:05:38 GMT

Yes, Thank you. I am waiting for a call back from support. Will let you know how it goes.

Re: config.xml service url format question

ScottBackstrom — Thu, 27 Dec 2012 15:39:49 GMT

I am able to resolve the site using the domain name (instead of the ip address) now after successfully install of the Web Adapter.

The issue for the web adapter is that the setup can???t resolve the list of websites when multiple websites have the same binding.
In my case, I did discover that there was two items in IIS with the value of 80. I temporarily changed one to 1001 and the other to 100. Then changed them back to 80 after the install.