Recent Changes

Differences

This shows you the differences between two versions of the page.

--- dev:technology:core:web_resources [2021/01/12 17:40]
jeroen
+++ dev:technology:core:web_resources [2023/10/06 09:10] (current)
jeroen [IT Troubleshooting]
@@ Line 20: / Line 20: @@
   * https://ogc.org/standards/wfs
-=== Current supported versions ===
+=== Supported versions ===
   * WMS versions 1.1.0, 1.1.1 and 1.3.0
   * WMTS version 1.0.0
-  * WFS versions 1.1.0, the support of version 2.0 is on our wishlist. Let us know if you are interested.
+  * WFS versions 1.1.0, 2.0.0
 === Remarks ===
@@ Line 36: / Line 36: @@
 There are 2 options to establish a connection to a WebService:
-=== File-based WebService Configuraiton ===
+=== File-based WebService Configuration ===
 Establish the connection using an Orbit configuration file to a well-defined WebService Layer. \\
-This file-based configuration supported by all products and today's recommended solution.
+This file-based configuration is supported by all products and today's recommended solution.
-  * [[dev:technology:supported_formats:image:owxs|]].
+More information, see [[dev:technology:supported_formats:image:owxs|]].
-=== Legacy WebService Connection ===
-Establish the connection using the Legacy Orbit Desktop Resource Library or Orbit EOS Console user interface, and add runtime one or more WebService Layers. \\
-This legacy approach is not supported in the 3DM Publisher Console and 3DM Viewer.
-  * Orbit desktop : [[dev:desktop:workspace:resource_library]] > Web
-  * Orbit EOS server : [[dev:server:console:resources:datasets_setup|]]
 ==== WebService CRS and Orbit Map CRS ====
@@ Line 58: / Line 50: @@
 ==== WebService in Orbit 3DM Viewer ====
-Special attention is required to use WMS and WMTS layers in the Orbit 3DM Viewer, see [[dev:technology:supported_formats:image:otm_for_wms|]].
+Special attention is required to use WMS and WMTS layers in the Orbit 3DM Viewer. \\
+More information, see [[dev:technology:supported_formats:image:otm_for_wms|]].
 ===== Tiled Map Service =====
-Orbit supports pyramid-based tile services as made popular by OpenStreetMap. \\
+Tiled Map Services (TMS) are made popular by Google and OpenStreetMap. \\
 More information, see [[https://en.wikipedia.org/wiki/Tiled_web_map|Tiled web map]].
-=== Setup Connection ===
+==== Supported Versions ====
-web service resource connection file
+The common standards and custom pyramid-based tile services are supported by Orbit.
-**Tiled map resource connection file** \\
+==== Orbit Connection to Tiled Map Service ====
-Configure the tiled map service connection and the web resource to load, cfr web services (see above).
-  * [[dev:technology:supported_formats:image:otm|]]
-===== SSL Security Certificates =====
+There is only 1 option to establish a connection to a Tiled Map Service.
-When loading web resources via a secured HTTPS connection, the website's Security Certificate must be available to the Oracle's Java Runtime Engine used by Orbit. \\
+=== File-based Tiled Map Configuration ===
-More information, see [[dev:technology:platforms:java_keystore|]].
-===== Network connectivity =====
+Establish the connection using an Orbit configuration file to a well-defined Tiled Map Layer, see [[dev:technology:supported_formats:image:otm|]].
-To use a Web-based resource a successful connection to the providing server/service is required.
+===== IT Troubleshooting =====
-If no network connection could be established, obviously Orbit will not be able to load the resource. Review the documentation below on how to check the connection from the local network to the web service.
+This paragraph documents common IT issues related to loading web resources.
+==== SSL Trusted Authority ====
+When loading web resources via a secured HTTPS connection, the website's Security Certificate must be available to the Java Runtime Engine used by Orbit. \\
+If the certificate is not known to the Java Runtime Engine, the following message is printed in the [[dev:technology:platforms:logfiles|Orbit logfile]]:
+  javax.net.ssl.SSLHandshakeException:
+  sun.security.validator.ValidatorException: PKIX path building failed
+  sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
+For more information and how to solve it, see [[dev:technology:platforms:java_keystore|]].
+==== SSL Mixed Content ====
+==== Network connectivity ====
+To use a Web-based resource a successful network connection to the providing server/service is required. \\
+If no connection could be established, obviously Orbit will not be able to load the resource. Review the documentation below on how to check the connection from the local network to the web service.
 If a network connection is successful, but Orbit can't load resources, most probably the Orbit application is not allowed to get online/network access due to an internal internet security application (e.g. aXsGUARD Gatekeeper from Vasco). The network and/or local computer administrator need to adjust your security settings or configure a proxy to be used by Orbit :
   * Orbit desktop standalone : [[inhouse:orbit:config|]].
-  * Orbit Server and Orbit desktop Client : [[dev:server:eos:service|]].
+  * Orbit Server and Orbit desktop Client : [[dev:publisher:orbit_eos_service|]].
 === Check Local network - Service connection ===
@@ Line 95: / Line 101: @@
 In the example below a connection to the OpenStreetMap service is tested :
-**Successful connection** \\
+  * Successful connection \\ {{:technologies:resources:otm_test_successful.png?nolink|}}
-{{:technologies:resources:otm_test_successful.png?nolink|}}
+  * Failed connection \\ {{:technologies:resources:otm_test_not_successful.png?nolink|}}
-**Failed connection** \\
-{{:technologies:resources:otm_test_not_successful.png?nolink|}}

Last modified:: 2021/01/12 17:40