KB302369: New feature for ESRI On-Premise map based on local ArcGIS server to run in a purely intranet environment

Description

Strategy Web 10.4 introduced the enhancement mentioned in Knowledge Base article KB217892 about using the ESRI on-premises map, based on local ArcGIS server run in a purely intranet environment.
 
To be able to take advantage of this feature, complete the following steps in a local environment:
(Please refer to KB485792  about configuring version 4.x ESRI on-premise map based on local ArcGIS server to run in a purely intranet environment.)
 

1. The ESRI on-premises customer should download the ESRI JS API (v3.14) and install it in the intranet environment according to the guidelines (

   install.htm

   or

   install_linux.htm

   ) in the installation file. For this, the next steps need to be followed if using a Tomcat Server:
   
1. Copy the

   arcgis_js_api\library

   folder and all its contents from the downloaded file to the target web server. In this example, the files are copied to:

   <apache_tomcat_home>/webapps/arcgis_js_api/library

2. Edit

   init.js

   and

   dojo.js

   files to include the URL to the server and directory:
   
• Open

  <apache_tomcat_home>\webapps\arcgis_js_api\library\3.14\3.14\init.js

  in a text editor and search for the text

  '[HOSTNAME_AND_PATH_TO_JSAPI]'

  , and replace this text with

  "<myserver>:<port>/arcgis_js_api/library/3.14/3.14/"

• Open

  <apache_tomcat_home>\webapps\arcgis_js_api\library\3.14\3.14\dojo\dojo.js

  in a text editor and search for the text

  '[HOSTNAME_AND_PATH_TO_JSAPI]'

  , and replace this text with

  <myserver>:<port>/arcgis_js_api/library/3.14/3.14/'

• For more detailed install notes, you can refer to the

  install.htm

  (for Windows IIS Web Server) or

  install_linux.htm

  (for Tomcat Web server) under

  "/arcgis_js_api/library/3.14/".

2. Add a configuration in the

   esriConfig.xml

   file under the ESRI plug-in:

   <jsapiurl url="http(s):<myserver>:<Port>/arcgis_js_api/library/3.14/3.14" />

   . The value of the

   "url"

   attribute should point to the installed ESRI JS API server url.
3. Save the configuration file and restart the web server.

The above steps must be followed in order for the ESRI map to use this configured URL to load the JS API. Otherwise, if you cannot find this configuration in the

esriConfig.xml

file or you are using a cloud-based service, you will load the JS API from ESRI server as of now.

Troubleshooting Tips

1. Using the fully qualified domain name (FQDN) as <myserver> usually works well; however, for troubleshooting purposes, try using the short name of the server name.
2. Make sure each URL mentioned above can be successfully assessed via browser.

Third Party Software Installation Warning

The third-party product(s) discussed in this technical note are manufactured by vendors independent of Strategy. Strategy makes no warranty, express, implied or otherwise, regarding these products, including their performance or reliability.