GMSC Discussions

GeoMedia Smart Client community discussion board is where you can create, contribute and share information and knowledge in regards to configuring as well as working with GeoMedia Smart Client. Find your answers, share your knowledge and help build a strong GeoMedia Smart Client community.
Showing results for 
Search instead for 
Do you mean 
Reply
New Contributor
Posts: 3
Registered: ‎07-23-2019

WMTS Layers not recognized (Connection failure?)

Hi there,

 

we have a problem displaying WMTS tiles at our customer in Austria. On our development system, the WMTS Layers are working perfectly fine, but when it comes to customers server and clients, it is a failure.

 

Some details about the server of the customer: it uses a SSL encryption and doesn't have internet access. 

 

I tried to load the WMTS from the clients, where the internet connection is available. I opened then the GMSC Administrator from the client and observed that when I try to add a new WMTS feature, the available parameters (Layers, Style, Format, Axis Order) arent't filled in automatically and I have nothing to choose from.

WMTS Error 

Same happens with the http://maps.wien.gv.at/basemap/1.0.0/WMTSCapabilities_31256.xml WMTS. When I'm loading these maps in browser, outside the Smart Client, there aren't any problems with them. 

 

On the other hand, when using OSM, the layers and their URL's are already predefined, so I can save them as a feature in Administrator. By starting the Smart Client and trying to load the OSM feature, an error message is written in the log file. 

 

This is a error message reported on a OSM Thunderforest Tile:

 

22.07.2019 15:51:45 SEVERE: The following tile can't be loaded because of an exception! [MapServiceFeatureTile[identifier=8_134_89; bounds=[-599854.39,337255.10,-493043.14,231722.78]; tileConnect=com.intergraph.web.plugin.osm.OSMFeatureTileCurator$OSMTileConnect@1daa9928]]    --> [pool-17-thread-1] com.intergraph.web.core.data.loader.ParallelFeatureLoader$1.call
java.net.UnknownHostException: c.tile.thunderforest.com
 at java.base/jdk.internal.reflect.GeneratedConstructorAccessor107.newInstance(Unknown Source)
 at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
 at java.base/java.lang.reflect.Constructor.newInstance(Unknown Source)
 at java.base/sun.net.www.protocol.http.HttpURLConnection$10.run(Unknown Source)
 at java.base/sun.net.www.protocol.http.HttpURLConnection$10.run(Unknown Source)
 at java.base/java.security.AccessController.doPrivileged(Native Method)
 at java.base/sun.net.www.protocol.http.HttpURLConnection.getChainedException(Unknown Source)
 at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source)
 at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
 at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Unknown Source)
 at com.intergraph.web.core.data.loader.MapServiceFileCache.openStream(MapServiceFileCache.java:178)
 at com.intergraph.web.core.data.loader.AbstractMapServiceLoader.processTile(AbstractMapServiceLoader.java:74)
 at com.intergraph.web.core.data.loader.ParallelFeatureLoader$1.call(ParallelFeatureLoader.java:63)
 at com.intergraph.web.core.data.loader.ParallelFeatureLoader$1.call(ParallelFeatureLoader.java:57)
 at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
 at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
 at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
 at java.base/java.lang.Thread.run(Unknown Source)
Caused by: java.net.UnknownHostException: c.tile.thunderforest.com
 at java.base/java.net.AbstractPlainSocketImpl.connect(Unknown Source)
 at java.base/java.net.SocksSocketImpl.connect(Unknown Source)
 at java.base/java.net.Socket.connect(Unknown Source)
 at java.base/sun.security.ssl.SSLSocketImpl.connect(Unknown Source)
 at java.base/sun.security.ssl.BaseSSLSocketImpl.connect(Unknown Source)
 at java.base/sun.net.NetworkClient.doConnect(Unknown Source)
 at java.base/sun.net.www.http.HttpClient.openServer(Unknown Source)
 at java.base/sun.net.www.http.HttpClient.openServer(Unknown Source)
 at java.base/sun.net.www.protocol.https.HttpsClient.<init>(Unknown Source)
 at java.base/sun.net.www.protocol.https.HttpsClient.New(Unknown Source)
 at java.base/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(Unknown Source)
 at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect0(Unknown Source)
 at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
 at java.base/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
 at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source)
 at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
 at java.base/sun.net.www.protocol.http.HttpURLConnection.getHeaderField(Unknown Source)
 at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.getHeaderField(Unknown Source)
 at com.intergraph.web.core.data.loader.MapServiceFileCache.openStream(MapServiceFileCache.java:166)
 ... 7 more

 

Could someone help me to solve this problem?

 

Thank you in advance Robot wink

Technical Evangelist
Posts: 658
Registered: ‎11-12-2015

Re: WMTS Layers not recognized (Connection failure?)

Hi mvernica,

 

It sounds like this issue is tied to customer's environment.

 

I as well dont have issues with the WMTS http://maps.wien.gv.at/basemap/1.0.0/WMTSCapabilities_31256.xml as a new feature.

 

What is the message in the console (F12 most browsers) when trying the WMTS at the customer environment? GMSC Admin relies on a connection to the 'URL' when gathering/auto populating the other parameters. If it can't connect it follows that it can't gather/auto populate.

Highlighted
Staff
Posts: 40
Registered: ‎02-27-2018

Re: WMTS Layers not recognized (Connection failure?)

Hi,

 

we had a similar issue: the url for WMTS-Capabilities was valid, but the GMSC did not recognize it. It was probably due to a firewall/network restriction.

What we did is as follow:

  • donwload the xml-Capabilities
  • save the file on the server where your installation is and where it ca be reached: e.g. www.myGMSCserver.net/doc/getCapabilties.xml
  • select the url to your version of the GetCapabilities when defining the WMTS in the Administrator

 

It solved our problem because the Administrator only needed access for the definition of the feature. Wenn the GMSC Client calls the WMTS the same restrictions in our case did not apply and the tiles were showing up, as planed.

Maybe it can help here as well.

 

Drawback: if the WMTS is changed or modified, it might break your configuration and you have to download the GetCapabilities again.

New Contributor
Posts: 3
Registered: ‎07-23-2019

Re: WMTS Layers not recognized (Connection failure?)

Thank for your answer. I saved the GetCapabilities document as xml, copied to the server where the GMSC installed is, but I don't know what should I specify under URL in Administrator. Should I specify the path to the xml document? For example:

 

C:\Program Files\Intergraph\WebApplications\GMSC\WMTS\httpmaps.wien.gv.atbasemap1.0.0WMTSCapabilities.xml

 

But if I do so, I will receive the message: I has to be a valid WMTS url. 

New Contributor
Posts: 3
Registered: ‎07-23-2019

Re: WMTS Layers not recognized (Connection failure?)

When trying WMTS in Administrator at the customer, the message in the console is: "SCRIPT438: Object doesn't support property or method 'then' " and it is pointing on the ig.capabilities.js 

Technical Evangelist
Posts: 1,165
Registered: ‎09-11-2015

Re: WMTS Layers not recognized (Connection failure?)

[ Edited ]

You should rather put it into e.g.

C:\inetpub\wwwroot\httpmaps.wien.gv.atbasemap1.0.0WMTSCapabilities.xml

And the reference it via web browser as

http://<your_server>/httpmaps.wien.gv.atbasemap1.0.0WMTSCapabilities.xml

Jan Neumann
Post Sales Engineer Web Applications
Hexagon Geospatial