Difference between revisions of "License Management"

From T-VEC Wiki
Jump to: navigation, search
(Specifying License File Location)
(Introduction)
 
Line 7: Line 7:
  
 
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.
 +
 +
==System Requirements==
 +
License manager software is available for 32 bit Microsoft Windows operating systems, including NT, 2000, XP, Server 2003, and Vista.
  
 
==Obtaining Licenses==
 
==Obtaining Licenses==
Line 52: Line 55:
  
 
==Installing Licenses==
 
==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.
+
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===
 
===Installing a Node-Locked License===
Line 71: Line 74:
 
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.
 
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.====
+
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:
 
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:
Line 107: Line 112:
 
</pre>
 
</pre>
  
The final line in the output indicates that a license was successfully checked out.
+
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==
 
==Problems or Issues==
Line 114: Line 183:
  
 
===Reference Material===
 
===Reference Material===
System administrators may be familiar with the Flexlm license management system, but support information can be found at [http://www.macrovision.com/pdfs/flexnet_licensing_end_user_guide.pdf Flexlm User Guide] or at the [http://www.macrovision.com/support/by_category/Software_Licensing.shtml Flexlm Support Website]
+
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