ARM ® FLEXnet LicenseManagement Guide v4.1


Table of Contents

Preface
About this book
Intended audience
Using this book
Typographical conventions
Further reading
Feedback
Feedback on license management
Feedback on this book
1. Introduction
1.1. Supported platforms
1.1.1. Client platforms
1.1.2. License server platforms
1.2. Tool licensing options
1.2.1. Node-locked license (Windows only)
1.2.2. Floating license (Windows and Unix/Linux)
1.3. ARM License Wizard
1.4. ARM web licensing portal
2. Requesting Your License
2.1. Information needed for a license
2.1.1. Product serial number
2.1.2. Host ID
2.2. ARM web licensing portal
2.2.1. Access from the License Wizard v4.x
3. Installing a Node-Locked License
3.1. Installing a node-locked license
3.1.1. Using the ARM License Wizard
4. Setting Up a Floating License Server
4.1. Installing the server software
4.1.1. Installing server software on Windows
4.1.2. Installing server software on Unix/Linux
4.2. Installing the server license
4.3. Starting the license server
4.3.1. Starting a Windows server
4.3.2. Starting a Unix/Linux server
5. Configuring a Client to Use a License Server
5.1. Configuring the client licensing onWindows
5.1.1. ARM License Wizard
5.1.2. Using the Control Panel
5.1.3. Using the Command Line
5.2. Client license on Unix/Linux
5.2.1. Shell commands
5.2.2. .flexlmrc
6. Frequently Asked Questions about Licensing
6.1. General licensing questions
6.1.1. How do the ARM development tools implementFLEXnet ?
6.1.2. How does FLEXnet finda license file?
6.1.3. Can I use FLEXnet withmore than one product?
6.1.4. How do I combine licenses?
6.1.5. How do I move my license to anothercomputer?
6.1.6. Do the ARM development tools supportBORROW?
6.1.7. Do ARM licenses support queuing?
6.1.8. Why can I not find the LMHOSTID utility?
6.2. Problems with client configuration
6.2.1. License apparently missing
6.2.2. My node-locked tools fail with an“Invalid license key (inconsistent authentication code” error
6.2.3. How do I manually install a node-lockedlicense?
6.2.4. How can I change the order in whichmy license sources are accessed?
6.2.5. What does the “Diagnose license managementproblems” option do in the License Wizard?
6.2.6. How can I optimize floating licensecheckout times?
6.2.7. Can I use a remote license server?
6.2.8. Problems communicating with the server
6.3. Problems with server configuration
6.3.1. Server log reports "Invalid licensekey (inconsistent authentication code)"
6.3.2. How do I update the license file myserver uses?
6.3.3. Can I define the order in which licensesin a mixed version license file are issued?
6.3.4. How can I tell how many floating licensesare in use?
6.3.5. Server log reports “(armlmd) cannotopen lock file”
6.3.6. What version of the license serverdaemons should I use?
6.3.7. How can I limit users’ access to particularlicensed features?
6.3.8. Why am I getting “DENIED” messagesin the server log?
Glossary

List of Tables

2.1. Commands for obtaining host IDs

ProprietaryNotice

Words and logos marked with ® or ™ are registered trademarks or trademarksowned by ARM Limited. Other brands and names mentioned herein maybe the trademarks of their respective owners.

Neither the whole nor any part of the information containedin, or the product described in, this document may be adapted orreproduced in any material form except with the prior written permissionof the copyright holder.

The product described in this document is subject to continuousdevelopments and improvements. All particulars of the product andits use contained in this document are given by ARM in good faith.However, all warranties implied or expressed, including but notlimited to implied warranties of merchantability, or fitness forpurpose, are excluded.

This document is intended only to assist the reader in theuse of the product. ARM Limited shall not be liable for any lossor damage arising from the use of any information in this document,or any error or omission in such information, or any incorrect useof the product.

Where the term ARM is used it means “ARM or any of its subsidiariesas appropriate”.

ConfidentialityStatus

This document is Non-Confidential. The right to use, copyand disclose this document may be subject to license restrictionsin accordance with the terms of the agreement entered into by ARMand the party that ARM delivered this document to.

Product Status

The information in this document is final, that is for a developedproduct.

Revision History
Revision A July2002 First Release
Revision B January2003 Second Release
Revision C May 2003 ThirdRelease
Revision D January 2004 Release3.1 for RVDS v2.1
Revision E December2004 Release 3.2 for RVDS v2.2
Revision F March2006 Release 4.0 for RVDS v3.0
Revision G March 2007 Release4.1 for RVDS v3.1
Copyright © 2002-2007 ARM Limited. All rights reserved. ARM DUI 0209G
Non-Confidential