Setting SkylineGlobe Server and TerraExplorer Fusion Settings
To set SkylineGlobe Server settings:
1. From the SkylineGlobe Server menu, select Settings. The Settings page is displayed.
2. Select the required category of settings:
§ General
§ WFS/WMS
3. The Setttings panel for the selected category is displayed. Make the required changes and click Save.
General Settings
|
Server Name |
The server name as reported to clients. According to the WFS/WMS standard, some of the requests arriving to the server require the SGS to include the server name and title in its reply. This has no practical impact effect on the functioning of SGS. Note: This setting is only displayed for super administrators. |
|
Server Title |
The server description as reported to clients. According to the WFS/WMS standard, some of the requests arriving to the server require the SGS to include the server name and title in its reply. This has no real effect on SGS work. Note: This setting is only displayed for super administrators. |
|
The publicly accessible base address that end users use to connect to SGS (e.g., https://cloud.skylineglobe.com). This may differ from the server’s internal IP and is typically set up via DNS, proxy, or routing by IT. SGS uses this URL when generating service responses (e.g., WMS, WFS, WMTS, Esri) to ensure links are reachable by client applications. Note: This setting is only displayed for super administrators. |
|
|
Authorization Mode |
Select Forms or Custom: § Default mode enables you to manage client registration and authentication at the application level, instead of relying on the authentication mechanisms provided by the operating system. When Forms authentication is selected, SGS will use standard login security to establish connections. You must specify a login ID and password for all connection requests. § Custom - Contact [email protected] for information on implementation. Note: This setting is only displayed for super administrators. |
|
Language |
Select the language for the SGS Manager’s user interface and error messages. |
|
Enable Auto-Scan |
Switch on to enable auto-scan for all data sources that have been set for auto-scan. All data sources except SG Upload have an Auto-Scan setting in their property sheet See "Adding Data Sources" in the "Working with Data Sources" chapter for more information. Note: This setting is only displayed for super administrators. |
|
Enable CORS |
Switch on to enable Cross Origin Requests (CORS). This enables cross-origin resource sharing, allowing requests from pages hosted on domains other than the SGS domain. Note: Enabling CORS may also be necessary if you have multiple domain names that point to your SkylineGlobe Server. Note: This setting is only displayed for super administrators. |
|
SameSite Cookies |
Determines whether session cookies should be sent only to pages from the same domain as your SGS, or also to pages hosted on other domains (third-party servers), e.g., a TerraExplorer Fusion application that is deployed on a non-SGS domain or an external web application that is accessing layers from SGS. Cookies are required for accessing non-public layers, i.e., layers with restricted view and edit access. A session cookie is sent when a user logs in to SGS via the GUI or API or using an access token. Select one of the following options: § Strict – Cookies will only be sent to your SGS domain, i.e., non-public layers will only be streamed to pages hosted on your SGS. Cookies will not be sent by SGS in response to requests initiated from other domains (Default). § Lax – Reserved. Do not use. § None – Cookies will also be sent to pages hosted on domains other than your SGS domain, i.e., non-public layers will also be streamed to pages not hosted on your SGS. The recommended default for this option is that all browser requests must be secure, i.e., follow the HTTPS protocol. If you want to allow streaming over a non-secure HTTP connection (e.g., for internal testing), clear the Secure option. and in the client-side browser, disable the setting that limits non-SameSite cookies to secure connections. Note: If SameSite Cookies was set to None and Secure (i.e., to use HTTPS protocol), but you don't actually have access to your site via HTTPS, you will not be able to open SGS Manager to correct the settings. In this case, append the following parameter to the SGS Manager URL: Note: This setting is only displayed for super administrators. |
|
SG Services Configuration File |
A file configuring the address search provider and the available OSM feature and map layers in TerraExplorer for Desktop. It is recommended to save the file to a shared drive that is accessible from all servers. Note: Changes can be made to the file by editing the file on the disk. If working with a cluster and using a local path, the edited file should be copied to the same local path on all the computers in the server cluster. Note: This setting is only displayed for super administrators. |
|
Cache Folder |
Sets the folder where SGS stores its cache. When requests are made to an SGS layer, it caches the request so that next time the SGS can serve clients’ requests in the most efficient way without loading the database. Cache is only created for 3D Tiles, feature layers in database data sources (Oracle Spatial, SQL Server, or PostgreSQL), and DirectConnect projects. The cache folder is very important to the work of the SGS. For best performance, this folder should be located on a high-speed storage device. For better cache management of a cluster, it is recommended to store the cache on a shared network drive. Note: In a DirectConnect project, cache files are automatically located in TBP_Cache under the Cache Folder. Note: This setting is only displayed for super administrators. |
|
Switch this option on to serve 3D Tiles in GLB format with Draco compression, for reduced size and better streaming. |
|
|
Enable Categories Mechanism |
Switch this option on to enable the category mechanism. See "Enabling Layer Categories" in the "Working with Layers" chapter for more information. |
|
Display Categories for Anonymous Users |
Switch this option on to display the categories panel in the Layers dialog also for non-logged in users. See "Enabling Layer Categories" in the "Working with Layers" chapter for more information. |
WFS/WMS Settings
|
Public WMS/WFS URL |
URL that WFS/WMS clients use to connect to SGS (Read-only). |
|
Maximum WFS Response Size |
Maximum size for WFS feature requests, from 1 to 100 MB. |
|
JPEG Quality |
Move the slider to adjust JPEG quality. Note: This setting is only displayed for super administrators. |
|
Image Quality |
Move the slider to adjust image quality. Note: This setting is only displayed for super administrators. |
|
Maximum WMS Image Size |
Maximum WMS image response size, from 256 to 2048 pixels. Note: This setting is only displayed for super administrators. |
TerraExplorer Fusion (TEF) Settings
SkylineGlobe Server includes TerraExplorer Fusion (TEF), a powerful 3D GIS viewer that allows you to view and analyze high-resolution, stunningly realistic 3D content in your web browser. See "What is TerraExplorer Fusion (TEF)" in the "Basic Concepts" chapter for more information.
The TEF project is created in TerraExplorer Pro by publishing a project to SkylineGlobe Server.
TerraExplorer Fusion can have custom configurations that define various elements of TEF including login mode, language, startup script, and CSS styling. These TEF elements are configured in the TerraExplorer Fusion Settings section of the Settings page. Multiple customized configurations can be set.
|
Add New Configuration |
Click Add New Configuration to set TerraExplorer Fusion Settings. The TerraExplorer Fusion Settings dialog is displayed. See "Configuring Your TerraExplorer Fusion" in the "Customizing TerraExplorer Fusion" chapter for information. |
DirectConnect Settings
These settings determine DirectConnect behavior when a TerraBuilder Project (TBP) is not being accessed.
Note: These settings are only displayed for super administrators.
|
TBP Connection Timeout Duration |
Determines the time (in minutes) that the TerraBuilder resources remain connected to a project after last accessing it. Note: The two most recently accessed projects are always kept active. This timeout applies only to any additional projects beyond those two. |
|
Minimum Number of TBP Connections to Keep Alive |
Determines the minimum number of connections SkylineGlobe Server should maintain alive (even when a TBP is not being accessed). By default, SkylineGlobe Server automatically shuts down the connection when a TBP is no longer being accessed, after the time set in the Free TBP Connection parameter. Keeping some connections live minimizes the startup time for subsequent accesses to the same project, but also uses up memory on each of the computers allocated resources for DirectConnect processing. |
|
Maximum Number of Threads per TBP |
Sets the number of threads on each host that will serve each TBP. |