This chapter introduces the licensing systems used in Telelogic Tau. Provided are both background material and practical tips on setting up and maintaining your licenses.
The following topics are discussed:
With Telelogic Tau there are two third-party-provided licensing systems, and which you will use depends on your networking situation:
Each system is introduced in detail below. You should have received your licensing materials with your delivery of Telelogic Tau.
If you have not yet received your license materials, or, if after reading this chapter you have questions, contact Telelogic Customer Support (see How to Contact Customer Support).
Both types of licensing systems use license keys which have individual expiration dates set by Telelogic, and can be renewed when needed.
Typically, license keys given for evaluation of the tool set are set for 30 days, renewable upon request and with approval from the appropriate Telelogic Area Manager.
Post-purchase license keys are typically set for one year, and are renewed. Customers with maintenance agreements will receive updated license keys for new versions of the tool upon their release. Customers without maintenance agreements will receive renewed keys for the version of Telelogic Tau that they initially purchased (that is, license keys for newer, up-to-date versions of Telelogic Tau will not be delivered).
Speak with your Telelogic Area Manager for further details on license renewals.
Licensing is done by "features" which are individual components of the Telelogic Tau tool set, such as SDT's Simulator or ITEX's C Code Generator.
A license key specifies the number of "seats" (simultaneously available licenses) for each feature of the tool set listed in the license key. The way the number of seats is controlled varies slightly between the two licensing systems. FLEXlm (floating) licenses allow the number of licenses available to be specified on a feature-by-feature basis. CopyControl licenses, since they are node-locked to a single-user machine, allow only one license for each feature listed. For reasons of technical differences between FLEXlm and CopyControl, they do not have the exact same featuring scheme.
FLEXlm is a network licensing system which consists of one or several license keys, license server "daemons", and the application(s) for which licenses are served. Licenses dynamically float around the network as needed.
The license "daemons" are background processes which run on a chosen "license server" machine. They administer the check-in and check-out of licenses for each feature of each application which uses FLEXlm.
Each machine on a network has two attributes which distinguish it uniquely from all other machines: the hostname and hostID. Host names are usually straightforward names for machines given by, perhaps, a system administrator. Examples are "einstein" and "suns20". The hostID is a number that uniquely identifies the machine and is obtained from different sources within a machine depending on the architecture. Examples are "80874ab9" (typical Sun style) and "080009734a85" (typical HP style).
There is one main FLEXlm daemon called "lmgrd", and one "vendor" daemon for each vendor whose software on the system uses FLEXlm. Telelogic's vendor daemon is simply called "telelogic". The "lmgrd" daemon will manage the vendor daemons, which in turn manage the licenses for their respective vendors' software. The "lmgrd" daemon and the vendor daemon(s) must run on the same physical node of the network, but they can run on any node; that is, you can choose any node on your network to be the FLEXlm license server.
A FLEXlm license key is a specially formatted text file containing:
Details of the structure of a FLEXlm license key are covered below.
FLEXlm license keys can come in three categories: "license keys", "evaluation license keys", and "DEMO license keys".
Both "license keys" and "evaluation license keys" require a valid hostname and hostID and require that the "lmgrd" and vendor daemon are correctly running on the license server specified in the license key file. The only difference between them is their durations; evaluation keys, of course, last for a much shorter time than "real" post-purchase keys.
"DEMO license keys" are used in uncommon situations when it may be difficult or impossible to obtain a proper hostname and/or hostID. This type of key does not require a specific hostname and hostID, nor does it require that the license daemons be running. This type of key is distinguished with the keyword "DEMO" appearing at the end of each feature line of the license key file. Also, the field in each feature line showing the number of seats is set to zero, although the feature can still be used. This type of key is typically reserved for emergency situations.
License keys for Telelogic training sessions will typically be evaluation license keys with very short durations (perhaps 5 days or so).
It is not necessary to install your Telelogic Tau software on the same node of the network that your license server runs on, although this is a common situation. You could install Telelogic Tau on a local disk and have your licenses served by another node on the network (to put it differently, you do not have to install Telelogic Tau on a disk that belongs to the same machine on which the license server will run). This is useful in situations when one member or a small part of a large organization will be using Telelogic Tau exclusively, but there is already an organization-wide FLEXlm license server on the network.
Since FLEXlm is designed for managing possibly many software packages from many vendors, it allows all license and daemon information for all vendors to be combined into one license key text file, instead of having to deal with a separate file for each vendor. If you already use FLEXlm for other software when you install Telelogic Tau, our Installation Guide will tell you how to add the license information you receive from Telelogic to your master license key text file.
If Telelogic Tau brings you to FLEXlm for the first time, then you will have only the "lmgrd" and "telelogic" daemons running, and the license key information you receive from Telelogic will make up your entire license key text file.
We suggest using the FLEXlm software included in the Telelogic Tau CD-ROM; for first time FLEXlm users this is of course what you will do. Existing FLEXlm users, however, may wish to upgrade their license server software with the Telelogic Tau-included version, if they are running an older version. Although this will cause a temporary interruption in availability for all FLEXlm administered software, it is a good idea since newer versions of the system are quite different. Although Telelogic keys are always backwards compatible, we cannot speak for other vendors, so it is generally best to make sure you run the latest daemons so as to be able to take advantage of new FLEXlm features. For your information, the version included on the Telelogic Tau CD-ROM is 6.1c.
On the following pages we give two examples of typical FLEXlm license keys as they appear when received from Telelogic. The first is a "real" license key (one requiring a valid hostname and hostID) and the second example is a DEMO key. Each example describes the "anatomy" of the license key. Being familiar with the different parts is very useful when trying to install the key properly.
When installed, the license key text file received from Telelogic should be saved with the filename license.dat. While this is not strictly necessary, some startup scripts may search for the license file using this name. This name is the standard in the FLEXlm "lingo" anyway.
|
Note: The default location for the |
Here is a FLEXlm "real" license key as it would appear when delivered by Telelogic.
SERVER test 12345678 7598 DAEMON telelogic /usr/appl/telelogic/flex/archflex FEATURE Telelogic telelogic 3.400 15-aug-98 2 1B5890E1960AFE22A57B "Telelogic" FEATURE SDT-Base telelogic 3.400 15-aug-98 1 0B58E0922F3034C3C29F "" FEATURE SDT-MSCE telelogic 2.200 15-aug-97 1 AB58C08192E26573643B "" FEATURE SDT-OME telelogic 1.100 15-aug-97 1 DBC8C061034073C86AD4 "" FEATURE SDT-Cbasic telelogic 2.200 15-aug-97 3 DBC322E12E1F4E6A7DC9 "" FEATURE SDT-Simulator telelogic 2.200 15-aug-97 1 5BA830E2597AAED4E6DF "" FEATURE SDT-Validator telelogic 2.200 15-aug-97 1 5BB3F0A11CDD96D4C1FF "" FEATURE SDT-TTCN-Link telelogic 1.200 15-aug-97 1 DBB87061BDA40AF3D222 "" FEATURE ITEX-Base telelogic 3.300 15-aug-97 1 FBF53071C228F9AF0CA7 ""
Here are detailed explanations for this license key example:
SERVER label, the hostname and hostID of the machine on which the license daemons will run, and a TCP/IP port number. Here we see that the machine test has hostID 12345678. The TCP/IP port number is 7598, which is the port number on which the license daemons will communicate.DAEMON label, the name of the vendor daemon (in this case telelogic), and a field to hold the path to the vendor daemon executable. In this case, the path is a "dummy" path generated by default when the license key is made. When you install your key, you must supply the correct path, which depends on your choice of installation directory and architecture. See FLEXlm Licensing Pitfalls to Avoid for additional information.FEATURE keyword. telelogic).FEATURE line, and by the hostID of the license server, specified on the SERVER line.
Here is a FLEXlm DEMO license key as it would appear when delivered by Telelogic.
SERVER hostname hostid 7598 DAEMON telelogic /usr/appl/telelogic/flex/archflex FEATURE Telelogic telelogic 3.400 15-aug-98 0 4BF862B1049767F837DE "Telelogic" DEMO FEATURE SDT-Base telelogic 3.400 15-aug-98 0 0B98B051C0144041B74C "" DEMO FEATURE SDT-MSCE telelogic 2.200 15-aug-97 0 EB98B0F1BF88E260FE2A "" DEMO FEATURE SDT-OME telelogic 1.100 15-aug-97 0 7B58E0C15A7D37B767B4 "" DEMO FEATURE SDT-Cbasic telelogic 2.200 15-aug-97 0 3BAB8081FEC65F761608 "" DEMO FEATURE SDT-Simulator telelogic 2.200 15-aug-97 0 8B28405166A00320F584 "" DEMO FEATURE SDT-Validator telelogic 2.200 15-aug-97 0 0B9810F1EB7103F3EA94 "" DEMO FEATURE SDT-TTCN-Link telelogic 1.200 15-aug-97 0 FB5820C123607B34A759 "" DEMO FEATURE ITEX-Base telelogic 3.300 15-aug-97 0 EBB8F0B71216A0C373E6 "" DEMO
Here are detailed explanations for this license key example:
SERVER label, two dummy placeholders for where a specific hostname and hostID would be placed in a "real" key, and a TCP/IP port number. Of course the port number is irrelevant, since with a DEMO key no license daemons need to be running, and thus do not need a port on which to communicate.DAEMON label, the name of the vendor daemon (in this case telelogic), and a field to hold the path to the vendor daemon executable. The path is again a "dummy" when you get your key from Telelogic Customer Support, but you will not need to put in the correct path for the telelogic daemon since the master lmgrd daemon never needs to start it -- neither daemon needs to run when you use a DEMO key.DEMO at the end of each. Also, the number of seats available is set to 0 (zero) on each FEATURE line. This is merely an implementation that "tricks" Telelogic Tau into allowing you to run the software even though the FLEXlm system is not operational. As before, the quoted field of the first FEATURE line will contain some text describing the license key (customer name, perhaps a contact person's name, etc.). All FEATURE lines after the first will have nothing between the quotes. Note, however, that the encryption codes are still valid for a DEMO key.When installing a new FLEXlm license key from Telelogic there are a few "pitfalls" to watch out for:
FEATURE and ends with a double-quote field (remember the first FEATURE line will have the customer name in this field). /appl/telelogic would be:/appl/telelogic/flex/sunos5flex/telelogicOn a Windows machine, if you use the FLEXlm software included with Telelogic Tau (i.e. you are not adding your FEATURE lines to a preexisting server) it is not necessary to specify the exact path (although you can, if you want to be thorough). Since both daemon executables are in the same directory within the Telelogic Tau installation (
\flex), the "lmgrd" master daemon can find the "telelogic" vendor daemon to start it up even when the path is unspecified:DAEMON telelogic telelogic.exeThis is how the DAEMON line looks when the license key comes from Telelogic Customer Support since your choice of installation directory is unknown to us. A full path example (with the default case of
\tau35 on the C: drive as the installation directory) is:DAEMON telelogic C:\tau35\flex\telelogic.exeIf for any reason you move the "telelogic" daemon from its normal place (
\tau35\flex) or if you make use of a preexisting FLEXlm server you must specify the complete path to it.license.log file if the conflict occurs. You can change the port number without invalidating your key. While this is purely a trial-and-error affair, as a "rule of thumb", numbers above 5000 (but below 20000) should not cause conflicts (most applications use numbers below port number 5000). Port number 7598 is often the "default" found in keys delivered by Telelogic. hostname and hostid found in the key delivered from Telelogic Customer Support. This is not the case. The encryption codes for each FEATURE line are actually generated based on a hostID value of "hostid", so inserting your actual hostID will invalidate the key.For direct-from-the-maker information on FLEXlm, including a FAQ (Frequently Asked Questions) document and the FLEXlm End User Manual, we suggest the following World Wide Web addresses at Globetrotter Software:
http://www.globetrotter.com/flxlmfaq/TOC.htm http://www.globetrotter.com/manual.htm
CopyControl is a node-locked licensing system from Microcosm, Ltd. That is, an application that uses CopyControl can run only on one specific machine at a time, and the license cannot move dynamically (i.e. across a network) from one machine to another. The license key is "stuck" on the hard drive it is installed on. It is possible, however, to move the license protection manually with some provided software tools.
CopyControl licensing consists of the application(s) to be licensed, some feature-by-feature DLL files which are used by the application(s) to recognize the license for each feature, some software tools for license management, and the actual license itself. The license is encrypted in such a way that it must be handled (installed, activated, moved between machines, etc.) by the provided software tools. All of these components are delivered to the customer on one or two floppy disk(s) with the Telelogic Tau delivery, although they can also be sent via email as a ZIP file. If the latter is the case, the ZIP file must be unpacked onto a floppy disk in order to use the license and software; if it is unpacked to a directory on your hard drive, it will not work. The tools for managing the license can be run from the floppy, but they are provided in the Telelogic Tau installation as well for convenience.
The license installation consists of moving the DLL files to the correct place, then transferring the actual license with one of the provided tools. During the license transfer, a five-digit unique serial number is generated and reported to the customer. Telelogic Customer Support takes this number and in return gives an activation code which the customer uses (via another of the software tools) to activate the license.
The CopyControl keys used in Telelogic Tau are known as CCROM keys. Once a key is installed on a hard drive, it can never actually be moved. However, it is possible to move the license protection from one drive to another. Complete details on how to do this are given in Moving a CopyControl License.
CopyControl licenses can be either evaluation licenses or post-purchase licenses. They are technically equivalent but differ in their durations, and also (most likely) by activated Telelogic Tau features, as an evaluating customer who decides to purchase may of course opt to buy more or less of Telelogic Tau than he or she evaluated!
It is possible to install Telelogic Tau either locally or on a network drive, and the CopyControl license software DLL files must be placed in a specified location within the Telelogic Tau installation directory structure. The actual CopyControl license must be installed on the local hard drive of each machine which is to run Telelogic Tau, in its own directory (chosen by the user).
In situations where there is a need to use both floating (FLEXlm) and node-locked (CopyControl) licenses, two installations of Telelogic Tau are required. This is because when Telelogic Tau starts up it checks for the presence of the CopyControl DLL files in the specified location within the Telelogic Tau installation directory structure. If those files are not present, then Telelogic Tau assumes that FLEXlm is to be used and tries to initiate communication with the FLEXlm license daemons.
One thing to note about CopyControl CCROM licenses: even though they are set for a "duration" (e.g. 30 days) on the floppy disk, when installed they are actually set to expire on an absolute date, determined by the duration (e.g. 30 days from today, whatever day that happens to be). This date will be preserved when a license is manually transferred to another machine or hard drive.
The license key floppy disk(s) (or emailed ZIP file) you will receive from Telelogic will contain several DLL files, some hidden license files, and three executables, called CCLOOK, CCMOVE, and CCCHANGE. These executables are what you will use to install (CCMOVE), activate (CCCHANGE) and check the status of (CCLOOK) your license. These utilities are also included within the Telelogic Tau delivery for convenience. CCCHANGE can also be used to manually move a license from one hard drive to another (note that you cannot copy a license; it must be installed initially with CCMOVE and transferred between hard drives with CCCHANGE).
Each DLL file handles one or more features of the Telelogic Tau tool set. All the DLL files will be present regardless of which actual features are included in your particular license key. The actual included features of your key are reported by the CCLOOK utility. For example, if you have a standard 30-day CopyControl evaluation license for the Telelogic Organizer, SDT Base, SDT Simulator, and SDT Validator, you will not be able to tell that you have access to these features from the DLL files. You will have DLL files for all the rest of the Telelogic Tau features, too. When you install and activate your license, you can use CCLOOK, which will report which license features are included and their expiration dates. In this example, you would have a license for the Cbasic feature as well, since this is required for the SDT Simulator and SDT Validator. Of course, the features included in the license key will be marked on the label of the floppy disk, or indicated in the email message accompanying the ZIP file.
An important piece of information (besides your product serial number given by CCMOVE) that you will need when getting an activation code from Telelogic Customer Support is the "product code" reported by CCLOOK. It identifies the combination of included features in your key. Examples are "TAU", "TAUD", and "TAU151".
When installing a new CopyControl license key from Telelogic there are a few "pitfalls" to watch out for:
CC_PATH_<product code>, where the "product code" is one item in a report by CCLOOK and mentioned above. It is often easy to forget this detail and to just call the environment variable CC_PATH_TAU.If you have questions about CopyControl licensing, contact Telelogic Customer Support (see How to Contact Customer Support).