nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Issues with Deploying Flex App

MatthewBullock

I have a SFV flex app ready for external deployment. We have had the application running on an internal server and recently moved the web server out to the data center that hosts our other websites. The server is running IIS 6 and Windows Server 2003. I copied the release build folder over to the wwwroot of the web server and create a virtual directory with the folder after we moved the server.

I had a release build create prior to moving the web server external and it worked fine internally. Now that the same web server has moved outside of our network, when I try to open the URL for the release build (i.e. Http://.../.../index.html) I get a white screen. Other files (.html, .pdf, etc) display properly when viewed from the server browser and my desktop browser.

I can view all of the files within the release build folder(s) from both the server and my desktop browser, so the permissions appear to be set up correctly. But I am not sure why the .swf within the HTML wrapper is not displaying properly. It seems like it is an IIS setting I am missing.

Does anyone have an suggestions/ideas? Thanks in advance.

-Matt

Encontre mais publicações marcadas com

Accepted answers

All comments

RamakrishnaBillakanti

Robert,

Actual plan is to deploy service only on the intranet. Probably in the future after approval we may go ahead and plan to deploy the project on the internet.

RobertScheitlin__GISP

Ramakrishna,

Than how do you plan to deploy this app externally?...

RamakrishnaBillakanti

Robert,

This is an internal server for which data is not accessible over the internet.

RobertScheitlin__GISP

Ramakrishna,

The fact that I can not even open http://pfoc2.uanet.edu/ tells me you have a big issue.

RamakrishnaBillakanti

Here are the link i'm using for deploying the app,

http://pfoc2.uanet.edu/ArcGIS/rest/services/Accessibility3/MapServer

MatthewBullock

Ramakrishna,

I was able to pinpoint the issue. I'm transferring the release build files from my desktop to the web server via the internet. The internet security settings on the web server were not allowing the AC_OETags.js file to be downloaded with the release build folder. So the HTML wrapper file was not displaying properly. I switched the internet security settings from high to medium high and I was able to download the AC_OETags.js file. The application is running properly now.

I'm not sure if it is what you are encountering but thought it may be helpful.

Same problem I've also encountered........Help would be highly appreciated.

Thank you

MatthewBullock

Since we are still testing the new setup I don't want to put the URL on the forums. I can send it to you via email though. My email is mbullock@azgfd.gov.

Thanks Robert.

Matt,

What is the URL? It could be a firewall issue.

RobertScheitlin__GISP

Matt,

What is the URL? It could be a firewall issue.

MatthewBullock

I went through and change the URLs to fully qualified names using the new IP for the web server. We have a simple setup, so in my case the web server is also the ArcGIS Server and is outside the firewall.

I moved another simple flex app to test and see if it was just the one app with the issue and the second app will not display either. The HTML wrapper displays, but it is a blank white page. The .swf doesn't display at all.

I was using the web server that we moved externally as the web server that I was developing the project. So when I moved the server I had to remove the output folder URL for the project. Now it creates the release build on a local drive on my desktop. Would that cause any issues? That is the one thing that changed within the project settings in flex builder.

Guys,

Are you using the fully qualified name of the external server in your config.xml. What I mean is internally urls like

http://gisserv2/arcgis/rest/services/ParcelOrthos/MapServer

would work but now it would have to be

http://gis.calhouncounty.org/arcgis/rest/services/ParcelOrthos/MapServer

This is also assuming that the server that you have moved out side the firewall is also the ArcGIS Server.

RobertScheitlin__GISP

Guys,

Are you using the fully qualified name of the external server in your config.xml. What I mean is internally urls like

http://gisserv2/arcgis/rest/services/ParcelOrthos/MapServer

would work but now it would have to be

http://gis.calhouncounty.org/arcgis/rest/services/ParcelOrthos/MapServer

This is also assuming that the server that you have moved out side the firewall is also the ArcGIS Server.

RamakrishnaBillakanti

Same problem I've also encountered........Help would be highly appreciated.

Thank you

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.