BookmarkSubscribeRSS Feed
Nigel_Pain
Lapis Lazuli | Level 10

SAS 9.4M7 on Windows 2012 R2, with middle tier SAS Studio and VA 7.5

I'm trying to enable the geo mapping elements of VA, which requires access to SAS' Open Street Map servers via a proxy. For this it appears I need to add a number of options to the JVM, namely

-Dhttp.proxyHost=proxy.domain -Dhttp.proxyPort=80 -Dhttp.nonProxyHosts=\"localhost|127.0.0.1\" -Dhttps.proxyHost=proxy.domain -Dhttps.proxyPort=443

 

  1. Am I correct in thinking I need to add these to the JVM_OPTS environment variable in setenv.bat for the webapp, and also as extra wrapper.java.additional.xx= lines in the wrapper.conf?
  2. Do the double quotes in the -Dhttp.nonProxyHosts options need to be escaped (I'm guessing so, as the options were supplied by Tech. Support).
  3. Is it absolutely necessary to add these options to all webapps, or only the one for VA (SASServeer12_1)?

Many thanks.

1 REPLY 1
JeremiahBoswell
SAS Employee

Hi Nigel,

 

It appears that you might have found SAS Note 52133 and are attempting to implement the configuration changes described within it. If you have not reviewed this SAS Note, please do so.

I have attempted to answer each of your questions, as well as provide additional information near the end of this post. Please see my responses below:


1. Question: What files need to have forward proxy related Java Virtual Machine (JVM) options added in order for geo maps to be displayed in SAS Visual Analytics?

In environments where the operating system is a version of Microsoft Windows, these forward proxy related JVM options should only be added to the applicable SAS Web Application Server instance wrapper.conf file.

 

Note: For the proxyHost and proxyPort options specifically, you will want to use the HTTP and/or the HTTPS versions depending on which protocols your forward proxy server is configured. For example, if the forward proxy is configured for HTTP--but not HTTPS--you would specify the following (the http.nonProxyHosts option is always specified):

 

...
wrapper.java.additional.nn=-Dhttp.proxyHost=proxy-server-name
wrapper.java.additional.nn=-Dhttp.proxyPort=proxy-port-number
wrapper.java.additional.nn=-Dhttp.nonProxyHosts="localhost|127.0.0.1|host-name|IP-address-of-middle-tier-machine"

If the forward proxy server requires authentication, you would also need to add the proxyUser and proxyPassword options--again, HTTP and/or HTTPS versions depending on your forward proxy server's protocols:

 

...
wrapper.java.additional.nn=-Dhttp.proxyUser=user-name
wrapper.java.additional.nn=-Dhttp.proxyPassword=password

(For all options mentioned, nn specifies the next sequential numbers.)

 

2. Question: For the -Dhttp.nonProxyHosts JVM option, do the double quote characters (") need to be escaped using backslash characters (/)?

 

No; In Windows environments, string values specified for JVM options within the SAS Web Application Server instance wrapper.conf files are surrounded by unescaped double quote characters.

 

3. Question: In Windows environments, do the forward proxy related JVM options for Visual Analytics geo map display needed to be added all SAS Web Application Server instance wrapper.conf files?

 

No; These options only need to be added to the wrapper.conf file for the SAS Web Application Server instance(s) on each SAS Middle Tier machine where the SAS Visual Analytics web applications are deployed. For environments containing multiple instances, these are typically the SASServer12_Y instances.

For most environments with multiple instances, only one has Visual Analytics deployed on it: SASServer12_1 ('Y' equals 1). If vertical clustering is enabled, 'Y' equals 1, 2, etc.


----

If not already known, you will need to contact your networking team to determine if your environment has a forward proxy server prior to making such configuration changes. If your environment has one, its hostname and other information can be provided for the mentioned JVM options. If, after adding them, geo maps are not displayed, your networking team should check if a firewall is preventing access to the OpenStreetMap URLs.

 

If your environment does not have a forward proxy server, then your networking team will need to make sure that the machine where Visual Analytics is deployed has network access to the OpenStreetMap URLs instead.

 

If, after checking firewall settings in your environment, geo maps are still not displayed, you should inform SAS Technical Support, as they will need some more information from you for further investigation.

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 1 reply
  • 1172 views
  • 1 like
  • 2 in conversation