| |||
| Home > Frequently Asked Questions about Licensing > Problems with server configuration > How can I limit user access to particular licensed features? | |||
As a floating license administrator, you can set aside specific features for named users or named client computers by using an options file. You can also prevent certain users or computers from being issued with a license of a particular type. This is particularly useful if you have a license that enables more than one version of the ARM tools and you want to control what users have access to what versions. You can do this using an options file.
To use an options file, first you must write it, then configure your license server to use it.
You can create an options file in any text editor. ARM recommends
that your options file has an .opt extension.
When complete, copy the options file to each of your ARM license
servers.
A sample options file is shown here, with some of the key syntax demonstrated. In this example, it is assumed that the license file contains both RealView Development Suite v4.0 and ADS v1.2 seats. There are two defined project groups with defined users, and a set of build computers. The administrator wants to limit the number of seats of a given feature on a group basis, and also wants to reserve RealView Development Suite v4.0 compiler seats for particular users and clients. A specific user is not to be granted a RealView Development Suite v4.0 compiler license.
The following permissions and restrictions are required:
The build computers in the host_group “buildbox” must always have 2 compiler seats available, of no particular version.
Users in group “project_talisker”, user1 to user5, must not be given more than three fromelf licenses of any version between them.
Users in group “project_macallan” must always have one seat of compiler version 4.0 available.
User7 cannot ever obtain a compiler license of version 4.0, despite being in group “project_macallan”.
The options file to enable the above would look like this:
# License Options File example by ARM Limited
# -------------------------------------------# This example should be modified as required for your own licensing # environment.# Turn off case sensitivity for group and hostnames# (Only valid in FLEXnet 10.x. In FLEXlm 9.x, you need to ensure that # case of groups and hostnames is consistent, and comment out the following
# line.)#GROUPCASEINSENSITIVE ON# Groups are defined here# --> use the form: GROUP group_name user_list#GROUP project_talisker user1 user 2 user 3 user4 user5GROUP project_macallan user6 user7 user8 # Host Groups are defined here# --> use the form: HOST_GROUP group_name host_list#HOST_GROUP buildbox buildpc01 buildpc02# Define usage restrictions below# --> use the form: OPTION feature[:keyword=value] type {name | group_name}#RESERVE 2 compiler HOST_GROUP buildboxMAX 3 fromelf GROUP project_taliskerRESERVE 1 compiler:version=4.0 GROUP project_macallanEXCLUDE compiler:version=4.0 USER user7
Some options, such as RESERVE, require that you specify the number of seats.
The RESERVE option puts aside a defined number of seats. You can specify an exact version of the feature if required.
The MAX option puts a limit on the number of seats of a given feature.
The EXCLUDE option prevents a user or group from being granted a license. This overrides any settings to include the user.
Other options are available and are described elsewhere, as is the exact syntax to use for all options. See Chapter 5 of theFLEXnet End User Guide.
You need to edit your ARM tools license file so that the options
file is called on the VENDOR or DAEMON line. For example, if your
options file is called armlmd.opt, in your
license file you need to add VENDOR armlmd option=armlmd.opt.
This must be done on each of your ARM license servers.
Restart your license server or servers. If your configuration is successful, the server log shows messages that the options file is being used and that your restrictions defined in the options file are being implemented.
| Copyright © 2002-2004, 2006-2008 ARM Limited. All rights reserved. | ARM DUI 0209H |
| Non-Confidential | |
 PDF version | |
| Home > Frequently Asked Questions about Licensing > Problems with server configuration > How can I limit user access to particular licensed features? |