ARM® FLEXlm License Management Guide v4.0 1.2.2. Floating license (Windows and Unix/Linux)

1.2.2. Floating license (Windows and Unix/Linux)

A floating license scheme is more flexible than a node locked license but requires more administration. It would typically be used where there are more potential tool users than purchased licenses.

A floating license-managed installation of the tools consists of the following computers:

Client: This is the computer upon which the ARM development tools are installed and run by a user.
Server: This is the computer upon which the license is installed. A license server may also be a client, though this is not normal operation.

The license server is used to control the number of copies of the tools in use at any one time up to the maximum number of licenses purchased. The license extract shown in Example 1.2 shows part of a typical floating license. In this example the fully qualified SERVER name is license1.somedomain.com, the host ID is 785f2170 and port 8224 is being used. A three server license would have three SERVER lines at the start of the license. This license allows up to 10 concurrent users of the specified ARM application, and each user obtains permission to run the application from the license server. Due to the flexible way the individual parts of the tools are license managed, this floating license allows up to 10 users to be using the armulate feature, while a different 10 users can use the fromelf feature. The SIGN key indicates that the license has the Counterfeit Resistance Option feature enabled.

Example 1.2. Typical single-server floating license extract

SERVER license1.somedomain.com 785f2170 8224
VENDOR armlmd
USE_SERVER
INCREMENT fromelf armlmd 2.0 permanent 10 7E338B2771EA DUP_GROUP=UHD \
	ISSUER="ARM Limited" NOTICE="For support please contact \
	your supplier." SN=ABCDE-98765-ZYXWV SIGN="8674 FEE3 \
	5830 D004 2F8D 8C07 E75C 84AA 14EB 37A0 9AD7 4D73 D34A F83A \
	EE22 B1F1 3579 54C8 54BA D9D7 5B87 E024 632C B7E0 1DF2 8526 2312 \
	27F2 DD78 C020 ABB9" SIGN2="1E17 F524 7987 9CD4 3BC2 FB34 E2FB \
	04AA 2C79 4B4C 776D 0FC3 9797 7653 2FBA 044B 2854 608B D8B9 \
	6F8A 7B69 3BFA 4AE4 2234 B9A0 0ACA 3E21 1CF8 0F58 54FE"
INCREMENT armulate armlmd 1.4 permanent 10 C10A180A3F79 DUP_GROUP=UHD \
	ISSUER="ARM Limited" NOTICE="For support please contact \
	your supplier." SN=ABCDE-98765-ZYXWV SIGN="D88E 04A5 \
	B8D3 7661 4CC2 2BA0 2933 BD9D F6AA 9C66 284D C7C2 1B65 9D47 \
	451C 0F43 A894 07C4 389C 51BB 0B1C C1E4 5ECC 42AC BCA8 16B3 \
	8EBE F131 6FEB 2D5D" SIGN2="0B05 AA41 0675 A505 B800 B09C BF22 \
	B094 155D 8ECA 8F96 F001 3994 A4F7 2820 0D8B 7ABC 6E68 6BDA \
	F321 A204 A2E6 2217 4753 D5CA 9663 64E7 F8FA 35EE 924A"
INCREMENT rvd_ide armlmd 1.7 permanent 10 8EE2C29A2DB3 DUP_GROUP=UHD \
	ISSUER="ARM Limited" NOTICE="For support please contact \
	your supplier." SN=ABCDE-98765-ZYXWV SIGN="2B77 780F \
	37C5 CAD3 ED05 AECA 0424 0876 6E3D 2EAC 64EB C78E 7015 6E99 \
	2119 08ED 4889 AF20 CD05 9E76 EA75 72FE 0154 CC8F CD78 AA01 \
	1824 C650 A7B5 0696" SIGN2="20EA 4015 0356 5FF8 2DE5 083A 2C9F \
	5645 B14E 220C 00E1 8970 F32E B873 AC7E 182A 20EF 27EA 7BB8 \
	B25E 08DB 70D3 AB8B 7847 DB87 B88A 5700 A079 BEB7 E3D2"
INCREMENT rvd_arm armlmd 1.7 permanent 10 D3C61DCC1FFE DUP_GROUP=UHD \
	ISSUER="ARM Limited" NOTICE="For support please contact \
	your supplier." SN=ABCDE-98765-ZYXWV SIGN="878E E524 \
	BCC7 9C50 1512 D42D 0707 DA8E B727 78EE A48B 913E DC88 A4B7 \
	BEF5 7DD7 FB2D 078C 7C9C AF10 945C 386E 661A 048E 1474 FEE7 \
	08B3 BAE4 E8E2 24EA" SIGN2="237E C75E 17A6 9687 8C94 DA87 27BE \
	5912 FA64 2406 E6D6 2EC4 F19B BFEB A7ED 1CC2 A0FE 0435 8701 \
	2EC9 1137 9D13 8F8D 5237 1BC7 C785 1374 A804 E9EF A91D"

Note

The use of Windows 95, 98 or Me on license server machines is neither recommended nor supported by ARM Limited.

Windows and Unix/Linux license servers and clients can be mixed in any installation. Client machines must be able to access the server machines over the local network.

ARM supports two different server models for floating license installations.

Single server model

The license file is locked to the host ID of a single server which is used to control the licensing process. A single server floating license model requires that the server machine is running at all times and that the client machines can access this server machine over the network.

Limitations

Should the server fail, the tools cannot be used until the server is repaired.

Figure 1.1 illustrates the single server model. On the server, a license file with the corresponding server details is loaded by the license server processes. The client must be configured so that it references the license server and the port through which the license is issued. The recommended method for doing this is to set the ARMLMD_LICENSE_FILE environment variable on the client to “port@server”. For the example in Figure 1.1, the environment variable should be set to “8224@Server_A”. More information on client configuration can be found in Chapter 5 Configuring a Client to Use a License Server.

Figure 1.1. Single server model

Three server model

The license file is locked to the host ID of three separate license servers. This permits more reliable licensing of the tools as failure of one server will not stop users from checking out licenses. A three server floating license model requires that:

a minimum of two server machines are running at all times
the servers can access each other over the network
the client machines can also access these server machines over the network.

Limitations

More complicated to setup than a single server system
Three servers are required, of which two must be operational at all times.

Figure 1.2 illustrates the three server model. On each of the servers, an identical license file with details of all three servers is loaded by the license server processes. The client must be configured so that it references all the license servers as well as the ports through which the license is issued. The recommended method for doing this is to set the ARMLMD_LICENSE_FILE environment variable. More information on client configuration can be found in Chapter 5 Configuring a Client to Use a License Server.

Figure 1.2. Three server model

For the example in Figure 1.2, on Windows, the environment variable should be set to “8224@Server_A;8224@Server_B;8224@Server_C”. The first server in the list, Server_A, is the master server, and must be started before the other two servers.

Depending on your operating system, the separators for the values in the environment variable may be different. On Unix/Linux, the separator is a colon “:” rather than a semicolon “;” as on Windows.

Copyright © 2002-2006 ARM Limited. All rights reserved.	ARM DUI 0209F
Non-Confidential
PDF version