Difference between revisions of "License Management"

From T-VEC Wiki
Jump to: navigation, search
(Installing Licenses)
(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 110: Line 115:
  
 
===Installing a Floating License===
 
===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.
+
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====
 
====Server Setup====
 
+
For an overview of floating licenses and details on setting up a license server, please see [[Floating_License_Sever_Setup]].
  
 
====Client Setup====
 
====Client Setup====
Line 120: Line 125:
 
[[Image:license_config_tool_floating.png]]
 
[[Image:license_config_tool_floating.png]]
  
Specify the license server name and optionally the port on which to communicate with the license server.
+
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>
 
<pre>
port@server
+
port@servername
 
</pre>
 
</pre>
 
In this example, the settings are
 
In this example, the settings are
Line 128: Line 135:
 
27007@license_server
 
27007@license_server
 
</pre>
 
</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
+
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>
 
<pre>
 
SERVER license_server 00609798439d 27007
 
SERVER license_server 00609798439d 27007
 
</pre>
 
</pre>
  
====Verifying the license configuration.====
+
====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 176: 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