This is an archive related to a previous version of Esri Maps for MicroStrategy. If you need the current version go to http://doc.arcgis.com/en/maps-for-microstrategy/.
Under some circumstances, Esri Maps for MicroStrategy uses an internal proxy mechanism to broker communication with the ArcGIS platform (in addition to any web services referenced by retrieved ArcGIS items). When required, Esri Maps for MicroStrategy sends HTTP requests to the proxy, and the proxy forwards the requests to the remote web server (such as ArcGIS). The proxy then relays the response back to Esri Maps for MicroStrategy.
The internal proxy is not used if Esri Maps for MicroStrategy and all the data and web services it uses are on the same domain, or if both the client browser and all servers support Cross-Origin Resource Sharing (CORS). In most production environments, however, this configuration is not common, and configuring the internal proxy is recommended.
Most modern browsers use the recommended standard, Cross-Origin Resource Sharing (CORS). The CORS standard adds headers to the HTTP specification that allow servers to describe the set of origins that are permitted to read resources and services using a web browser.
Esri Maps for MicroStrategy automatically detects servers that use Cross-Origin Resource Sharing (CORS) and communicates with these servers without issue. In some cases, however, the initial request (an HTTP POST, for example) is automatically routed through the Esri Maps for MicroStrategy internal proxy, even though the server is CORS-enabled. As an Esri Maps for MicroStrategy administrator, you can list the URLs for known CORS-enabled servers in the Esri Maps for MicroStrategy configuration file (settings.js) to ensure that all calls originating from those locations are automatically considered CORS-enabled, thereby bypassing the proxy.
To specify CORS-enabled servers:
Each URL must be enclosed within quotation marks, with multiple URLs separated by commas.
For example: corsEnabledServers: ["mapserver.mycompany.com", "otherserver.othercompany.com"]
Although the internal proxy is designed to work with minimal custom configuration, you can customize its settings to allow only requests to specific servers; that is, you can specify the resources to which the proxy will forward requests.
To configure the internal proxy settings, modify the proxy configuration file using a standard text editor.
The proxy configuration file (proxy.config) is located in the proxy directory that applies to your environment:
The default location is C:\Program Files (x86)\MicroStrategy\Web ASPx\plugins\em4mstr\asp\proxy.config.
For example, when installing on Tomcat, the default location is Tomcat/webapps/MicroStrategy/plugins/em4mstr/jsp/proxy.config.
To define the URLs that Esri Maps for MicroStrategy is allowed to access, specify each individual URL in a separate serverUrl child element. Create a separate serverUrl element for every server that Esri Maps for MicroStrategy must access to retrieve map services.
<ProxyConfig mustMatch = "true">
To test the internal proxy, route an HTTP request through it. If the proxy returns the expected value, it is working correctly. The following steps provide examples of calls that simulate the HTTP traffic that Esri Maps for MicroStrategy would generate.
For ASP.NET configurations:http://Your_IIS_SERVER_URL.com/MicroStrategy/plugins/em4mstr/asp/proxy.ashx?www.TEST_URL.com
For J2EE configurations:http://Your_JSP_SERVER_URL.com/MicroStrategy/plugins/em4mstr/jsp/proxy.jsp?http://www.TEST_URL.com
For example, each of the following URLs should return a JSON object that describes the version of the software installed on the server.
For example, each of the following URLs should return a JSON object that describes the version of the software installed on the server:
A successful result means that your proxies are properly configured and working as expected.
In situations in which Esri Maps for MicroStrategy must use its internal proxy, the internal proxy must be able to forward HTTP requests to the intended target resources (such as map services). In some environments, firewall rules prevent these requests from being sent; for example, the firewall may prevent HTTP traffic from leaving the internal network.
To solve this problem, you can configure an upstream forwarding proxy.
An upstream proxy allows connections outside the network without compromising the security of the internal network. One common approach to using an upstream proxy is to place a proxy server in a perimeter network to protect the internal network.
The upstream proxy itself represents an enterprise-level, third-party (non-Esri) solution. It is not part of Esri Maps for MicroStrategy.
The Esri Maps for MicroStrategy proxy configuration file contains elements that allow you to configure an upstream proxy.
To configure upstream proxy settings, modify the proxy configuration file using a standard text editor.
<useUpstreamProxy enabled = true>