License Mechanism

SkylineGlobe Server is protected by a licensing mechanism that controls its operation, license term, and available modules. A license file issued by Skyline determines the licensing mechanism used.

The following licensing mechanisms are available for SkylineGlobe Server:

§   Skyline Cloud Floating License Server

§   Local Hardware Protection (USB Key)

§   Workstation Dependent Software License

Note:    Local hardware protection (HASP key) and HASP floating license are no longer supported.

 

Skyline's Cloud Floating License Server

The license information can be obtained using Skyline’s cloud floating license service, which enables a number of licenses to be shared among a larger number of users through Skyline’s secure cloud infrastructure. Unlike the Skyline Floating License Server (SFLS), which must be installed and maintained on your organization’s network, the cloud service is fully hosted and managed by Skyline. This eliminates the need for local server setup, simplifies IT administration, and makes floating licenses accessible to users wherever they have an internet connection.

When an authorized user wants to run TerraExplorer, the application connects to Skyline’s cloud licensing service using the access token provided in the Skyline Store account. If a license is available, the cloud service grants TerraExplorer permission to run. When the user finishes running TerraExplorer, the license is automatically returned to the cloud license pool for use by other users.

Floating licenses can also be “checked out,” enabling them to function as machine-dependent licenses that do not require an active internet connection while in use. The availability of licenses for checkout and the length of the checkout period are defined by the Skyline cloud license service. Licenses checked out by a client via the License Manager can later be checked back in to return them to the license pool. See “Configuring TerraExplorer to Use Skyline's Cloud Floating License Server (SFLS)” in this chapter for details.

Note:    As an alternative to the cloud floating license, Skyline also provides an option to self-host a floating license pool on your own network using the Skyline Floating License Server (SFLS).

Configuring TerraExplorer to use Skyline's Cloud Floating License Server (SFLS)

 To configure TerraExplorer to use Skyline’s cloud floating license:

1.       Open the License Manager. See "License Manager" in this chapter for information.

2.       To set the floating license server URL, from the File menu, select Set Floating License Server. The Floating License Server dialog is displayed.

3.       In the Server URL field, enter the Skyline cloud license service URL in the following format: https://cloud.skylineglobe.com/sws/[ACCESS_TOKEN]

4.       Log in to your Skyline Store account (https://cloud.skylineglobe.com/store/account), copy your Access Token, and replace [ACCESS_TOKEN] in the URL with this value.

5.       Click Apply to save your settings.

 

Loading the Self-Hosted Skyline Floating License on Each of the SkylineGlobe Servers

When using a Skyline Floating License Server, you must load the floating license on each of the SGS machines that is sharing the license.

Note:    When SkylineGlobe Server is running in a server cluster, all servers in the cluster share a single license, i.e., only a single license needs to be requested from the license server.

 To load your Skyline Floating License on a SkylineGlobe Server machine:

1.       Close any open Skyline applications.

2.       For Windows deployment, in your Windows Server Manager, toggle the setting for IE Enhanced Security Configuration (for both administrators and users) to OFF.

3.       Place the license file in the correct location

§   Windows: root of the server directory

§   Docker/Kubernetes: config subdirectory within the server directory

4.       Set the LicenseServerURL parameter to the location of the license file:

§   Windows Deployment – in appsettings.json, under the "ServerConfig": section, add the following:

§   Docker Compose Deployment – In docker-compose.yaml file, under the environment: section, add the following:

§   Kubernetes Deployment – In deployment.yaml, under the env: section, add the following:

Local Hardware Protection (USB Key)

A USB key is a physical hardware key delivered with the SGS software package that plugs into the USB port of the computer – to allow the operation of the product. Verify that the USB key is plugged into the USB port before starting SGS. 

Workstation Dependent Software License

Another type of license is the workstation dependent software license. This license does not require any hardware protection but is limited to a specific computer. Before working with the workstation dependent software license, you must first register to get a license locked to your computer. The license cannot be transferred without repeating the registration process.

When SkylineGlobe Server is running in a server cluster, the server on whose machine the license is locked can share its license with all the other servers in the cluster. If for any reason, however, this machine is disconnected from the cluster, the license will stop running on the other servers.

License Manager

The License Manager allows the user to view and update the current license level.

 To activate the License Manager:

§   From the Windows start menu, select SkylineGlobe Server > LicenseManager.

The License Manager window is displayed.