FLEXlm
|
Copyright
Copyright 2003 Macrovision Corporation. All rights reserved.
Macrovision products contain certain confidential information of Macrovision Corporation. Use of this copyright notice is precautionary and does not imply publication or disclosure. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language in any form by any means without the written permission of Macrovision Corporation.
Trademarks
Globetrotter, Macrovision, FLEXbill, Flexible License Manager, FLEXlm, FLEXlock, and GTlicensing are registered trademarks or trademarks of Macrovision Corporation. All other brand and product names mentioned herein are the trademarks and registered trademarks of their respective owners.
Restricted Rights Legend
Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights of Technical Data and Computer Software clause of DFARS 252.227-0713 and FAR52.227-19 and/or applicable Federal Acquisition Regulation protecting the commercial ownership rights of independently developed commercial software.
Printed in the USA.
March 2003
Table of
Contents
Preface
Chapter 1 Introduction and Overview
1.3.4 FLEXlm Components Shipped by Your Vendor
1.4 The License Request Process
1.6.1 Installing Licensed Software
Chapter 2 License File Basics
2.1 Specifying Location of the License File
2.1.1 Setting the Path with an Environment Variable
2.2 License File Format Overview
2.3.1 Floating (Concurrent) Licenses
2.3.3 Mixed Node-Locked and Floating Licenses
Chapter 3 Managing Licenses from Multiple Vendors
3.1 Overview of Multiple License Management Strategies
3.3 One Machine with Multiple License Servers
3.4 One Machine with One License Server and Multiple License Files
3.5 Managing Multiple License Files
3.6.2 Version Component Compatibility
Chapter 4 Selecting Server Machines
4.1 Resources Used by the Server
4.3.1 Redundancy via License-File List
4.3.3 Comparing Three-Server to License-File List
4.4 Counted vs. Uncounted Licenses
Chapter 5 The Options File
5.3 How the Vendor Daemon Uses the Options File
5.4 Rules of Precedence in Options Files
5.5.1 Simple Options File Example
5.5.2 Limiting Access for Multiple Users
Chapter 6 The License Manager Daemon
6.2 Starting the License Manager Daemon on UNIX Platforms
6.3 Starting the License Manager Daemon on Windows
6.3.1 Manually from the Command Line
6.3.2 Configuring the License Manager as a Windows Service
6.3.4 Automatically at System Start Up
Chapter 7 License Administration Tools
7.1 Running Administration Tools
7.2 Universal lmutil Arguments
7.16 License Administration Tools—LMTOOLS for Windows
7.16.1 Configuration Using License File
7.16.2 Configuration Using Services
Chapter 8 Mobile Licensing
8.1 Node-Locked to a Laptop Computer
8.2 Node-locked to a FLEXid (Windows Only)
8.3 Node-Locked to a FLEXid with FLOAT_OK (Windows Only)
8.3.1 Initiating FLEXid with FLOAT_OK
8.3.2 Returning a FLEXid with FLOAT_OK License
8.3.3 FLEXid with FLOAT_OK Example
8.4 License Borrowing with BORROW
8.4.1 Initiating License Borrowing
8.4.3 Support for License Borrowing
8.5 Node-locked to a User Name
8.6 Fulfilled from a Prepaid License Pool
Appendix A Hostids for FLEXlm-Supported Machines
Appendix B License File Format
Appendix C Troubleshooting Guide
C.2.3 Level 3 Content (FLEXlm v6.0+ only)
C.3 FLEXlm Troubleshooting List
C.3.1 Problem Description Format
C.3.4 Other FLEXlm-Licensed Application Problems
Appendix D FLEXlm Environment Variables
D.1 How to Set Environment Variables
Appendix E Frequently Asked Questions
E.1.1 I’ve received FLEXlm license files from two different companies. Do I have to combine them?
E.1.2 When is it recommended to combine license files?
E.3.1 Does FLEXlm work across the Internet?
E.3.2 Does FLEXlm work with Internet firewalls?
E.3.3 If my FLEXlm-licensed application dies, does the server free the license?
E.3.4 What happens when the license server dies?
E.3.5 How do you tell if a TCP/IP port is already in use?
E.3.6 Does FLEXlm require root permissions?
E.3.7 Is it OK to run lmgrd as “root” (UNIX only)?
E.3.8 Does FLEXlm licensing impose a heavy load on the network?
E.3.9 Does FLEXlm work with NFS?
E.3.10 Does FLEXlm work with ATM, ISDN, Token-Ring, etc.
E.3.11 Does FLEXlm work with subnets, fully qualified names, multiple domains, etc.?
E.3.12 Does FLEXlm work with NIS and DNS?
E.3.13 We are using FLEXlm over a wide-area network. What can we do to improve performance?
E.4.1 What Windows Platforms are supported?
E.4.2 Will the Server run on Windows 95?
Appendix F FLEXlm Error Codes
F.1.2 Format 2 (long—version 6.0+):
Appendix G The Report Log File
G.1 Managing Report Log Output
G.2 Enabling Report Log Output for a Vendor Daemon
G.3 Redirecting Report Log Output for a Vendor Daemon
Appendix H The Debug Log File
H.1.1 Capturing Debug Log Output for a License Server
H.1.2 Capturing Debug Log Output for a Particular Vendor Daemon
H.1.3 Redirecting Debug Log Output for a Running Vendor Daemon
H.1.4 Limiting Debug Log Output for a Vendor Daemon
H.2.2 Configuration Problem Messages
H.2.3 Daemon Software Error Messages
Appendix I FLEXlm Versions
I.1 Version Compatibility and Components
I.2 How to Tell the License File Version
Index
FLEXlm End Users Guide March 2003