Difference between revisions of "License Management"

From T-VEC Wiki
Jump to: navigation, search
(Machine Identification)
(Introduction)
 
Line 1: Line 1:
 
==Introduction==
 
==Introduction==
Access to the T-VEC Toolset is controlled by a license management scheme supported by flexlm. A valid, encrypted license key must be installed for the software to operate. The toolset supports license management in node-locked and floating configurations. In node-locked licensing each machine running the toolset requires a machine-specific key. In a floating configuration, a set of licenses is shared by multiple computers on a network. Floating licenses require the installation of a license manager to control license usage on the network.
+
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.
  
By default the toolset is installed to operate in a node-locked configuration. To prepare the toolset for operation, a license key must be obtained from T-VEC. To setup a floating license configuration, the license manager software must be installed on a machine designated as the license server, and a set of floating licenses must be obtained for that specific machine.
+
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.
  
==License Management==
+
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.
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.
+
  
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.
+
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 Registration===
+
==System Requirements==
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.
+
License manager software is available for 32 bit Microsoft Windows operating systems, including NT, 2000, XP, Server 2003, and Vista.
  
===Machine Identification===
+
==Obtaining Licenses==
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.
+
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 name and hostid.  
  
Open a command window (DOS window) and execute the command
+
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====
 +
To obtain the hostid on a Windows machine, open a command window (DOS window) and execute the command
  
 
   ipconfig /all
 
   ipconfig /all
Line 47: Line 52:
 
</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.
 +
 
 +
====Specifying License File Location====
 +
The location of a license file is specified with the T-VEC License Configuration Tool. Start the License Configuration Tool through Start -> T-VEC -> Utilities -> T-VEC License Config.
 +
 
 +
[[Image:license_config_tool.png]]
 +
 
 +
Specify the location of the license file through the System or User Settings and click 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.
 +
 
 +
Multiple license files can be specified by separating each with a semicolon.
 +
 
 +
====Verifying the Setup====
 +
 
 +
The version command in the T-VEC console tool attempts to check out a license after displaying version information. This is a convenience mechanism for verifying license configuration. The version command is specified as follows:
 +
<pre>
 +
t_vec -version
 +
</pre>
 +
The output produced by the tool is similar to the following example:
 +
<pre>
 +
T-VEC Console Tool 3.8.0  Copyright 1996-2008 T-VEC Technologies, Inc.
 +
 
 +
Licensed To:
 +
User: User Name
 +
Company: T-VEC
 +
Installation: 20-4-2008 11:29:3
 +
License File:
 +
  (T-VEC Specific) C:\T-VEC\license\license.dat
 +
  (Environment)    Value Not Set
 +
 
 +
T-VEC Version 3.3.0 (build 1573) for Windows NT4, 2000, XP
 +
  T-VEC Compiler                  8.3.0  (verified)
 +
  T-VEC Vector Generator          10.3.0  (verified)
 +
  T-VEC Coverage Analyzer          4.0.0  (verified)
 +
  T-VEC Inference Engine          10.1.0  (verified)
 +
  T-VEC Mapper Generator          2.0.0  (verified)
 +
  T-VEC Vector Formatter          5.1.0  (verified)
 +
  T-VEC Test Driver Generator      3.0.2  (verified)
 +
  T-VEC Cross Comparator          3.0.0  (verified)
 +
  T-VEC API                        3.1.2  (verified)
 +
    Specification Parser          3.0.0  (verified)
 +
    Knowledgebase Parser          3.0.0  (verified)
 +
    Test Vectors Parser            3.0.0  (verified)
 +
    Mapper Parser                  3.0.0  (verified)
 +
 
 +
Requesting license...granted
 +
</pre>
 +
 
 +
The final line in the output indicates whether a license was successfully checked out.
 +
 
 +
===Installing a Floating License===
 +
Floating licenses are managed by a license server. Each client machine communicates with the server to request license access.  The license server should be setup and tested prior to setting up client machines to use the server.
 +
 
 +
====Server Setup====
 +
For an overview of floating licenses and details on setting up a license server, please see [[Floating_License_Sever_Setup]].
 +
 
 +
====Client Setup====
 +
In a floating license setup, each client machine communicates with the license server across the network. The location of a license server is specified with the T-VEC License Configuration Tool. Start the License Configuration Tool through Start -> T-VEC -> Utilities -> T-VEC License Config.
 +
 
 +
[[Image:license_config_tool_floating.png]]
 +
 
 +
Specify the license server name and optionally the port on which to communicate with the license server and click the Set button to save the changes. 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.
 +
 
 +
The license server is identified in the following format.
 +
<pre>
 +
port@servername
 +
</pre>
 +
In this example, the settings are
 +
<pre>
 +
27007@license_server
 +
</pre>
 +
where "license_server" is the name of the server and 27007 is the port on which to communicate with the server. Port 27007 is the default for T-VEC tools, but can be changed in the license file. The license server port is typically stored in the first line of the license file on the license server.  For this example, this first line would look something like this
 +
<pre>
 +
SERVER license_server 00609798439d 27007
 +
</pre>
 +
 
 +
====Verifying the Setup====
 +
 
 +
The version command in the T-VEC console tool attempts to check out a license after displaying version information. This is a convenience mechanism for verifying license configuration. The version command is specified as follows:
 +
<pre>
 +
t_vec -version
 +
</pre>
 +
The output produced by the tool is similar to the following example:
 +
<pre>
 +
T-VEC Console Tool 3.8.0  Copyright 1996-2008 T-VEC Technologies, Inc.
 +
 
 +
Licensed To:
 +
User: User Name
 +
Company: T-VEC
 +
Installation: 20-4-2008 11:29:3
 +
License File:
 +
  (T-VEC Specific) 27007@license_server
 +
  (Environment)    Value Not Set
 +
 
 +
T-VEC Version 3.3.0 (build 1573) for Windows NT4, 2000, XP
 +
  T-VEC Compiler                  8.3.0  (verified)
 +
  T-VEC Vector Generator          10.3.0  (verified)
 +
  T-VEC Coverage Analyzer          4.0.0  (verified)
 +
  T-VEC Inference Engine          10.1.0  (verified)
 +
  T-VEC Mapper Generator          2.0.0  (verified)
 +
  T-VEC Vector Formatter          5.1.0  (verified)
 +
  T-VEC Test Driver Generator      3.0.2  (verified)
 +
  T-VEC Cross Comparator          3.0.0  (verified)
 +
  T-VEC API                        3.1.2  (verified)
 +
    Specification Parser          3.0.0  (verified)
 +
    Knowledgebase Parser          3.0.0  (verified)
 +
    Test Vectors Parser            3.0.0  (verified)
 +
    Mapper Parser                  3.0.0  (verified)
 +
 
 +
Requesting license...granted
 +
</pre>
 +
 
 +
The final line in the output indicates whether a license was successfully checked out.
 +
 
 +
==Problems or Issues==
 +
===Firewalls===
 +
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 [http://www.globes.com/support/flexnet_licensing_end_user_guide.pdf Flexlm User Guide] or at the [http://www.google.com/search?q=flexlm+support Flexlm Support Website]

Latest revision as of 10:23, 2 July 2008