Licensing an STK Engine Application

This document will help AGI STK Engine technology users better understand what licenses they need to develop and/or deploy custom STK Engine applications in the various operating environments supported by the STK Engine.

STK Engine Runtime Licensing Rules

Development

Windows. Developing an STK Engine application on Windows requires an STK license. Depending on the capability implemented within the STK Engine application, additional licenses may be required to execute all of the application’s functionality.

UNIX. Developing an STK Engine application on UNIX requires an STK Engine for UNIX license. The STK Engine for UNIX license is a purchased license with STK Pro capability.

Deployment

Windows. Deploying an STK Engine application on Windows requires that the end user has an STK Engine Runtime license with a valid vendor ID or an STK license. Depending on the capability implemented within the STK Engine application, additional licenses may be required to execute all of the application’s functionality. Deploying to a paying customer requires the customer has a purchased license (STK Pro, STK Engine Basic Runtime, etc.).

UNIX. Deploying an STK Engine application on UNIX requires that the end user has an STK Engine Runtime for UNIX license with a valid vendor ID or an STK license. The STK Engine for UNIX license is a paid license with STK Pro capability. Depending on the capability implemented within the STK Engine application, additional licenses may be required to execute all of the application’s functionality. Deploying to a paying customer requires the customer to have a purchased license (STK Pro, STK Engine Basic Runtime, etc.) with the STK Engine for UNIX extension.

Installation

Windows. The license comes in the form of an encrypted text file with a .lic extension. This file must be saved in some location where the STK Engine application will look for it. Hard-coded license locations include:

Alternatively, the folder location of the license file can be specified via the STKD_LICENSE_FILE environment variable.

If the license file is to be installed by the end-user, the programmer may wish to include the STK License Manager in the install. If the License Manager is installed on the machine, the user can double-click on a license file to install the license.

UNIX. The license comes in the form of an encrypted text file with a .lic extension. This file must be saved in some location where the STK Engine application will know to look for it. Hard-coded locations include:

Alternatively, the folder location of the license file can be specified via the STKD_LICENSE_FILE environment variable.

Recommendation

Always specify a valid Vendor ID (Application Key) for each STK Engine Runtime control (Globe, Map, Graphics Analysis, etc.). This will help you avoid any potential problems that may arise from using invalid vendor ID in your deployed application.

Obtaining a Deployment License

To obtain a deployment license for an STK Engine application, contact AGI technical support by:

Include your Vendor ID with your license request.

STK Programming Interface 11.0.1