License Server Features and Management

<< Click to Display Table of Contents >>

Navigation:  Enterprise > Installation and Configuration > EQuIS Licenses >

License Server Features and Management

License Server Overview

 

EQuIS Product Licenses are Managed within the EQuIS Database

 

Network Licenses are saved in the ST_LICENSE table. This table stores the product code, encrypted key string, product name, and supports links to External License Database. EarthSoft recommends that the user save keys to the ST_LICENSE table using the registration form of the application (register.exe).

 

The Network ID string is longer than the Computer ID, and the Network ID is a number generated from the server name and database name as reported by the database server. As such, keys are tied to a particular database. If that database is moved to another server, then the Network ID will change, and new registration keys are required. Please plan accordingly when moving or renaming database servers.

 

When a user checks out a network license, they are said to acquire a license lease. Leases are issued when the number of held leases is less than the maximum number of concurrent use licenses available. Those values are displayed on the registration form. Each lease is issued for a 15 minute period. EQuIS Professional products will automatically renew their lease before that expiration period is reached. If for any reason the lease is not renewed, the license becomes available for other users.

 

When EQuIS renews its product leases, it verifies their authenticity. If the authentication fails, EQuIS releases the lease and attempts to acquire a new lease. If no licenses are available at that time, the Evaluation form is displayed with the message "Failed to acquire license". If EQuIS cannot renew the lease because of trouble connecting to the database server, a warning message is displayed. The message informs the user that EQuIS will automatically exit if it cannot renew the lease within the subsequent 15 minutes.

 

License Server Linking

 

Organizations managing several EQuIS databases may wish to designate one as the Network License database. Optionally, the Database Administrator may setup a separate Network License database to manage concurrent licenses for an organization. See the Creating an External License Database section below for additional information. If License Server linking is enabled with an EQuIS database, no other keys are used within that database. EQuIS will follow up to five (5) links before it stops searching for a license server. EarthSoft recommends minimizing the number of links to a license server.

 

To setup License Server Linking, the Systems Administrator will need to:

1.Create a license database OR choose an EQuIS Database where licenses currently reside.

2.Create a link from an unlicensed database, to point to the license database of Step 1.

3.Register the application (if the license database OR licenses do not already exist.)

 

This article covers Step 1 and Step 2 of the process, with additional information regarding license servers.

 

Creating an External License Database

 

By default, EQuIS will use the EQuIS database originally logged into as its licensing server. With the license server linking feature, it is possible to designate a different database to manage all the keys in an organization. The database managing EarthSoft product keys does not need to be an EQuIS database. If an EQuIS database is not used, the external license database must be accessible by all workstations that will consume network licenses and needs to contain the tables ST_LICENSE, ST_LICENSE_USE, ST_VERSION, and ST_USER.

 

A standalone license database contains only the tables required to manage licenses. This is created and updated through SQL Server Management Studio and is not available connecting through EQuIS Professional. A standalone license database can be used with all EQuIS Products, including Standalone EDP. End users should review the release notes on each new release to determine if standalone license databases requires a Schema update.

 

A separate EQuIS database can also be used as a license database. Caution should be used when using an EQuIS database as a license database as these databases can be connected to through Professional and data could be loaded into this 'license database.' The script_ExternalLicenseDatabase_v7.zip SQL statement from the EarthSoft Community Center (ECC) Downloads Dashboard (under All Items > Products > Additional Resources > v7.0) will create the standalone license database and table structure required by EQuIS. After the database is created, an SQL login should be created with read/write access for each table.

 

Linking an EQuIS Database to the License Database

 

For more than one EQuIS database to share network licenses, a connection string must be created that points to the database containing the licenses.

 

To create a link from the unlicensed EQuIS database to the license database:

1.Create a record in the unlicensed database's ST_LICENSE table with the following information:

APP_ID=1023

KEY_TYPE=4

2.In the LICENSE_SERVER field, enter a plain text connection string for the server and database acting as a license server. Upon successful login, EQuIS will encrypt the connection string and save it back to ST_LICENSE.

3.If Network Licensing is available on the target database, the Server name, Database name, and a new Network ID will be displayed on the registration form.

4.The ST_LICENSE.LICENSE_TITLE can be set to provide information about the link. For example, "Link to database 'Training' on server 'Primary', SQL Login as 'Student'".

 

Note: If license server linking is used, the database should only contain the one record defined above, while the actual licenses reside on the license server.

 

Connection String Examples (for reference)

 

SQL Server with Windows Authentication

Data Source=dbserver;Integrated Security=SSPI;Database=licensedb;

SQL Server with SQL Authentication

Data Source=dbserver;User ID=someusername;Password=somepassword;Database=licensedb;

 

 

Information on Changing License Servers

 

Network Keys are bound to the Network ID for the database storing the keys. If the database server name (or database name) changes, the Network ID will also change. Any existing keys bound to the old Network ID are rendered invalid. Organizations planning to move or rename their database server should plan accordingly.

 

EarthSoft recommends:

1.Setting up the new server.

2.Requesting new keys be issued prior to the actual move. This will prevent any loss of productivity during the transition.

 

 

License Use History

 

EQuIS tracks usage history for all products using Network Licenses. This information is saved in the ST_LICENSE_USE table and includes the following fields:

APP_ID – The webkey identifier for the product.

WORKSTATION – The workstation used to consume the license. It is a concatenation of the computer name environment variable, the CPU ID, the volume serial number of the first hard drive, and the network MAC address.

USER_NAME – The database login name used when acquiring the license, and reflects the connection type used when first opening EQuIS. For Windows Authentication, the user name is the Windows Login. For SQL Authentication, the name is the Database Management System login name. For Application Level Security, the name is the value of ST_USER.USERNAME from the database the user connected to when starting EQuIS. In the case of a master license server, it could be the credentials used to connect to the license database as stored in another EQuIS database ST_LICENSE table.

LICENSE_CHECKED_OUT – The date and time when the record was created. The time is given in Coordinated Universal Time (UTC).

LICENSE_EXPIRES

For Professional licenses, this field is populated every 5 minutes with an expiration date that is 15 minutes in the future. The LICENSE_EXPIRES is set to the current date and time upon successful termination of a session. Thus, values set in the future indicate current leases, while expiration dates in the past represent historical usage data. Since expiration dates are automatically set to 15 minutes in the future, session duration is accurate to within 15 minutes, even in the event of power failure or loss of network.

For Enterprise 7 licenses, this field populates with a date for expiring 30 years in the future (or until the user is disabled or deleted through the User Manager Widget).

CHECKSUM – Determines if the license-use record was modified while the license was checked out.