Difference between revisions of "License Management"

From T-VEC Wiki
Jump to: navigation, search
(Introduction)
(License Management)
Line 8: Line 8:
 
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 [http://en.wikipedia.org/wiki/Flexlm FlexLM] to implement its licensing.
 
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 [http://en.wikipedia.org/wiki/Flexlm FlexLM] to implement its licensing.
  
==License Management==
+
==Obtaining Licenses==
Access to the T-VEC toolset is controlled by license management. A valid license key is required to operate the tools. T-VEC generates and distributes encrypted license keys based on the number of licenses purchased.
+
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.
  
Licenses can be managed as node-locked or as floating. Node-locked licenses are generated for and used by specific machines, while floating licenses are shared among a group of networked machines. Floating licenses are more flexible as they allow licenses to be shared by multiple users. For example, two licenses may be used to support 5 developers as long as only 2 developers require access to the tools concurrently.
+
===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.
===License Registration===
+
License keys are distributed by T-VEC support. To obtain licenses, contact Support with the target machine’s identification information. In a node-locked setup, submit the machine identifier for the workstation that will be running the tools. In a floating setup, a license manager controls the license keys. Submit the machine identifier of the machine that runs the license management software.
+
 
+
===Machine Identification===
+
In order to uniquely identify a machine, the T-VEC license management scheme uses the machine’s ethernet address and hard disk serial number. Thus, machines must be equipped with an ethernet card or adapter in order to execute the tools and/or operate as a license server. This is true regardless of whether license management is setup as nodelocked or floating.
+
  
 +
====Hostids On Windows====
 
Open a command window (DOS window) and execute the command
 
Open a command window (DOS window) and execute the command
  
Line 51: Line 47:
 
</table>
 
</table>
  
'''The important information is the Physical Address (e.g. 00-11-22-AB-DC-33)'''
+
'''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:
 +
<pre>
 +
c:\t-vec\license\license.dat
 +
</pre>
 +
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.
 +
<pre>
 +
t_vec -version
 +
</pre>
  
 
==Problems or Issues==
 
==Problems or Issues==

Revision as of 12:08, 1 June 2008