License Server Administration for CCS
From Texas Instruments Embedded Processors Wiki
Contents |
Administrating Code Composer Studio Licenses
Code Composer Studio makes use of FLEXnet Publisher (industry-standard licensing technology from Acresso) for product licensing.
If you are using Code Composer Studio in the standard single-user mode – no additional administration steps are necessary. This guide is intended for those who wish to setup and administer floating licenses for Code Composer Studio.
Floating Licenses
In the node locked single-user scenario, the license file (.lic) is stored on the machine running Code Composer Studio (one .lic file per machine). In the floating license scenario, a server is setup as a license host and each of the client machines are configured to “check-out” a license as needed.
This guide outlines administration details specific to Code Composer Studio and is intended to supplement the existing License Administration Guide from Acresso (Chapters 8 through 14 cover the generic details of setting up and maintaining a floating license system).
Requirements
- License Administration Guide
- License Server Machine. Currently we support Windows, Solaris (Sparc) and Red Hat Linux (See License Administration Guide Chapter 8 "Selecting a License Server Machine") lmadmin, lmgrd and lmtools executables (downloaded from Acresso) for either Solaris (Sparc), Red Hat Linux or Microsoft Windows
- Texas Instruments’ vendor daemon (tidspssw)
- Please Note: Code Composer Studio and the tidspssw vendor daemon were built with FLEXnet publisher v11.4.1
- The tidspssw vendor daemon is available for (click on the link to download):
- Floating License File for Code Composer Studio
Step 1: Get a License File
- Register online with your activation code to get your license file.
- Floating license files (.lic) serve-up multiple licenses to clients, but the license file itself is locked to a physical server. When you register online to receive your license file - please use the HostID of your license server.
- You can get the HostID of your server by running 'lmhostid' (downloaded as part of the lmtools package from Acresso. See page 89-91 of the License Administration Guide).
Step 2: Setup License Server
- You will need the tidspssw vendor daemon, the license file (from Step 1) and either lmadmin or lmgrd.
- Follow the steps in the License Administration Guide to setup lmadmin (Chapter 8) or lmgrd (Chapter 11) as the server process.
- IMPORTANT: Make sure that the .manifest file is extracted from the zip along with the executable program.
Step 3: Configure Code Composer Studio
Once your license server is running you need to configure Code Composer Studio to connect to the server in order to acquire a license. This is done in one of three ways:
Option 1: licenselocation.txt (recommended)
- The recommended method for defining the license server for Code Composer Studio to use is to create a licenselocation.txt file.
- If the file ccsv4\DebugServer\license\licenselocation.txt exists, location entries in this file are searched for licenses.
- This text file contains a single location entry per line. Location entries are one of the following:
- port@host where port is the port number and host is the host name of a license server system.
- @host where host is the host name of a license server system. Since no port number is specified, a default port number between 27000 and 27009 is used. @localhost always works if the server is running on the same system as the application
- A comma separated list of three port@host entries denoting a three-server redundant configuration. For example, port1@host1,port2@host2,port3@host3 specifies the three-server redundant configuration composed of host1, host2 and host3.
- The actual text of the license file, with START_LICENSE\n as a prefix, and \nEND_LICENSE as suffix, where the embedded newlines (\n) are required.
- If licenselocation.txt contains multiple entries, they are searched in order from the first line, to the last line.
Option 2: Environment Variables
- It is possible to specify the license locations in an environment variable. Locations are specified similar to the entries of licenselocation.txt, with the one exception that relative path entries are not auto-expanded, so you must use absolute paths.
- If these environment variables exist, the locations they specify are searched before those in licenselocation.txt and the DebugServer\license folder.
- On Windows, multiple entries are separated by a semicolon (;).
- TIDSPSSW_LICENSE_FILE Override the application defined license location for Code Composer Studio.
- LM_LICENSE_FILE Override the application defined license location for all FLEXnet-enabled applications. If you use multiple FLEXnet-enabled applications, with a single license server serving all of them, this variable is useful as a quick way to tell all the applications where to search for licenses.
Option 3: Windows Registry
- The Environment Variable specified above can exist as "proper" environment variables or as special entries:
- Windows Registry:
- HKEY_LOCAL_MACHINE\Software\FLEXlm License Manager
- Windows Registry:
Automatically Configuring During Installation
As mentioned above, Code Composer Studio will read the contents of ccsv4\DebugServer\license\licenselocation.txt to determine where to search for a license (file or server). If your organization installs many copies of Code Composer Studio, it can be difficult to ensure that all of the client installations are correctly configured to check-out licenses from your server.
As a matter of convenience you can create a licenselocation.txt file that has the parameters for your server (i.e. 9900@myserver.mycompany.com) and then create a .\license folder in your Code Composer Studio install image:
\install_images\ccscore\license\licenselocation.txt
This file will automatically get installed into ccsv4\DebugServer\license folder during product installation. Users within your organization will never need to setup licensing and will never be shown the "Registration" dialog.
Leave a Comment
