Difference between revisions of "License Management"

From T-VEC Wiki
Jump to: navigation, search
(→‎Verifying the license configuration.)
(→‎Installing Licenses)
Line 87: Line 87:
 
License File:
 
License File:
 
   (T-VEC Specific) C:\T-VEC\license\license.dat
 
   (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 license.
 +
 +
====Server 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.
 +
<pre>
 +
port@server
 +
</pre>
 +
In this example, the settings are
 +
<pre>
 +
27007@license_server
 +
</pre>
 +
where "license_server" is the name of the server and 27000 is the port on which to communicate with the server. 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 license configuration.====
 +
 +
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
 
   (Environment)    Value Not Set
  

Revision as of 14:01, 1 June 2008

Contents

Introduction

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 name and 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

To obtain the hostid on a Windows machine, 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. . . . . . : abc.efg.net

Ethernet adapter Local Area Connection:

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

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: 

c:\t-vec\license\license.dat

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.

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.

Verifying the license configuration.

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: 

t_vec -version

The output produced by the tool is similar to the following example: 

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

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 license.

Server 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.

License config tool floating.png

Specify the license server name and optionally the port on which to communicate with the license server. 

port@server

In this example, the settings are 

27007@license_server

where "license_server" is the name of the server and 27000 is the port on which to communicate with the server. 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 

SERVER license_server 00609798439d 27007

Verifying the license configuration.

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: 

t_vec -version

The output produced by the tool is similar to the following example: 

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

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 Flexlm User Guide or at the Flexlm Support Website

Retrieved from "http://www.t-vec.com/wiki/index.php?title=License_Management&oldid=3291"