GeoBase Licenses |
Using GeoBase requires a valid license. GeoBase licenses can have any name, but must have a .lic extension.
Important |
---|
The user account being used to run your GeoBase application must have full read and write permissions to the license file. Without these permissions the license file cannot be activated. |
Note |
---|
License seat activations are tied to individual workstations and significant changes to hardware may require license re-activation. If your license requires re-activation, contact gbsupport@verizonconnect.com. |
There are two license types:
SDK license - An SDK license allows you to use GeoBase to develop applications for distribution.
Three SDK license levels are available:
'Standard' with support for basic functionality and 5 seat activations
'Professional' with support for most commonly used features and 10 seat activations
''Enterprise' with support for GeoBase premium features and 20 seat activations
Additional seats are also available for purchase in blocks of 5.
On first use, an SDK license will automatically contact the Verizon Connect licensing server for an initial 100 day activation. When this 100 day activation period has expired, the licensing server (http://licenses.telogis.com) will be contacted a second time for permanent license activation. Until this final activation occurs, the license remains subject to revocation in the event of non-payment or installation on more PCs than permitted. When final activation has succeeded, GeoBase will not typically contact the license server again unless significant changes are made to PC hardware. If an SDK license is unable to contact the licensing server 100 days after its initial activation, a 20 day grace period will begin. During this 20 day period the license will attempt to contact the licensing server on every use. If the initial 100 day trial period and this 20 day grace period pass without successful contact with the license server (totaling 120 days from the date of initial activation) the license will be disabled automatically.
SDK licenses are for development only - they should not be distributed with the applications you develop. Using an SDK license in any production or commercial deployment is a violation of your GeoBase End User License Agreement (GB EULA).
Like the trial license, an SDK license limits you to a fixed number of GeoBase operations, after which it expires. Maps in applications using an SDK license will display the text 'For development only.'
Runtime license - A Runtime license allows the applications that you deploy to use GeoBase features. Unlike trial and SDK licenses, Runtime licenses do not expire. However, they do not enable you to use the designer for developing applications -- you must use an SDK license for that. When you deploy your GeoBase application for production or commercial use, you must include a runtime license in one of the following ways:
Loose - If the license file is located in the same folder as geobase.net.dll it will be located and used automatically
Embedded - The license file is embedded into your application
To embed a license in your application, follow the steps below.
Add the license file to your project in Visual Studio.
Rename the license file to runtime.lic
Open the properties window for the license and set Build Action to Embedded Resource
Now when you build your application the license will be embedded in the executable. This will be found by GeoBase at runtime.
Imagine an ASP.Net application with both client and server executables.
On the server side it is simple to leave the license file in the bin directory of your ASP.Net application.
On the client side (which is going to be distributed) you must embed the license file in the application executable.
In order to validate some GeoBase licenses, your GeoBase application must contact a Licensing server over HTTP. These HTTP requests may need to use a proxy server in order to reach the Licensing server. You can configure the proxy server either using the registry or in code:
To configure the proxy using the Windows registry, add the key Software\Telogis\Licensing in either HKLM or HKCU. Under the new key, create string values called ProxyAddress, ProxyUsername, and ProxyPassword. Note that the ProxyUsername can, if necessary, include a domain: for example "MyDomain\\User" or @"MyDomain\User".
To configure the proxy in your application code, use System.Configuration.ConfigurationManager.AppSettings. For example:
string proxyAddr = "http://localhost"; string proxyUser = "MyDomain\\User"; string proxyPass = "123"; System.Configuration.ConfigurationManager.AppSettings.Set("Xheo.Licensing.ProxyAddress", proxyAddr); System.Configuration.ConfigurationManager.AppSettings.Set("Xheo.Licensing.ProxyUsername", proxyUser); System.Configuration.ConfigurationManager.AppSettings.Set("Xheo.Licensing.ProxyPassword", proxyPass);