Deploy individual applications via reverse proxy

Permanently deleted user

9. November 2012 05:56

I'm in the process of getting our first ArcGIS Server services and Geocortex Essentials applications published.  Our web server is being made available to the internet via a reverse proxy server.  We currently make only the the AGS Services (http://webserver/ArcGIS/Rest/Services) folder and subdirectories available to the internet.  As we create applications via Geocortex Essentials, we'd like to add individual entries to the reverse proxy server to point internet users to each application.  Is there any documentation for GE on how best to do this?  I did find the "How to make a Silverlight site available externally" document, and understand that I'll need to be sure the proper URL is coded into each site and application.  But, I'm also under the impression that there may be a setting file that needs to be set up for each site or viewer to make sure all the pieces work.  If I were using one of the ESRI APIs, it might be proxy.ashx and/or proxy.config.  Within Essentials, I found GisProxySettings.xml, but haven't found any documentation on how to use/distribute this file.  Any suggestions to point me in the right direction?  Let me know if this post is more appropriate for my specific viewer forum.

0

• 

  Permanently deleted user

  9. November 2012 06:45

  Hi Alice,

  Using a reverse proxy with Essentials should be fairly straightforward:

  1. Make sure all of the urls are pointing to the reverse proxy

  2. Set the External Rest Url in the Rest Application Settings, which is located at the bottom of the Sites list when you first log in to Rest Manager. For more information on setting the External Rest Url, click on the '(for use with a reverse proxy)' link to open the Help

   

  -Victoria

  0
• 

  Permanently deleted user

  10. November 2012 03:56

  Thanks - looks pretty straight-forward.

  0
• 

  Permanently deleted user

  12. November 2012 11:12

  Can you use the Geocortex manager through a reverse proxy?

  When I go to look at the viewers in the manager the HTML5 can be edited, but the Silverlight gives me an error about the viewer.xml not being able to be found.  That's because the address it's looking for is the internal address?

  Something gone wrong with the install of the template?

  Even when I log on locally I don't get a properties page for the viewer.

   

  HTML5 working all ok.

  0
• 

  Permanently deleted user

  12. November 2012 23:10

  Peter, the Viewer.XML file is loaded by the silverlight viewer, then it goes to the REST endpoint located in that file. If the Viewer file is failing to open it is because the URL path to it is either wrong (not fully qualified) or is not inaccessible.

  Take a look at your viewer URL. You will notice it has a parameter pointing to a long HTTP path with viewer.xml at the end. Paste just that into an external system and try to "fix" the URL so it does retrieve the document. Once it opens in the viewer, check the XML tag "SiteURI" property to make sure that URL is correctly specified and fully qualified to the REST endpoint. Simply pasting it into a web browser should open the REST endpoint for the site, which tells you it is correct.

  With both the REST endpoint URL in the viewer.XML file correct, and the VIewer.XML file accessible via a URL, try to form a new HTTP load with the new path to the viewer.xml file. Take a look at the example I have put below to get an idea.  The servername.latitudegeo.com portion is repeated twice and should be consistent to work.

  http://<strong>servername.latitudegeo.com</strong>/SilverlightViewer_1_7/Viewer.html?ViewerConfig=http://<strong>servername.latitudegeo.com</strong>/Geocortex/Essentials/REST/sites/CharlotteArcGISOnline/viewers/demo/virtualdirectory/Config/Viewer.xml

  The "manager" link and the "external" link for your site will likely be very different. So do not copy the manager link and give it out to external people. If that is the case, give external people accessing it through the proxy the "hand crafted" URL. 

  Good luck,

  -S

  0
• 

  Permanently deleted user

  14. November 2012 07:25

  My problem was in the end that I had to go through web.configs in REST and the Manager and changed the ServiceBaseUrl and EssentialsUrl.  Also changed the RestManagerSettings.xml.

  0
• 

  Permanently deleted user

  15. November 2012 08:44

  Peter has the correct answer here. When nothing is accessible except through the proxy you must change your EssentialsURL (configured in the Manager web.config file) to also point at the proxy address.

  This is mostly an internal fix for using REST Manager and isn't always required. Often internal users do not need to use the reverse proxy, and in this case this configuration is optional.

   

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.