|ARM Technical Support Knowledge Articles|
Installing and configuring a floating license involves four steps:
If you have an existing ARM license server, you should ensure that you are using the same version of the server utilities provided with the latest ARM development tools you have. You must also stop and restart the license server(s) before you can use a new license. Full information on how to carry out these steps is provided at the end of this FAQ; however the two sections immediately below are a quick guide to the required procedures on Windows and Unix/Linux platforms.
The document "Floating License Installation for RealView Developer Suite 2.0" explains how these steps can be done for a Windows license server. It is equally applicable to later releases of RealView Developer suite. Users of RVDS 2.2 and later can use the ARM License Wizard v4.x to complete step 4, configure client licensing.
Unix and Linux users should refer to the following sections of the ARM FLEXnet License Management Guide:
Detailed Floating License Installation Instructions:
Installing the server software
The FLEXlm license server utilities for all supported server platforms are provided on your ARM development tools CD, in the Utilities/FLEXlm directory of RealView Developer Suite, or flexlm/ directory of ADS.
Copy the files from the CD-ROM into a destination directory (for example, C:\FLEXlm) on your license server. This directory should be on your PATH. On Solaris, Linux or HP-UX, run the makelinks.sh script in the licence utilities directory on the server.
You should use the license server utilities provided with the latest ARM development tools that you have, as changes to license file formats may mean that an older license server will not support a new tools license. See the FAQ: Which version of the license server daemons should I run? . Further information on installing license server software is in section 4.1 of the ARM FLEXnet License Management Guide.
Installing the license
Copy the license you have obtained from the web licensing system to each of the servers you are using. We recommend that you put the license file in the same directory as your license utilities. You may need to make some changes to the license file's
this_host' with the corresponding server name.
8224for ARM licenses.
Your modified server line should then be of the following format:
SERVER <servername> <host ID> <port>
Starting the license server(s)
To start the license server on Windows, run the lmtools.exe program in your license utilities directory. On the Configure Services tab, add paths for the lmgrd daemon, license file, and log file. Save the service. On the Start/Stop/Reread tab, click Start Server.
You can also start the license server from the command line on all platforms. Change to your license utilities directory, then type:
lmgrd -c <license_file> -l <logfile_name>
More information on starting the license server is in section 4.3 of the ARM FLEXnet License Management Guide.
Configuring the client
The final step is to get the client computers to obtain their license from the license server(s). One way to do this is to create an environment variable called
ARMLMD_LICENSE_FILE on the client. The value of this environment variable should be of the form "
port@host", where port is the port number of the license server, and host is the hostname of the server. If you have a three server license you must include three
port@host values. All three servers must have been configured and started before you can use the license.
Here is one method of setting the ARM licensing environment variable for a three server system for a Windows client. Open the Control Panel, double click on the System icon, then click on the Advanced tab (or Environment tab on WinNT). Add a system environment variable called
ARMLMD_LICENSE_FILE and set it to a value of the form:
You would of course use the real port and server names for your own license servers. Note that the third server in this example has no port number defined as this server is using a default port in the range between
If you are using a Solaris, Linux or HP-UX client, you would set the environment variable using the relevant command for your shell (for instance, "
setenv" if using csh or tcsh), and separate the servers with
: (colon) rather than
If you are using Windows and recent ARM developer tools (RVDS 2.2 and later), you could instead use the ARM License Wizard v4.x to configure your license environment on the client.
See chapter 5 of the ARM FLEXnet License Management Guide for more details on how to configure a client to use a license server.
N.B. It is strictly forbidden to attempt to install seats which have since been replaced by upgrade/update seats.
For more details, please see the FAQ: Do upgrade/update seats replace existing seats?
Article last edited on: 2013-01-29 09:59:52
Did you find this article helpful? Yes No
How can we improve this article?