Steps to allow access to map resources in Web Player or Automation Services

Steps to allow access to map resources in Web Player or Automation Services

The updated map charts require access to web-based resources to display the map layer. Many companies have their Web Player and Automation Services servers running on machines with limited Internet access, which results in an error when attempting to view map charts. In the Web Player client, the error reported is: "Error when downloading map chart service list from http://geoanalytics.tibco.com/service/services-list.json." See the attached screen shot (Filename: Web_Player_json error.png). In the Web Player debug log there will also be an error similar to:

=====

DEBUG 2014-07-24 14:49:04,773 [WorkThread 17, ABCD\username WAT 1]

Spotfire.Dxp.Application.Visuals.MapComponents.Util.MapTileServiceJsonRest - Error when reading Json from

http://geoanalytics.tibco.com/service/services-list.json

System.Net.WebException: Cannot resolve host name 'geoanalytics.tibco.com'.

=====

In Automation Services there may not be an error, but the default map layer is missing from the saved/exported map charts.

Spotfire and IIS use the security settings in Internet Explorer to reach the online map resources.

1). Add the following URLs to the Trusted Sites section in the Internet Explorer (IE) Security settings on the Web Player or Automation Services server machine:

http://geoanalytics.tibco.com/

http://tilescf.maporama.com/

The second URL is used for web distribution of tiles. It is based on the Amazon cloud front. If this does not resolve the problem, then modification of a proxy server to allow access to these resources may be required. There are two possible steps to this process. The first of these steps may be enough to allow access:

2). Configure the existing Proxy server settings in the web.config file as outlined in the Web Player Installation manual or the Spotfire.Dxp.Automation.Launcher.exe.config file as outlined in the Automation Services Installation manual.

a). Add the proxyaddress to the PROXY SERVER: section.

b). Add the ProxyUsername and ProxyPassword to the credentials section.

a) <!-- ********* PROXY SERVER: **********--> =====
<configuration>
<system.net>
<defaultProxy>
<proxy
proxyaddress="http://MyProxyServer:3128"

scriptLocation="MyScriptLocation"
/>
</defaultProxy>
</system.net>
</configuration>
=====

b) <!--Proxy -->
=====

<!-- You need to set the system.net/defaultProxy/proxy: proxy address to use this. -->

<!-- Proxy username/password for communication between Web Player Server and Spotfire Server. -->

<setting name="ProxyUsername" serializeAs="String">

<value />

</setting>

<setting name="ProxyPassword" serializeAs="String">

<value />

</setting>

=====

For most authentication methods (Kerberos, NTLM, etc.), the ProxyUsername and ProxyPassword fields must be filled in to specify credentials that have permission to access the Proxy Server. If this does not resolve the problem, or if an error occurs when trying to launch the Web Player, a bypasslist may be necessary to allow the Web Player to communicate with the Spotfire Server.

3). Extend the PROXY SERVER section to include the following block of code to create a 'bypasslist', which identifies addresses that do not need to go through the Proxy server.

=====

<configuration>

<system.net>

<defaultProxy >

<proxy

usesystemdefault="true"

proxyaddress="http://192.168.1.10:3128"

bypassonlocal="true"

/>

<bypasslist>

<add address="[a-z]+\.contoso\.com" />