License Management

From T-VEC Wiki
Revision as of 12:08, 1 June 2008 by Admin (Talk | contribs)

Jump to: navigation, search



Use of the T-VEC toolset is controlled through license management. A valid license is required to operate the tools. T-VEC generates and distributes license keys based on the number of licenses purchased. Each T-VEC tool has a specific license key.

Licenses are managed as node-locked or floating. Node-locked licenses allow operation of the tools on a single specific machine, while floating licenses allow shared concurrent operation of the tools among a group of networked machines. The floating licenses limit the number of machines using the tools concurrently to the number of licenses purchased.

Floating licenses are more flexible as they allow multiple users to share the licenses. For example, two licenses could support five developers as long as only two developers require access to the tools concurrently. Floating licenses can be shared across LANs and WANs.

Floating licenses require the installation of a license manager server to control license usage on the network. The T-VEC toolset uses license management software called FlexLM to implement its licensing.

Obtaining Licenses

License keys are distributed in license files by T-VEC Support. The license file is a simple text file that contains details about each license key. To obtain licenses, contact Support with the target machine’s hostid. For node-locked licenses, submit the hostid of the machine running the tools. For floating licenses, submit the hostid of the machine acting as the license server.

Obtaining a Machine's Hostid

A machine's hostid is a unique identifier for that machine. Typically, the machine's hostid is the machine's ethernet address. In rare situations, the machine's hard disk identifier is used as the hostid.

Hostids On Windows

Open a command window (DOS window) and execute the command

 ipconfig /all

You should see something like:

Windows IP Configuration

        Host Name . . . . . . . . . . . . : computer_name
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : Yes
        DNS Suffix Search List. . . . . . :

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Network Connection
        Physical Address. . . . . . . . . : 00-11-22-AB-DC-33
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . :
        Subnet Mask . . . . . . . . . . . :
        Default Gateway . . . . . . . . . :
        DHCP Server . . . . . . . . . . . :
        DNS Servers . . . . . . . . . . . :

The hostid is the Physical Address (e.g. 00-11-22-AB-DC-33)

Installing Licenses

T-VEC support typically distributes licenses keys via email in a license file. The license file must be installed in a location accessible to the machine using the license.

Installing a Node-Locked License

The standard location for the license file is in the license directory located in the T-VEC installation. Generally, this file is named license.dat and is located as follows:


The license file’s name and location are not important, but they must be identified to the tools. If the license file is installed in the default location (license directory of T-VEC installation), the T-VEC tools will locate the file automatically. Otherwise, the location of the license file must be identified to the tools. Consult the following section on how to identify the license file location.

Specify the license file location by entering it in the System or User Level areas and clicking the Set button. Setting the value at the System level applies the value for all users and requires Administrator privileges to set. Applying the value at the User level applies the value only for the current user. Once the values are set, dismiss the dialog with the OK button. To verify the license configuration settings, use the version command in the console (command line) tool.

t_vec -version

Problems or Issues


License server issues may require specific ports to be opened when firewalls are in place. Port 27000 is the primary port, but it may be necessary to open ports 27000 and 27007.

Reference Material

System administrators may be familiar with the Flexlm license management system, but support information can be found at Flexlm User Guide or at the Flexlm Support Website