Home

End Users Guide

1. This configuration requires an 1mgrd and a vendor daemon because the concurrent usage of the two licenses on the third FEATURE line is counted License File Basics Managing Licenses from Multiple Vendors Since more than 2500 vendors have chosen FLEX m as their license manager chances are good that you have to administer FLEX m licenses from more than one vendor 3 1 Overview of Multiple License Management Strategies When you are running FLEX m licensed products from multiple vendors you may need to take steps to prevent licensing conflicts during installation There are several strategies to accomplish this of which three are presented here e Multiple machines each running one 1mgrd one vendor daemon and using one license file e One license server machine running multiple 1mgrds each of which running one vendor daemon and using one license file e One license server machine running one 1mgrd multiple vendor daemons each of which using its own license file License files share a common directory These strategies are ordered from most to least independence among vendors In the first option mentioned above you have the most license server machines to monitor in the third option you have only one server and one license file to administer Each of these three strategies is described in detail in the following sections Variations are mentioned in Section 3 6 Additional Considerations FLEXIm End Users Guide
2. 31 3 4 One Machine with One License Server and Multiple License Files 32 3 5 Managing Multiple License Files 0 00000 33 FLEXIm End Users Guide July 2003 iii Chapter 4 Chapter 5 3 6 Additional Considerations 00 00 ce eee eee 34 3 6 1 Combining license files 0 0 0 0 0 0 eee 34 3 6 2 Version Component Compatibility 38 Selecting Server Machines 0 0 0 ce eee eee ee eee 39 4 1 Resources Used by the Server 0 0 000008 39 4 DT Sockets 22s ub esee ly ace ave E uc rel Duck wt oe 39 41 2 CPU Time esses ettet etant edet ient 39 4 1 3 Disk Space iecore Ree EI Sa m cte etn 40 44 4 Memory 42 ociupReUepER eSiactie A UNRSE 40 4 1 5 Network Bandwidth 0 eee eee eee 40 4 2 Remote Mounted Disks 0 0 e eee eee 41 4 3 Redundant License Servers 2 0 0 0 0 cece eee eee 41 4 3 1 Redundancy via License File List 42 4 3 2 Three Server Redundancy 00200005 42 4 3 3 Comparing Three Server to License File List 43 4 4 Counted vs Uncounted Licenses 005 43 Th Options Bile orsi sasatna a en Prax enemies 45 5 1 Creating an Options File 0 0 00 ee eee ee eee ee eee 45 5 2 Options Eille Syntax ceo ssacutercqremtes rie ere bad ptu 46 5 2 1 BORROW LOWWATER eeeeee eee eee 50 5 2 2 DEBUGEOG eL ap OAS EP NEED U
3. End Users Guide VERSION 9 2 JULY 2003 ma rovision COPYRIGHT NOTICE 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 FLEX m FLEXIock FLEXbill Flexible License Manager 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 re spective owners RESTRICTED RIGHTS LEGEND Use duplication or disclosure by the government is subject to restrictions as set forth in subparagraph c 1 i1 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 July 2003 Contents Pr tace ds ete hid ladies Blithe a T be solid E bled oe oet ix Chapter 1 Introduction and Overview 0 0 cece cece eee 11 1 1 Introduction to FLEXIm 1 0 eee 11
4. Denies access to the feature paint to anyone except picasso mondrian or anyone from the host bigbrush by implication 66 The Options File The License Manager Daemon The license manager daemon 1mgrd is one of two components which comprise the license server the other being the vendor daemon It handles the initial contact with FLEX m licensed applications passing the connection on to the appropriate vendor daemon The purpose of the license manager daemon 1mgrd is to Start and maintain all the vendor daemons listed in the VENDOR lines of the license file Refer application checkout or other requests to the correct vendor daemon A newer 1mgrd can be used with an older vendor daemon or FLEX m licensed application but a newer vendor daemon or FLEX m licensed application might not work properly with an older 1mgrd Always use the newest version of 1mgrd as possible it is available for download from www macrovision com 6 1 Imgrd Command Line Syntax l1mgrdis the main daemon for FLEX m When you invoke 1mgrd it looks for a license file which contains information about vendors and features and starts those vendor daemons Usage is lmgrd c license file list 1 debug log path 2 p local x lmdown x lmremove z v help where c license file list Use the specified license file s FLEXIm End Users Guide July 2003 67 Imgrd Command Line Syntax 6
5. July 2003 29 Multiple Machines 3 2 30 Multiple Machines In this scenario each distinct vendor daemon and its associated license file or files is located on a separate server machine Each machine serves licenses just for its vendor daemon and runs its own local copy of 1mgrd Figure 3 1 shows this arrangement Imgr o Imgr o Imgr o grd 9 grd 9 grd 9 0 fod fod 09 dp op Vendor o Vendor g Vendor g ABC S DEF T XYZ T Daemon S Daemon S Daemon S Vendor ABC s 3 Vendor DEF s f q Vendor XYZ s f a License File s License File s License File s Server Machine1 Server Machine2 Server Machine n Figure 3 1 Multiple Server Machines ADVANTAGES The license files for each vendor are independent from one another Machines are maintained separately If one machine goes down the other machines continue to serve licenses for their vendors Each server has its own debug log Licensing load is distributed DISADVANTAGES Administrative overhead is the highest e If one machine goes down licensing for the vendor s product associated with that machine is down STARTING THE LICENSE SERVER Invoke the license manager daemon on each machine lmgrd c server machine n license list Where server machine n license listis a license fil
6. OUT feature user num lic licenses user has checked out num 1ic licenses of feature RESERVE feature for USER user RESERVE feature for HOST host A license of feature is reserved for either user or host REStarted vendor internet port nnn Vendor daemon vendor was restarted at TCP IP port nnn Retrying socket bind address in use The license servers try to bind their sockets for approximately six minutes if they detect address in use errors Selected EXISTING master host This license daemon has selected an existing master host as the master 150 The Debug Log File Debug Log Messages Message SERVER shutdown requested Description A daemon was requested to shut down via a user generated kill command Server started on host for feature_list A possibly new server was started for the features listed Shutting down vendor The license manager daemon is shutting down the vendor daemon vendor SIGCHLD received Killing child servers A vendor daemon logs this message when a shutdown was requested by the license daemon Started vendor The license manager daemon logs this message whenever it starts a new vendor daemon Trying to connect to host The daemon is attempting a connection to host G2 2 Configuration Problem Messages Message host Not a valid server host exiting Description Th
7. 1 Copies the license file containing the FLOAT_OK node locked FEATURE line from the license file on the license server machine to a license file on the client computer in the location where the licensed application expects to find its license file 2 Moves the FLEXid matching the node locked FEATURE line from the license server machine to the client computer When the FLEXid is removed from the license server machine this license is unavailable on the network 3 Installs the FLEXid drivers on the client computer if they are not already installed 4 Disconnects the client computer from the network Now the license is available on the computer with the FLEXid even though that computer is disconnected from the network Returning a FLEXid with FLOAT_OK License To return the license to the license server machine so it floats on the network again the end user 1 Removes the FLEXid from the client machine and replaces it on the license server machine 2 Rereads the license file for the license server that serves the floating version of the license by running 1mreread When the FLEXid is returned to the license server machine the FLOAT OK license does not float on the network again until lmreread is run FLEXid with FLOAT OK Example The following is a sample license file issued to a customer site It is shipped with two FLEXids FLEXID 7 b28520b9 and FLEXID 7 b2857678 SERVER myhost ANY VENDOR sampled FEATURE f1 sampled
8. O options file BORROW_LOWWATER 50 creating 45 DEBUGLOG 51 DISPLAY type 50 examples 63 EXCLUDE 52 EXCLUDE_BORROW 52 EXCLUDEALL 53 GROUP type 53 GROUPCASEINSENSITIVE 54 HOST type 49 HOST_GROUP type 54 INCLUDE 55 INCLUDE_BORROW 56 INCLUDEALL 56 INTERNET type 50 LINGER 57 164 FLEXIm End Users Guide July 2003 MAX 58 MAX_BORROW_HOURS 59 MAX_OVERDRAFT 59 NOLOG 59 overview 21 PROJECT type 50 read by vendor daemon 62 REPORTLOG 60 required for HOST_BASED 121 required for USER_BASED 122 RESERVE 61 rules of precedence 63 TIMEOUT 61 TIMEOUTALL 62 type argument 49 USER type 49 options file path 116 OPTIONS SUITE 125 OPTIONS SUITE_RESERVED 125 order of lines in license file 28 128 OVERDRAFT 121 P PACKAGE line 124 OPTIONS SUITE 125 OPTIONS SUITE_RESERVED 125 syntax 124 package suite 125 PLATFORMS 121 port number server default range 115 SERVER line 115 VENDOR line 116 preface ix PROJECT type 50 R redundant servers selecting server nodes 41 separate license files 69 SERVER lines 114 three server redundancy 42 via license file list 42 rehosting license 99 remote disks guidelines for using 41 report log file 40 reporting on project 60 REPORTLOG 60 RESERVE 61 restricting access Imdown 68 Imremove 68 Imreread 68 S SAMreport 60 SAMsuite Users Guide x SAMwrap Users Guide x SERVER line 114 combining license files 37 default port numbers 115 host 114 hostid 114 port number 11
9. The Options File Rules of Precedence in Options Files FLEXLM VERSION NOTES 5 4 5 5 The lmreread utility enhanced in v8 0 vendor daemon so that it causes the vendor daemon to reread the options file If you are using earlier versions of FLEX m the vendor daemon must be stopped and restarted in order for the options file to be reread Rules of Precedence in Options Files Rules of precedence take effect when INCLUDE and EXCLUDE statements are combined in the same options file and control access to the same features The following define the precedence when both types of statements appear together e If there is only an EXCLUDE list everyone who is not on the list is allowed to use the feature e fthere is only an INCLUDE list only those users on the list is allowed to use the feature If neither list exists everyone is allowed to use the feature The EXCLUDE list is checked before the INCLUDE list someone who is on both lists is not allowed to use the feature Once you create an INCLUDE or EXCLUDE list everyone else is implicitly outside the group This feature allows you as an administrator the ability to control licenses without having to explicitly list each user that you wish to allow or deny access to In other words there are two approaches you either Give most users access and list only the exceptions or e Severely limit access and list only the those users that have access privileges Options File Ex
10. app2 Checkout succeeded f1 BC64A7B120A License file localhost License Server localhost app3 Fl FLEXIm End Users Guide July 2003 131 FLEXLM_DIAGNOSTICS Checkout succeeded f1 BC64A7B120AE License file servtest lic License Server speedy Note that the feature name and license key are printed along with the license file location or host name if host were used and host name of the server where applicable 132 Troubleshooting Guide FLEX mEnvironment Variables Environment variables are not required in order to use FLEX m licensed applications Environment variables are normally used for debugging or for changing license default location D 1 How to Set Environment Variables FLEX m environment variables are set in two different ways nthe process environment e Inthe registry Windows v6 04 or in HOMI which functions like the registry for FLEX m on UNIX D 1 1 Registry On Windows the FLEX m registry location is HK EY LOCAL MACHINI ENSoftwareNFLI EXIm License Manager E flexlmrc UNIX v7 04 E fleximrc In this On UNIX the equivalent information is stored in HOMI file the syntax is variable value D 1 2 Precedence If the variable is LM_LIC ENSE FILE or VENDOR LIC ENS E FIL E then both the environment and the registry are used with the environment used first and the registry appended to the p
11. lmreread FLEXLM VERSION NOTES e all option introduced in the v7 0 FLEX m Imdown utility force option introduced in the v8 0 FLEX m Imdown utility Imhostid The 1mhost id utility returns the FLEX m hostid of the current platform Invoked without any arguments 1mhost id displays the default hostid type for current platform Otherwise the hostid corresponding to the requested t ype is displayed if supported on the current platform Usage is lmhostid n type utf8 FLEXIm End Users Guide July 2003 85 Imhostid Where n Only the hostid itself is returned as a string which is appropriate to use with HOSTIDz in the license file Header text is suppressed type One of the following hostid types If not specified the default hostid for the current platform is displayed See Appendix A Expected FLEXIm Hostids for a list of the default types utf8 The hostid is output as a UTF 8 encoded string rather than an ASCII string If your hostid contains characters other than ASCII A through Z a through z or 0 through 9 use this option with Imhostid To view a correct representation of the resulting hostid use a utility such as Notepad that can display UTF 8 encoded strings Platform Dependent Hostids ether Ethernet address string String id vsn Volume serial number Windows platforms only flexid Parallel or USB FLEXid hardware key identification Windows platforms only long 32 bi
12. 1 2 How to Use This Manual 0 0 0 0 e 11 1 2 1 License Administrator 0 0 eese 11 12 2 EMG Ser 2 sn hay ican Bier bye ie ein Una ReR AER 12 1 3 FLEX m Components 13 1 3 1 Served Licenses a once epe bebo ges ets 13 1 3 2 Unserved Licenses ee Eee 14 1 3 3 Component Overview 0 cece eee eee ees 15 1 3 4 FLEX m Components Shipped by Your Vendor 17 1 4 The License Request Process 0 0 00 s ee eee eee eee 19 1 5 Configuring FLEXIm eee 19 1 6 Getting Started Checklist 0 0 0 0 eee eee eee 20 1 6 1 Installing Licensed Software 005 20 1 6 2 Notes for End Users llle 21 Chapter 2 License File Basites 526i cueste Lee lee bleed 23 2 1 Specifying Location of the License File 23 2 1 1 Setting the Path with an Environment Variable 25 2 2 License File Format Overview lslleeeeeleeenl 26 2 3 Types of License Files lleleee I 26 2 3 1 Floating Concurrent Licenses 00 0005 27 2 3 2 Node Locked Licenses 0 0 eee eee eee eee 27 2 3 3 Mixed Node Locked and Floating Licenses 28 Chapter 3 Managing Licenses from Multiple Vendors 29 3 1 Overview of Multiple License Management Strategies 29 3 2 Multiple Machines 0 0 cee eee ee eee 30 3 3 One Machine with Multiple License Servers
13. 2 4 Specifying Location of the License File Software vendors often recommend a specific location for your license file If you are running the application on multiple machines you have these options for making your licenses available on all the machines Place the license file in a partition which is available to all machines in the network that need the license file Copy the license file to all of the machines where it is needed Setthe LM LICENSE FILE Or VENDOR LICENSE FILE where VENDOR is the vendor daemon name environment variable to port host where host and port come from the SERVER line in the license file Alternatively if the license file SERVER line specifies a TCP IP port in the default port range 27000 27009 or does not specify a port thereby allowing the system to choose one from the default range use the shortcut specification host Table 2 1 shows some examples of LM LICENSE FILE and VENDOR LICENSE FILE environment variable settings FLEXIm End Users Guide July 2003 23 Specifying Location of the License File Table 2 1 Environment Variable Specification Examples LM_LICENSE_FILE or SERVER Line VENDOR_LICENSE_FILE Setting SERVER myserver 17007ea8 40000 myserver 40000 where host myserver e port 40000 SERVER myserver 17007ea8 myserver 27001 where e host myserver e port 27001 within the default range SERVER myserver 1
14. FLOAT OK keyword introduced in v8 0 FLEXIm client library license manager daemon and vendor daemon All components must be v8 0 in order to use FLOAT OK License Borrowing with BORROW If a license is to be used on a computer that is intermittently connected to a license server that license can be issued as a floating license with the BORROW keyword A BORROW license can be borrowed from a license server via a special checkout and used later to run an application on a computer that is no longer connected to the license server License borrowing must be enabled by a vendor before an end user can borrow licenses With license borrowing a vendor issues a floating license with a FEATURE line that contains the BORROW keyword An end user specifies the expiration date a borrowed license is to be returned and runs the application while connected to the network which writes borrowing information on the client computer The license server keeps the borrowed license checked out The FLEXIm licensed application automatically uses the local borrowing data to do checkouts during the borrow period If enabled by the vendor borrowed licenses can be returned early that is before the borrow period expires Upon the earlier of either the expiration of the borrow period or the early return of a borrowed license the local borrowing data no longer authorizes checkouts and the license server returns the borrowed license to the pool of available licenses No cl
15. No such feature exists 5 116 2 No such file or directory license file s usr myproduct licenses testing lic license lic lm checkout fl1 1 0 1 0x0 0x4000 Troubleshooting Guide FLEXLM_DIAGNOSTICS Note that the error message actually contains two separate problems which both occurred during the checkout There s no such feature in the license it did find t was unable to find the other license file which is what produces the message No such file or directory Following is a description of the arguments to Im checkout lm checkout feature version num lic queue flag dupgroup mask where feature The requested feature version The requested version The license file must contain a version the requested version num lic Number of licenses requested Usually 1 queue flag If 0 no queueing If 1 queue for license blocking queue If 2 queue for licenses but return to application non blocking queue dupgroup_mask Indicates duplicate grouping also called license sharing User host and display are as shown by lmstat a C 2 3 Level 3 Content FLEX m v6 0 only If FLEXLM DIAGNOSTICS is set to 3 then in addition to level 1 and 2 output if a checkout is successful information is printed explaining how the license was granted setenv FLEXLM DIAGNOSTICS 3 app Checkout succeeded 0 14263EAEA8E0 License file servtest lic O server used
16. RESERVE num_lic feature keyword value typ name group_name Reserves licenses for a specific user num_lic feature keyword value type name group_name Number of license to reserve for this user or group Feature this reservation applies to Feature name modifier to denote a group of licenses See the section Feature Specification for details One of USER HOST DISPLAY INTERNET PROJECT GROUP or HOST_GROUP See the section Type Specification for details Name of an item of type t ype for which license usage is reserved Name of group for which license usage is reserved To reserve one license of feature f1 for user mel RESERVE 1 f1 USI ER mel If you want to reserve a license for each of several users or groups you must use a separate RESERVE line for each user or group Note Any licenses reserved for a user are dedicated to that user Even when that user is not actively using the license it is unavailable to other users However a RESERV Ed license does not cause usage to be reported by SAMreport if the license is not actually in use 5 2 19 TIMEOUT TIMEOUT featur keyword value seconds Sets the time after which an inactive license is freed and reclaimed by the vendor daemon FLEXIm End Users Guide July 2003 61 How the Vendor Daemon Uses the Options File Note The vendor must have enabled this feature in the licen
17. See Section 7 14 Imswitchr for more details F3 Redirecting Report Log Output for a Vendor Daemon The report log output for a particular vendor daemon can be moved into separate files each file representing activity over a different period of time There are three ways in which to do this whether the vendor daemon is running or not Change the REPORTLOG line in the vendor daemon s options file and reread its options file by invoking 1mreread v8 0 vendor daemon or restart e Invoke 1mswitchr on the vendor daemon See Section 7 14 Imswitchr for more details e Invoke 1mnewlog on the vendor daemon Requires a v7 1 vendor daemon See Section 7 8 Imnewlog for more details 146 The Report Log File The Debug Log File The license server produces both debug log files and report log files The focus of this appendix is debug log files For information on report log files see Appendix F The Report Log File A debug log file contains status and error messages useful for debugging the license server A license server always generates debug log output Some of the debug log output describes events specific to Lmgrd and some of the debug log output describes events specific to each vendor daemon G1 Managing Debug Log Output As 1mgrd and its vendor daemons run for a period of time the volume of this output increases As it gets older the value of the debug log output decreases therefore it may be necessa
18. To display the current license path settings use lmpath status The following is displayed lmpath Copyright C 1989 2002 Macrovision Corporation Known Vendors demo counted lic uncounted lic FLEXIm End Users Guide July 2003 89 Imremove Other Vendors usr local flexlm licenses license lic Note that where the path is set to a directory all the 1ic files are listed separately 7 10 Imremove The 1mremove utility allows you to remove a single user s license for a specified feature If the application is active it re checks out the license shortly after it is freed by 1mremove Usage is lmremove c license file list feature user user host display Or lmremove c license file list h feature server host port handle where c license file list feature user user host display server host port 90 License Administration Tools Specify license file s Name of the feature checked out by the user Name of the user whose license you are removing as reported by 1mstat a Name of the host the user is logged into s reported by 1mstat a Name of the display where the user is working as reported by 1mstat a Name of the host on which the license server is running TCP IP port number where the license server is running as reported by 1mstat a 7 11 Imreread handle License handle as reported by 1mstat a The uses user host
19. a11 force If licenses are borrowed 1mdown runs only from the machine where the license server is running and then only if the user adds force If 1mdown encounters more than one server for example if c specifies a directory with many 1ic files and a11 is not specified a choice of license servers to shut down is presented License Administration Tools Note 7 6 Imhostid On UNIX do not use kill 9 to shut down the license servers On Windows if you must use the Task Manager to kill the FLEX m service be sure to end the 1mgrd process first then all the vendor daemon processes To stop and restart a single vendor daemon use 1mdown vendor vendor then use lmreread vendor vendor to restart the vendor daemon When shutting down a three server redundant license server there is a one minute delay before the servers shut down 1mdown shuts down all three license servers of a set of redundant license servers If you need to shut down one of a set of redundant license servers not recommended because you are left with two points of failure you must kill both the 1mgrd and vendor daemon processes on that license server machine You can protect the unauthorized execution of 1mdown when you start up the license manager daemon 1mgrd Shutting down the servers causes users to lose their licenses SEE ALSO e Section 6 1 Imgrd Command Line Syntax for details about securing access to 1mdown e Section 7 11
20. in those files so there is no need to enumerate each license file name on the 1mgrd command line SEE ALSO Section 3 5 Managing Multiple License Files Section G 1 2 Capturing Debug Log Output for a Particular Vendor Daemon FLEXLM VERSION NOTES Ability for one 1mgrd to process multiple license files introduced in v6 0 lmgrd Managing Multiple License Files You can manage multiple license files that are on the same server machine via a license file list A license file list is specified two ways e By using the c option to 1mgrd lmgrd c license file list other lmgrd options FLEXIm End Users Guide July 2003 33 Additional Considerations Note 3 6 3 6 1 34 e By defining the LM LICENSE FILE environment variable within the scope of the 1mgrd process environment Install the license files in convenient locations on the server machine and then define the 21cense file list Wherever 1icense file list is specified it consists of a list of one or more of the following components the full path to the license file e adirectory containing one or more license files with a 1ic extension oe 0 Use a colon to separate the license file names on UNIX and on Windows use a semicolon 1mgrd builds up an internal license file list when it starts up by parsing each license file list component in the order listed Some scenarios where a license file list is used i
21. 1 jan 2005 2 SIGN 1B9A308CCOF7 provide three v1 0 licenses of f1 and two v2 0 licenses of f1 An UPGRADE line operates on the closest preceding FEATURE or INCREMENT line with a version number that is gt rom feat version and lt to feat version UPGRADE lines do not work for node locked uncounted licenses Decimal Format Licenses can be represented in decimal format Decimal has the advantage that it s simpler to type in and often the licenses are much shorter A simple demo license in readable format FEATURE f1 sampled 1 00 1 jan 2005 0 keyi HOSTID DEMO and its decimal equivalent sampled f1 00737 55296 1825 If needed decimal lines can be mixed with readable format lines in a license file Use the 1minstall command to convert decimal licenses to readable format FLEXIm End Users Guide July 2003 127 License File Order SEE ALSO Section 7 7 Iminstall for additional information on the 1minstall command FLEXLM VERSION NOTES B 3 128 The decimal format was introduced in the v6 FLEXIm client library and vendor daemon License File Order The order of the lines in a license file is not critical They are sorted when they are processed so that in most cases the optimal result is achieved However pre v7 0 versions of FLEXIm licensed applications and license servers implicitly impose an ordering to license file lines Note the following suggestions for
22. Figure 1 1 FLEXIm Served License Component Model Typically the license server components reside on a machine in the network but can optionally reside on the same machine as the licensed application The three optional files Debug Log Administration Options and Usage Log files are configured by the end user Unserved Licenses License models that do not need a license server have two components The FLEXIm Licensed Application with the FLEX m static client library linked into it The License File Introduction and Overview 1 3 3 FLEXIm Components Figure 1 2 shows this model See Section 1 3 3 Component Overview fora description of each component FLEX m Licensed Application License File s gt Fe oO x 2 I c 2 o E x lt W p iL Figure 1 2 FLEXIm Unserved License Component Model The licensed application and license certificate reside on the same machine Component Overview THE LICENSE MANAGER DAEMON LMGRD The license manager daemon 1mgrd handles the initial contact with the FLEX Im licensed applications passing the connection on to the appropriate vendor daemon It also starts and restarts the vendor daemons Chapter 6 The License Manager Daemon contains information for configuring and starting the license manager daemon in your environment THE VENDOR DAEMON In FLEXIm counted floating licenses are granted by processes running on the system There is one proce
23. G The Debug Log File 0 0 eee cee ee 147 G 1 Managing Debug Log Output 006 147 G 1 1 Capturing Debug Log Output for a License Server 147 G 1 2 Capturing Debug Log Output for a Particular Vendor Daemon eee eee eee 148 G 1 3 Redirecting Debug Log Output for a Running Vendor Daemon 0 eee eee eee 148 G 1 4 Limiting Debug Log Output fora Vendor Daemon 148 G 2 Debug Log Messages lee eh 148 G 2 1 Informational Messages eese 149 G 2 2 Configuration Problem Messages 151 G 2 3 Daemon Software Error Messages 0 153 Appendix H FLEX m Versions 0 0 0 cece eee eens 155 H 1 Version Compatibility and Components 155 H 2 How to Tell the License File Version 4 155 H3 Version Summary d EV ta tea eh 156 Index Aigo eee RIVERA eens VER Sie ies eee AN ED 161 FLEXIm End Users Guide July 2003 vii viii FLEXIm End Users Guide July 2003 ama Preface Welcome to FLEXIm the de facto standard network license manager used by over 2000 leading software vendors to control the use of their software products If you are a system administrator or user chances are one or more of the products currently on your network is licensed by FLEXIm About This Manual This manual explains FLEX m for administrators and end users and describes how to use the tools which are pa
24. GROUPCASEINSENSITIVE is OFF user names and host names are treated as case sensitive HOST_GROUP HOST_GROUP group_name host_list Defines a group of hosts for use in INCLUDE INCLUDEALL EXCLUDE EXCLUDEALL and RESERVE option lines Multiple HOST_GROUP lines add all the specified hosts into the group group_name Name of the group being defined Host group names are Case sensitive host_list List of host names in that group Names are case sensitive Set the FLEXLM_GROUPCASEINSENSITIVE environment variable to turn on case insensitivity See Appendix D Environment Variables 99 66 To define the host group Pacific consisting of tokyo seattle and auckland HOST_GROUP Pacific tokyo seattle auckland The Options File 5 2 9 Note Options File Syntax Anywhere a host name can be used in an options file an IP address can be used instead INCLUDE INCLUDE feature keyword value type name group name Includes a user or pre defined group of users etc in the list of who is allowed to use licenses for this feature Anyone not in an INCLUDE statement is not allowed to use that feature EXCLUDE supersedes INCLUDE conflicts between the EXCLUDE list and the INCLUDE list are resolved by the EXCLUDE taking precedence feature Name of the feature being affected keyword value Feature name modifier to denote a group of licenses See the section Feature Specificati
25. LOWWATER options keyword introduced in v8 0 vendor daemon EXCLUDE BORROW options keyword introduced in v8 0 vendor daemon INCLUDE BORROW options keyword introduced in v8 0 vendor daemon COMMENTS Include comments in your options file by starting each comment line with a pound sign FEATURE SPECIFICATION The feature name can be modified with an optional keyword value pair to fully qualify it This notation is used for distinguishing a particular group of licenses when there are multiple FEATURE lines for a single feature The following syntax is used feature keyword valu For example 1 VERSION 2 0 specifies the version 2 0 pool of licenses for feature f1 The Options File Note Options File Syntax A colon is a valid feature name character If colons are in your feature names specify a group of licenses with the following alternative syntax using quotation marks and spaces feature keyword value The following option keywords are used as feature name modifiers to denote a specific group of licenses VERSION HOSTID EXPDATE KEY SIGN ISSUER NOTICE e VENDOR STRING if configured by the vendor as a pooling component e dist info e user info e asset info If the USER BASED or HOST BASED keywords appear in a feature line this feature specification syntax must be used to qualify the feature Using a package name in place of a feature name applie
26. Running Vendor Daemon Itis possible to redirect the debug log output for a particular vendor daemon to a different file There are two ways to do this Change the DEBUGLOG line to the options file for the vendor daemon and reread its options file by invoking 1mreread See Section 5 2 2 DEBUGLOG for more details e Invoke 1mswitch on the vendor daemon See Section 7 13 Imswitch for more details Limiting Debug Log Output for a Vendor Daemon By default debug log output contains all events To limit the events that are logged for a particular vendor daemon add a NOLOG line to the options file of that vendor daemon See Section 5 2 16 NOLOG for more details One of the reasons you may want to limit the events that are logged is to reduce the size of the debug log output Debug Log Messages FLEX m daemons generate debug log files in the following format hh mm ss daemon message where hh mm ss Time that the message was logged daemon Either 1mgrd or the vendor daemon name In the case where a single copy of the daemon cannot handle all of the requested licenses an optional followed by a number indicates that this message comes from a forked daemon The Debug Log File Debug Log Messages message The text of the message The debug log files can be used to Diagnose configuration problems Diagnose daemon software errors Note A debug log file cannot be used for usage reporting with SAMreport
27. a license for that package one or more corresponding FEATURE INCREMENT lines enable the PACKAGE line Example PACKAGE package vendor pkg_version COMPONENTS pkg_list OPTIONS SUITE SUPERSEDE pl p2 ISSUED date SIGN pkg sign Table B 4 lists the PACKAGE line fields They must appear in the order listed Table B 4 PACKAGE Line Fields Field Description package Name of the package The corresponding FEATURE INCREMENT line must have the same name vendor Name of the vendor daemon that supports this package pkg version Optional field specifying the package version If specified the enabling FEATURE INCREMENT line must have the same version 124 License File Format License File Syntax Table B 4 PACKAGE Line Fields Continued Field COMPONENTS pkg_list Description List of package components The format is feature version num_lic Packages must consist of at least one component Version and count are optional and if left out their values come from the corresponding FEATURE INCREMENT line num_lic is only legal if OPTIONS SUITE is not set in this case the resulting number of licenses is num_lic on the COMPONENTS line multiplied by the number of licenses in the FEATURE INCREMENT line Examples COMPONENTS compl comp2 comp3 comp4 COMPONENTS compl 1 5 comp2 comp3 2 0 4 OPTIONS SUITE Optional field Used
28. application program using FLEX m is linked with the program module called the FLEXIm client library that provides the communication with the license server During execution the FLEX m licensed application communicates with the vendor daemon to request a license Introduction and Overview 1 3 4 FLEXIm Components DEBUG LOG FILE The debug log file contains status and error messages useful for debugging the license server Some of the debug log output describes events specific to lmgrd and some of the debug log output describes events specific to each vendor daemon See Appendix G The Debug Log File for more information about this file END USER ADMINISTRATION OPTIONS FILE The end user administration options file allows the end user license administrator to control various operating parameters of FLEX m that remain within the license rights granted to them by the vendor Specifically the license administrator can Allow the use of features Deny the use of features Reserve licenses Restrict the number of licenses available Control the amount of debugging information logged about license usage Enable a report log file See Chapter 5 The Options File for details on how to create this file REPORT Loc FiLE The report log file contains feature usage information and is generated by the vendor daemon Report log output is encrypted and is consumed by reporting products such as SAMreport and FLEXbill See
29. command shell using the following syntax C flexlm gt lmgrd c license file list L debug log path where license file listis one or more of the following the full path to a single license file a directory where all files named 1ic in that directory are used debug log pathis the full path to the debug log file Prepending debug log path with the character appends logging entries Spaces in pathnames require double quotes around the path On Windows 1mgrd can be installed as a service to allow it to be started and stopped through a user interface and run in the background FLEXIm End Users Guide July 2003 71 Starting the License Manager Daemon on Windows 6 3 2 Configuring the License Manager as a Windows Service To configure a license server as a service you must have Administrator privileges 1 Run LMTOOLS 2 Click the Configuration using Services radio button then click the Config Services tab 3 In the Service Name type the name of the service that you want to define for example Myvendor License Manager 4 In the Path to the Imgrd exe file field enter or browse to 1mgrd exe for this license server 5 In the Path to the license file field enter or browse to the license file for this license server 6 In the Path to the debug log file enter or browse to the debug log file that this license server writes Prepending the debug log file name with the character appends logging entrie
30. display server host port and handle information must be obtained from the output of 1mstat a l1mremove removes all instances of user on user host and display from usage of feature If the optional c license file listis specified the indicated file s is used as the license file The h variation uses the server host port and license handle as reported by 1mstat a Consider this example 1mstat a output joe nirvana dev ttyp5 v1 000 cloud9 7654 102 start Fri 10 29 18 40 In this example the user is joe the user host is nirvana the display is dev typp5 the server host is cloud9 the TCP IP port is 7654 and the license handle is 102 To remove this license issue one of the following commands lmremove f1 joe nirvana dev ttyp5 Or lmremove h f1 cloud9 7654 102 When removing by handle if licenses are grouped as duplicates all duplicate licenses are also removed If license lingering is set and 1mremove is used to reclaim the license Lmremove starts but does not override the license s linger time You can protect the unauthorized execution of 1mremove when you start up the license manager daemon 1mgrd because removing a user s license is disruptive SEE ALSO e Section 6 1 Imgrd Command Line Syntax for details about securing access to 1mremove Imreread The 1mreread utility causes the license manager daemon to reread the license file and start any new vendor
31. of clearing the LM BORROW setting for the vendor daemon that serves the returned license If the borrowing system is not placed back on the network before attempting the early return the license is not returned and LM BORROW is kept intact Additionally an error message is issued to the end user with notification that the system needs to be connected to the network FLEXLM VERSION NOTES Early borrowed license return introduced in v8 3 FLEXIm utilities 82 License Administration Tools 7 4 Imdiag Imdiag 1mdiag allows you to diagnose problems when you cannot check out a license Usage is lmdiag c license file list n feature keyword value where c license file list Diagnose the specified file s n Run in non interactive mode 1mdiag does not prompt for any input in this mode In this mode extended connection diagnostics are not available feature Diagnose this feature only keyword value If a license file contains multiple lines for a particular feature select a particular line for 1mdiag to report on For example lmdiag f1 HOSTID 12345678 attempts a checkout on the line with the hostid 12345678 keyword is one of the following VERSION HOSTID EXPDATE KEY VENDOR_STRING ISSUER If no feature is specified 1mdiag operates on all features in the license file s in your list 1mdiag first prints information about the license then attempts to check out each license If the checkout succe
32. ordering lines in the license file Place FEATURE lines before INCREMENT lines for the same feature The rule regarding FEATURE lines is that only the first counted FEATURE line is observed by the license server and that if there is a FEATURE line and INCREMENT lines the FEATURE line must appear first Where multiple counted FEATURE lines exist for the same feature make sure the desired FEATURE line appears first All but the first is ignored Place node locked uncounted lines before floating lines for the same FEATURE Otherwise it is possible the floating license is consumed instead of the node locked license resulting in denial for other users The placement of a USE SERVER line affects behavior A USE SERVER line is recommended Normally the USE SERVER line is placed immediately after the SERVER line However place any uncounted licenses not served by SERVER before the USE SERVER line Make sure each user that needs the uncounted license has direct access to a current copy of the file The advantage to placing USE SERVER right after the SERVER line is users don t need up to date copies of the license file License File Format Troubleshooting Guide This appendix documents areas of FLEX m that have given customers difficulty in the past C 1 General Troubleshooting Hints The following are tips for debugging When you start the license server 1mgrd be sure that you direct the output into a local log file where you
33. server 18 License server does not support this feature 19 Error in select system call 21 License file does not support this version 22 Feature checkin failure detected at license server 23 License server temporarily busy new server connecting 24 Users are queued for this feature 25 License server does not support this version of this feature FLEXIm End Users Guide July 2003 139 Error Code Descriptions Table 8 1 FLEXIm Error Codes Continued Error Code Description 26 Request for more licenses than this feature supports 29 Cannot find ethernet device 30 Cannot read license file 31 Feature start date is in the future 32 No such attribute 33 Bad encryption handshake with daemon 34 Clock difference too large between client and server 35 In the queue for this feature 36 Feature database corrupted in daemon 37 Duplicate selection mismatch for this feature Obsolete with v8 0 vendor daemon 38 User host on EXCLUDE list for feature 39 User host not on INCLUDE list for feature 40 Cannot locate dynamic memory 41 Feature was never checked out 42 Invalid parameter 47 Clock setting check not available in daemon 52 FLEXIm vendor daemon did not respond within timeout interval 53 Checkout request rejected by vendor defined checkout filter 54 No FEATURESET line in license file 55 Inco
34. than once that day no duplicate license is borrowed No license is borrowed if the application is run on a day different than the date borrowing was set to be initiated For example say that today you want to borrow a license for the PageWizard feature for a week The PageWizard feature is served by the sampled vendor daemon Today while you are connected to the network run 1mborrow or set LM BORROW directly For example lmborrow sampled enddate Today after you run 1mborrow while you are connected to the network run the application that checks out a license for the PageWizard feature After the license is checked out close the application and disconnect your machine from the network The license that you just checked out stays checked out from the license server until the borrow period expires that license now is used on your disconnected machine until the borrow period expires The borrowed Mobile Licensing 8 4 3 License Borrowing with BORROW license cannot be returned before the end of the borrow period Once checked out it remains checked out for the full borrow period The borrow period cannot be renewed until the period has expired CLEARING THE BORROW PERIOD Once you have borrowed all the licenses that you need for the current borrow period defined by the LM_BORROW environment variable prevent licenses for any additional features from being borrowed by running 1mborrow clear This clears the LM_BORROW setting in
35. the registry Windows or SHOME flexlmrc UNIX 1mborrow clear does not clear the local information about licenses you have already borrowed CHECKING BORROW STATUS To print information about borrowed features issue the following command on the machine from which they are borrowed lmborrow status The borrowing system does not have to be connected to the network to determine the status RETURNING A BORROWED LICENSE EARLY To return a borrowed license before the borrow period expires first reconnect the borrowing system back to the network and then from the same machine that initiated the borrowing issue the command lmborrow return c license file list feature This option may or may not be allowed by your vendor Check directly with your vendor to determine if early borrowed license return is supported Returning the license early has the effect of clearing the LM BORROW setting for the vendor daemon that serves the returned license Support for License Borrowing See the following sections for more information about the utilities and end user options that support license borrowing e Section 7 3 Imborrow Section 7 5 Imdown e Section 7 12 Imstat Section 5 2 1 BORROW LOWWATER Section 5 2 4 XEXCLUDE BORROW FLEXIm End Users Guide July 2003 105 Node locked to a User Name Section 5 2 10 INCLUDE BORROW FLEXLM VERSION NOTES 8 5 8 6 106 BORROW keywor
36. 1 0 permanent uncounted FLOAT OK HOSTID FLEXID 7 b28520b9 SIGN 123456789012 FEATURE f1 sampled 1 0 permanent uncounted FLOAT OK HOSTID FLEXID 7 b2857678 SIGN ABCDEF123456 The customer installs the license file and the two FLEXids on the license server machine When attached to the license server machine each uncounted FLOAT OK license floats on the network and allows a single use Therefore up to two users can use f1 on the customer s network except on the license server machine itself where the license use is disallowed FLEXIm End Users Guide July 2003 101 License Borrowing with BORROW 8 4 102 If an end user wants to work at home the end user installs a license file that contains the FEATURE line node locked to FLEXID 7 b28520b9 this only needs to be done once transfers the FLEXid FLEXID 7 b28520b9 from the license server machine to the client computer and installs the FLEXid driver on the client computer this also only needs to be done once The end user disconnects the client computer from the network and uses the transferred FLOAT_OK license on the client computer The license server allows only the single remaining FLOAT_OK license to float on the network After returning the FLEXid to the license server machine the end user or the system administrator runs 1mreread so the returned license can float again FLEXLM VERSION NOTES
37. 1700 VENDOR sampled etc mydaemon E E EATURE f1 sampled 1 000 01 jan 2005 5 26C7DD9C0186 EATURE f2 sampled 1 000 01 jan 2005 5 8CE46C57041D License 2 for tokyo SERVER tokyo 17a07e08 1700 VENDOR sampled etc mydaemon E F EATURE f1 sampled 1 000 01 jan 2005 5 16BE40E1D98D EATURE f2 sampled 1 000 01 jan 2005 5 6DB6FS3E402DF The user in Chicago could set LM LICENSE FILE to 1700 chicago 1700 tokyo The user in Tokyo could set LM LICENSE FILE to 1700 tokyo 1700 chicago Remember to separate the license file names with a colon on UNIX and with a semicolon on Windows The application attempts the first server in the list and if that fails for any reason the second server is tried Three Server Redundancy These three server redundant servers need to have excellent communications on a reliable network and need to be located on the same subnet The three servers must be located physically close to each other This form of redundancy requires that the servers exchange heartbeats periodically and poor communications can cause poor performance Avoid configuring redundant servers with slow communications or dial up links Three server redundancy is designed to provide hardware failover protection only and does not provide load balancing Use LM LICENSE FILE list instead if load balancing is desired This is be
38. 2048 character limit per feature v4 0 DECEMBER 1994 Removed use of floating point for enhanced reliability FEATURE line additions ck OVERDRAFT DUP_GROUP INTERNET hostid PACKAGE line License Finder lmdiag and FLEXLM DIAGNOSTICS for end user diagnostics v4 1 May 1995 Performance improvements and new platform support V4 1 PATCH RELEASE 6 OCTOBER 1995 Windows patch release for Windows 95 with various performance improvements v5 0 MARCH 1996 Improved port host behavior FLEXIm licensed application doesn t read license file Automatic port host via USE SERVER line in license file Hostid lists lock a feature to several hostids New FEATURE attributes SN serial number USER BASED HOST BASED MINIMUM SUPERSEDE ISSUED issued date CAPACITY charging based on system capacity Optional avoidance of NIS and DNS via IP address instead of host name Improved report log file format Server upon startup notifies of licenses that expire within two weeks Improved end user options file functionality v5 11 FEBRUARY 1997 SUPERSEDE lists PLATFORMS license attribute FLEXIm End Users Guide July 2003 157 Version Summary 158 new end user options MAX TIMEOUTALL Windows control panel added Windows license generator GENLIC added v5 12 APRIL 1997 Performance improvements and new platform support V6 0 SEPTEMBER 1997 lmgrd can read multiple license files FLEX m license directo
39. 5 redundant servers 114 syntax 114 setting environment variables 133 SIGN 119 signature 119 SN 121 sockets number used by license server 39 specifying location of license file 23 START 121 starting Imgrd 69 status of license server 93 SUITE_DUP_GROUP 121 SUPERSEDE 122 switching debug log FLEXIm End Users Guide July 2003 165 Imswitch 95 switching report log Imnewlog 88 Imswitchr 96 T term X three server redundancy 42 TIMEOUT 61 TIMEOUTALL 62 troubleshooting with FLEXLM_DIAGNOSTICS 130 with Imdiag 83 TS_OK 122 typographic conventions X U UPGRADE line syntax 127 USE_SERVER line 117 USER hostid 110 USER type 49 USER_BASED 122 user_info 122 user_info 121 V vendor daemon and redundant servers 60 debug log file 148 Imnewlog 88 Imreread 91 Imswitchr 96 memory usage 40 options file 46 overview 15 restarting 85 uncounted licenses 44 VENDOR LICENSE FILE 134 version compatibility 67 vendor daemon name FEATURE line 118 VENDOR line 115 vendor daemon path 116 VENDOR line 115 options file path 116 port number 116 vendor daemon name 115 vendor daemon path 116 vendor opt 46 116 vendor info 122 VENDOR LICENSE FILE 25 134 VENDOR STRING 122 166 FLEXIm End Users Guide July 2003
40. 6 The License Manager Daemon License Administration Tools FLEX Im provides utilities for the license administrator to help manage the licensing activities on the network Always use the newest version of the utilities as possible they are available for download from www macrovision com Table 7 1 lists these utilities Table 7 1 License Administration Utilities Utility Description lmborrow Supports license borrowing lmdiag Diagnoses license checkout problems lmdown Gracefully shuts down selected license daemons both 1mgrd and all vendor daemons on the license server machine or on all three machines in the case of three server redundant servers lmhostid Reports the hostid of a system lminstall Converts license files between different formats lmnewlog Moves existing report log information to a new file name and starts a new report log file with existing file name lmpath Allows users direct control over license file path settings lmremove Releases a hung license to the pool of free licenses lmreread Causes the license daemon to reread the license file and start any new vendor daemons FLEXIm End Users Guide July 2003 77 Running Administration Tools Table 7 1 License Administration Utilities Continued Utility Description lmstat Displays the status of a license server lmswitch Controls debug log location and size lmswitchr Switches the
41. 7007ea8 myserver where e host myserver port none specified uses a default TCP IP port number in the range of 27000 27009 On Windows if the application cannot find the license file the user is presented with a dialog that asks the user to specify the license file location the license server or license fulfillment from the internet Since the vendor daemon keeps track of license usage and since the license file contains encrypted data to protect it against modification you may move and copy the license file as much as necessary For counted licenses no matter which option you choose you must first copy lmgrd and the vendor daemon to a location accessible by the licensed application 24 License File Basics Specifying Location of the License File 2 1 1 Setting the Path with an Environment Variable Most applications specify a location where they expect to find the license file and install it automatically However you can change the license file location by setting the LM_LICENSE_FILE environment variable to a license file list Wherever license file list is specified it can consist of the following components the full path to the license file e adirectory containing one or more license files with a lic extension aport host setting where port and host are the TCP IP port number and host name from the SERVER line in the license file Alternatively use the shortcut specification
42. 8 1 debug log path local x lmdown x lmremove The License Manager Daemon Write debugging information to file debug log path This option uses the letter 1 not the numeral 1 Prepending debug log path with the character appends logging entries See Appendix G The Debug Log File for more information on this file Restricts usage of 1mdown 1mreread and 1mremove to a FLEX m administrator who is by default root If there a UNIX group called Imadmin then use is restricted to only members of that group If root is not a member of this group then root does not have permission to use any of the above utilities If 2 p is used when starting 1mgrd no user on Windows can shut down the license server with lmdown Restricts the 1mdown command to be run only from the same machine where lmgrd is running Disable the 1mdown command no user can run 1mdown If 1mdown is disabled stop 1mgrd via kill pid UNIX or stop the 1mgrd and vendor daemon processes through the Windows Task Manager or Windows service On UNIX be sure the ki11 command does not have a 9 argument Disable the 1mremove command no user can run 1mremove 6 2 Note 6 2 1 Starting the License Manager Daemon on UNIX Platforms z Run in foreground The default behavior is to run in the background If 1 debug_log_path is present then no windows are used but if no 1 argument specified separate windows are used for 1
43. ASED or SN appear gt Version 6 START appears gt Version 7 1 SIGN keyword appears gt Version 8 BORROW FLOAT_OK and TS_OK appear Version Summary v1 0 1988 First FLEX m Release containing all the basic FLEX m features V1 5 FEBRUARY 1990 First widely used version including DEMO v2 1 MARCH 1991 Improved TIMEOUT support Improved ethernet hostid support v2 21 NOVEMBER 1991 Added support for many platforms and some platform specific improvements such as hostid Hostid ANY added v2 26 MaARcH 1992 USED ONLY BY SUN Added license lingering v2 4 DECEMBER 1992 Added use all feature lines capability for incremental license distribution Enhanced vendor customization routines Enhanced end user options file Added new hostid types USER HOSTNAME and DISPLAY e Added port host to locate license file downloads license file from server v2 61 MARCH 1993 USED ONLY BY SUN Added INCREMENT and UPGRADE lines to license file FLEXIm Versions Version Summary V3 0 May 1994 INCREMENT and UPGRADE behavior changed and improved Added UDP protocol support Added uname i hostid for HP Added multiple jobs for enhanced support of LM_LICENSE_FILE environment variable as a license file list New optional license file format with keyword value syntax for optional new features including asset_info ISSUER and NOTICE license file continuation character
44. Appendix F The Report Log File details regarding this file FLEX m Components Shipped by Your Vendor This section provides a list of FLEX m components that may be supplied to you by your software vendor along with the FLEX m licensed application Table 1 1 provides a general list and may differ from that actually supplied Your vendor is the definitive source for the list of FLEX m components that are shipped FLEXIm End Users Guide July 2003 17 FLEXIm Components 18 Table 1 1 FLEXIm Components for End User Distribution Component Windows and UNIX Description Common Components lmgrd exe 1mgrd UNIX vendor exe vendor UNIX Required for served license models The license manager and vendor daemons where vendor is the name of your vendor lmutil exe 1mutil UNIX Optional component FLEX m utilities program Used for license server management and administration Also available from www macrovision com Additional Windows Components lmtools exe Optional component Graphical user interface for FLEXIm utilities lmutil exe Also available from www macrovision com lmgr8b dll Required if the FLEX m licensed application is dynamically linked This library provides the standard FLEXIm client library routines fldata ini and flrsrc dll Required for applications which support try before you by FLEXlIock licensing flexid exe or flexidsile
45. BUGLOG DEBUGLOG debug log path Specifies a location for the debug log output from the vendor daemon associated with this options file Preceding the debug 1og path with a character appends logging entries otherwise the file is overwritten each time the daemon is started Note that this affects output from only the vendor daemon associated with this options file The debug log output of 1mgrd and any other vendor daemons in the same license file is not captured in this file SEE ALSO e Section 7 13 Imswitch Appendix G The Debug Log File FLEXLM VERSION NOTES Debug log output restricted to that of just the vendor daemon introduced in V8 vendor daemon FLEXIm End Users Guide July 2003 51 Options File Syntax 5 2 3 5 2 4 52 EXCLUDE EXCLUDE feature keyword value type name group name Excludes a user or pre defined group of users etc from the list of who is allowed to use the feature EXCLUDE supersedes INCLUDE conflicts between the EXCLUDE list and the INCLUDE list are resolved by the EXCLUDE taking precedence feature Name of the feature being affected keyword value Feature name modifier to denote a group of licenses See the section Feature Specification for details type One of USER HOST DISPLAY INTERNET PROJECT GROUP or HOST_GROUP See the section Type Specification for details name Name of an item of type t ype for which license us
46. CENSE FILE requires v6 04 clients Used for initiating license borrowing and setting the borrow period See Section 8 4 1 Initiating License Borrowing for more details FLEXIm Environment Variables Environment Variables LM_PROJECT LM PROJECT s value is logged in the report log file and later reported on by SAMreport Limited to 30 characters v5 04 client required This can also be used to RESERVE INCLUDE etc licenses with PROJECT For example RESERVE 1 f1 PROJECT airplane v5 04 clients and v7 0 vendor daemon are required for this feature FLEXIm End Users Guide July 2003 135 Environment Variables 136 FLEXIm Environment Variables FLEX m Error Codes E 1 Error Message Format FLEX m error messages presented by applications have the following components FLEX m Error Number a negative number starting at 1 FLEX m Error Text short sentence 80 characters summarizing problem FLEX m Error Explanation optional short paragraph 3 5 lines explaining problem and possible solutions or workarounds FLEX m Minor Error Number a positive number starting at 1 These numbers are unique error identifiers and are used by FLEX m vendors for more advanced support assistance Their meaning is not documented System Error Number optional a UNIX or Windows OS error code last set by the operating system System Error Explanation
47. EATURE INCREMENT Lines 2 4 117 B 1 6 PACKAGE Lines eee 124 B 1 7 UPGRADE Lines 2 0 a eee eee eee 127 B Z DecimalBotrm t uev nee ay eae E ey ae 127 B 3 License File Order i cess eee Dae ld eene 128 Appendix C Troubleshooting Guide 0 0 0 cece eee eee 129 C 1 General Troubleshooting Hints 00005 129 C 2 FLEXLM_DIAGNOSTICS 0 0 0 0 eee ee eee 130 C21 Level f Content 6s vA Ae ee 130 C 2 2 Level2 Content 1 Let ee ee RR 130 C 2 3 Level 3 Content FLEX m v6 0 only lusus 131 Appendix D FLEX m Environment Variables eee 133 D 1 How to Set Environment Variables 0 133 Did id R gistty ng nnee SE wid a eases date ge ee 133 D 1 2 Precedence picor ek one pe yes wee ee SET 133 D 2 Environment Variables 0 0 0 eee eee eee 134 vi FLEXIm End Users Guide July 2003 Appendix E FLEX m Error Codes 0 0 00 137 E Error Message Format sis eese dee agora eee 137 E 1 1 Format 1 short asrin a EA eens 137 E 1 2 Format 2 long version 6 0 0 00000 eee 138 E 2 Error Code Descriptions 0 0 0 cece eee 138 Appendix F The Report Log File 0 0 0 B 145 F 1 Managing Report Log Output 0 000 145 F 2 Enabling Report Log Output fora Vendor Daemon 146 F 3 Redirecting Report Log Output for a Vendor Daemon 146 Appendix
48. ENDOR line You can modify these elements in the license file Host names on the SERVER line s TCP IP port numbers on the SERVER line s Paths on the VENDOR line s Options file paths on the VENDOR line s Optional TCP IP port numbers on the VENDOR line s for firewall support only USE SERVER line e Values in keyword value pairs on FEATURE lines if keyword is specified in lowercase SEE ALSO Section 4 3 Redundant License Servers Section 4 4 Counted vs Uncounted Licenses Appendix B License File Format for details on each one of these components FLEXLM VERSION NOTES USE SERVER introduced in the v5 0 FLEXIm client library VENDOR lines are known as DAEMON lines in the pre v6 0 1mgrd and vendor daemon Types of License Files License files are created by the software vendor License files specify floating concurrent usage node locked both counted and uncounted or any combination of floating counted and uncounted License File Basics 2 3 1 2 3 2 Types of License Files Floating Concurrent Licenses A floating license means anyone on the network can use the FLEX m licensed application up to the limit specified in the license file also referred to as concurrent usage or network licensing Floating licenses have no hostids on the individual FEATURE lines Floating licenses requires an lmgrd and a vendor daemon to be running to count the concurrent usage of the licens
49. K SERIAL NUM number Volume Serial Number 3e2e17fd is and remove FLEXid lmhostid flexid FLEXID 7 b28520b9 parallel or USB port FLEXids are made available by your vendor Your hardware key vendor can also provide you with an installer that dongle installs drivers for all FLEXids A 3 Special FLEX m Hostids FLEX m contains a number of special hostid types which apply to all platforms These hostid types are valid to use in both SERVER lines and FEATURE lines wherever a hostid is required These are DEMO COMPOSITE P composit hostid Locks the software to any machine i e does not lock anything Similar to ANY but only for use with uncounted FEATURE lines Locks the software to a composite hostid A composite hostid is a hashed 12 character hexidecimal value formed by combining the values of one or more simple hostids types as defined by the software vendor FLEXIm End Users Guide July 2003 109 Special FLEXIm Hostids DISPLAY display HOSTNAME host ID n INTERN HITS ttt ttt EEH HEH USER u ser Locks the software to display display On UNIX display is dev ttyxx which is always dev tty when an application is run in the background or the X Display name On Windows it is the system name or in the case of a terminal server environment the terminal server client name v8 licensed applications only Locks the software to comput
50. LOG IN To turn off logging of checkouts and queued requests two separate NOLOG lines are required NOLOG DENIED NOLOG QUEUED License administrators use this option to reduce the size of the debug log file However it can reduce the usefulness of the debug log in debugging license server problems See also Section 7 13 Imswitch 5 2 17 REPORTLOG Note 60 REPORTLOG report_log_path REPORTLOG specifies the report log file for this vendor daemon It is recommended preceding the report_log_path witha character to append logging entries otherwise the file is overwritten each time the daemon is started On Windows pathnames which include spaces have to be enclosed in double quotes SAMreport a separate product available from Macrovision is used to process FLEX m report log files SAMreport processes only report log files not debug log files REPORTING ON PROJECTS WITH LM PROJECT The SAMreport report writer reports on projects A project is set up by having all users working on the same project set their LM PROJECT environment variable or registry on Windows to a string that describes the project SAMreport groups usage by project as defined by what LM PROJECT was set to when the application was run SEE ALSO e Appendix D FLEXIm Environment Variables Appendix F The Report Log File The Options File 5 2 18 RESERVE Options File Syntax
51. M VERSION NOTES uncounted keyword introduced in v6 FLEXIm client library 44 Selecting Server Machines The Options File The options file allows the license administrator to control various operating parameters of FLEX m Users are identified by their user name host name display IP address or PROJECT which is set with the LM_PROJECT environment variable Specifically the license administrator can Allow the use of features Deny the use of features Reserve licenses Restrict the number of licenses available Control the amount of information logged about license usage Enable a report log file Options files allow you as the license administrator to be as secure or open with licenses as you like Lines in the options file are limited to 2048 characters The V character is a continuation character in options file lines FLEXLM VERSION NOTES PROJECT identification set by LM PROJECT in options file introduced in v7 0 vendor daemon 5 1 Creating an Options File To create an options file 1 Use the appropriate options listed in Section 5 2 Options File Syntax to create the options file using any text editor FLEXIm End Users Guide July 2003 45 Options File Syntax 2 Locate the options file anywhere however it is recommended that the options file be placed in the same directory as the license file 3 Add the path to the options file in the license file as the fourth field
52. MENTS GB the host id is a different type even INCREMENT f6 GHI though the server name is the same Figure 3 5 Combining License Files FLEXIm End Users Guide July 2003 37 Additional Considerations 3 6 2 Version Component Compatibility 38 When one Imgrd process manages multiple vendor daemons it may be the case that those vendor daemons do not use the same version of FLEX m By observing the FLEX m version compatibility rules described in Section H 1 Version Compatibility and Components you are assured that all of your FLEX m components are compatible For specific FLEX m licensed applications use either the new or the old version of course the vendor daemon for that application must be at least as new as the application itself Managing Licenses from Multiple Vendors Selecting Server Machines This chapter helps you decide which machines to use as license server machines 4 1 Resources Used by the Server This section discusses the resources used by the license server When you select a server machine you may need to take into account the system limits on these resources For small numbers of licenses under about 100 most of these system limits are not a problem on any workstation 4 1 1 Sockets When using TCP IP ports each FLEX m enabled application connected to a license server uses one or more sockets The number of sockets any one FLEX m enabled application requires is dependant on FLEX
53. NES 51 5 2 3 EXCLUDB oer RAE i edd Geek we 52 5 2 4 EXCLUDE BORROW seen 52 23 2 5 EXCLUDBALT nev een ge eee e EVER 53 52 01 GROUP Ani ooo be ee sepe re grep s 53 5 2 GROUPCASEINSENSITIVE 20 0 0 000000 54 5 2 8 HOST GROUPD eee eR Saas 54 25 2 9 INCEUDE enr r e eer p eH WI e 55 5 2 10 INCLUDE BORROW sse ene 56 9 221 HINGEUDEALLEL 2 they ba eve Lae es Sete ds 56 2 2 12 LINGBR 5 Ruhe ETE 57 5 213 MAX seda e rubis eno hele e estes tas eu Sale eaten 58 5 2 14 MAX BORROW HOURS eese 59 5 2 15 MAX OVERDRAFT seeee ee eee 59 5 2416 NOEOG c soieie eus E uA NERA NE edad eie aud 59 S217 REPORTEOG restan aa Le ers she nba nforetus 60 5 2418 RESERVE fous 8h veto aun ye AAE E ba hey REV 61 5 2 9 TIMEOUT or EG pU Ree Iber PEERS 61 92 20 TIEIMEOUTALL bii ee hae ee oes 62 FLEXIm End Users Guide July 2003 5 3 How the Vendor Daemon Uses the Options File 62 5 4 Rules of Precedence in Options Files 04 63 5 5 Options File Examples sleleeeee en 63 5 5 1 Simple Options File Example 005 63 5 5 2 Limiting Access for Multiple Users sess 64 5 5 3 EXCLUDE Example ence ee 65 5 5 4 INCLUDE Example ses eni onre suri noi Eaa eee eee 65 Chapter 6 The License Manager Daemon 00 00 e eee eee 67 6 1 Imgrd Command Line Syntax 0 000000 0005 67 6 2 Starting
54. Q2 1 Informational Messages Message Description Connected to host This daemon is connected to its peer on host CONNECTED master is host The license daemons log this message when a quorum is up and everyone has selected a master DENIED num lic feature to user Was denied access to num 1ic user licenses of feature EXITING DUE TO SIGNAL nnn All daemons list the reason that the EXITING with code nnn daemon has exited EXPIRED feature feature has passed its expiration date IN feature user num_lic user has checked in num_lic licenses licenses of feature FLEXIm End Users Guide July 2003 149 Debug Log Messages Message Lost connection to host Description A daemon can no longer communicate with its peer on node host which can cause the clients to have to reconnect or cause the number of daemons to go below the minimum number in which case clients may start exiting If the license daemons lose the connection to the master they kill all the vendor daemons vendor daemons shut themselves down Lost quorum The daemon lost quorum so it processes only connection requests from other daemons MULTIPLE vendor servers running Please kill and restart license daemon The license manager daemon 1mgrd has detected that multiple vendor daemons for vendor are running Shutdown 1mgrd and all vendor daemons with the 1mdown utility and then restart 1mgrd
55. R jan The Options File Options File Syntax 5 2 14 MAX BORROW HOURS MAX BORROW HOURS feature keyword value num hours Changes the maximum period a license can be borrowed from that specified in the license certificate for feature The new period must be less than that in the license certificate If multiple MAX BORROW HOURS keywords appear in the options file only the last one is applied to feature feature Feature this borrow period applies to The license certificate for feature must have BORROW enabled keyword value Feature name modifier to denote a group of licenses See the section Feature Specification for details num hours Number of hours in the new borrow period This value must be less than that specified in the license certificate for feature the default if not specified is 168 hours 5 2 15 MAX OVERDRAFT MAX OVERDRAFT feature keyword value num lic Limits OVERDRAFT license usage below the OVERDRAFT allowed by the license file feature Feature this limit applies to keyword value Feature name modifier to denote a group of licenses See the section Feature Specification for details num lic Usage limit for this user or group 5 2 16 NOLOG NOLOG IN OUT DENIED QUEUED Suppresses logging the selected type of event in the debug log file FLEXIm End Users Guide July 2003 59 Options File Syntax Note To turn off logging of checkins NO
56. TLY The 1mborrow utility is a user interface to set LM BORROW in either the registry Windows or in SHOME flexlmrc UNIX LM BORROW can also be set directly as an environment variable today vendor all enddate time where today Today s date in dd mmm yyyy format Any checkouts done on this date create local borrow information If a checkout is done on a different date than this date no local borrowing information is created FLEXIm End Users Guide July 2003 103 License Borrowing with BORROW 8 4 2 104 vendor Vendor daemon that serves the licenses to be borrowed or all specifies all vendor daemons in the license server enddate Date the license is to be returned in dd mmm yyyy format time Optional time is specified in 24 hour format hh mm in the FLEX m licensed application s local time If time is unspecified the checkout lasts until the end of the given end date For example LM BORROW 15 aug 2001 sampled 20 aug 2001 13 00 In this example one or more licenses served by the sampled vendor daemon are borrowed on August 15 2001 and are scheduled to be returned at 1 pm on August 20 2001 Borrowing a License To borrow a license for a desired feature on the same day and the same machine that the end user runs 1mborrow or sets LM BORROW and while still connected to the network the end user runs the application to check out and borrow the license If the end user runs the application more
57. The standard filename extension for license files is Lic The number of vendor daemons is not limited by FLEX m Figure 3 3 illustrates this scenario oO E Imgrd E is E 2 D D E Vendor Vendor Vendor o o ABC DEF XYZ M Daemon Daemon Daemon 8 o 72 Swe Vendor ABC s Vendor DEF s Vendor XYZ s 2 2 2 License File License File License File Q o abc lic def lic xyz lic 630 Figure 3 3 One lmgrd Multiple License Files 32 Managing Licenses from Multiple Vendors 3 5 Managing Multiple License Files ADVANTAGES The license files can be maintained separately Reduced administrative overhead DISADVANTAGES e One Imgrd serves all vendor daemons If 1mgrd goes down all licensing is disabled Ifthe machine goes down all licensing is disabled Output from all vendor daemons goes into one common debug log unless separate debug logs are specified with DEBUGLOG in each vendor s options file Having one common debug log makes it harder to debug a single vendor daemon s problem e Maximizes licensing load to one machine and one 1mgrd process STARTING THE LICENSE SERVER Invoke the license manager daemon once on the server machine lmgrd c common license directory lmgrd processes all files with the lic extension in common license directory and starts all vendor daemons referred to
58. a FEATURE line node locked to a FLEXid and containing the FLOAT_OK keyword and a FLEXid for that FEATURE line One FEATURE line containing the FLOAT_OK keyword and one FLEXid is needed for each instance of a license that is mobile When the FLEXid is attached to a license server the license floats on the network When the FLEXid is removed from the license server the license is available only on the standalone computer This method supports parallel or USB FLEXids Because it is simpler to attach multiple USB dongles to a computer USB FLEXids may be preferable Initiating FLEXid with FLOAT OK A vendor issues the end user a FLEXid a FLEXid driver installer and a license file that contains a FEATURE line node locked to that FLEXid containing the FLOAT OK keyword An end user then 1 Installs the license file on the license server machine 2 Attaches all of the FLEXids to the license server machine 3 Installs the FLEXid driver on the license server machine 4 Starts the license server or rereads the license file While the FLEXids are attached to the license server machine the node locked licenses associated with them float on the network Each of the FLOAT OK uncounted node locked FEATURE lines has a count of one while it is available on the network Mobile Licensing 8 3 2 8 3 3 Node Locked to a FLEXid with FLOAT_OK Windows To transfer a license from the pool of floating licenses to a disconnected computer the end user
59. age is excluded group_name Name of the group to exclude To exclude the user hank from the list of users able to use feature f1 EXCLUDE f1 USER hank EXCLUDE_BORROW EXCLUDE BORROW feature keyword value type name group name Excludes a user or pre defined group of users etc from the list of who is allowed to borrow licenses for this BORROW feature EXCLUDE BORROW supersedes INCLUDE BORROW conflicts between the EXCLUDE BORROW list and the INCLUDE BORROW list are resolved by the EXCLUDE BORROW taking precedence feature Name of the feature being affected keyword value Feature name modifier to denote a group of licenses See the section Feature Specification for details The Options File 5 2 5 5 2 6 type name group_name Options File Syntax One of USER HOST DISPLAY INTERNET PROJECT GROUP or HOST_GROUP See the section Type Specification for details Name of an item of type t ype for which license borrowing is excluded Name of the group to exclude from borrowing To exclude the user fred from the list of users able to borrow feature f1 assuming the feature has the BORROW attribute EXC EXCLUDEALL UD EXC UD E BORROW f1 USER fred EALL type name group name Excludes a user or pre defined group of users etc from the list of who is allowed to use all features served by this vendor
60. amples The following information gives some examples of options files intended to illustrate ways to effectively control access to your licenses 5 5 1 Simple Options File Example RESERVE 1 compile USER robert RESERVE 3 compile HOST mainline EXCLUDE compile USER lori OLOG QUEUED FLEXIm End Users Guide July 2003 63 Options File Examples 5 5 2 64 This options file Reserves one license for the feature compile for the user robert Reserves three licenses for the feature compile for anyone on the system with the host name mainline Prevents the user lori from using the compile feature on any machine on the network Causes QUEUED messages to be omitted from the debug log file The sum total of the licenses reserved must be less than or equal to the number of licenses specified in the FEATURE line In the example above there must be a minimum of four licenses on the compile FEATURE line If fewer licenses are available only the first set of reservations up to the license limit is used If this data were in file a b sampled licenses sampled opt then modify the license file VENDOR line as follows VENDOR sampled etc sampled sample_app sampled licenses sampled opt Limiting Access for Multiple Users Each INCLUDE INCLUDEALL INCLUDE_BORROW EXCLUDE EXCLUDEALL EXCLUDE_BORROW MAX and RESERVE line must have a si
61. ariables Some utilities take more than one license file path in a license file list separated by colons on UNIX and semi colons on Windows Pathnames which include spaces have to be enclosed in double quotes help Displays usage information and exits v Displays the FLEX m version of the utility and exits verbose Displays longer description for all errors found FLEXLM VERSION NOTES VENDOR LICENSE FILE environment variable honored in utilities starting with v7 0 FLEXIm utilities verbose option introduced in v6 0 of the FLEXIm utilities T 3 Imborrow lmborrow supports borrowing of licenses that contain the BORROW attribute It must be run on the machine where licenses are borrowed It is used to perform the following FLEXIm End Users Guide July 2003 79 Imborrow 80 Initiating borrowing by setting the borrow period Clearing the borrow period Determining borrow status Returning a borrowed license early INITIATING BORROWING To initiate borrowing the user sets the borrow period by running 1mborrow from the command line or through LMTOOLS imborrow vendor all enddate time where vendor The vendor daemon name that serves the licenses to be borrowed or all specifies all vendor daemons in that license server enddate time Date the license is to be returned in dd mmm yyyy format t ime is optional and is specified in 24 hour format
62. ath If it s a different variable then if the environment set only that is used otherwise the registry is used That is the registry is only used if the environment is not set FLEXIm End Users Guide July 2003 133 Environment Variables D 2 Environment Variables Variable FLEXLM_BATCH FLEXLM DIAGNOSTICS FLEXLM TIMEOUT LM LICENSE FILE or VENDOR LICENSE FILE LM BORROW 134 Use FLEX m version introduced Windows only prevents interactive pop ups from appearing Set to 1 if a batch application Version 7 0 clients Used for debugging where applications don t print FLEX m error message text Set to 1 2 or 3 depending on the amount of diagnostic information desired See Section C 2 FLEXLM DIAGNOSTICS Version 5 04 clients Windows only Sets the timeout value a FLEX m licensed application uses when attempting to connect to a license server port in the range 27000 27009 Values are in microseconds within the range 0 through 2147483647 The default setting is 100000 microseconds Reset path to license file Can be a license file list separated by on UNIX and on Windows If VENDOR LICENSE FILE used VENDOR is the vendor daemon name used by this application For example Macrovision products use GSI LICENSE FILE Can be a file name or port host See also Section 2 1 1 Setting the Path with an Environment Variable VENDOR LI
63. ating options file 45 D DAEMON line 115 debug log file format 148 debugging license server 129 DEBUGLOG 51 decimal format licenses 87 DEMO hostid 109 deployed FLEXIm files FLEXid drivers 18 FLEXlock DLL 18 Imgr8b dll 18 Imgrd 18 Imtools exe 18 Imutil 18 vendor daemon 18 diagnosing checkout problems troubleshooting checkouts 83 disabling Imdown 68 Imremove 68 DISPLAY hostid 110 type 50 dist info 122 DUP GROUP 120 E enabling report log 60 environment variables FLEXLM BATCH 134 FLEXLM DIAGNOSTICS 134 FLEXLM TIMEOUT 134 LM BORROW 134 LM LICENSE FILE 134 LM PROJECT 135 setting 133 VENDOR LICENSE FILE 134 error code descriptions 138 format 137 EXCLUDE 52 FLEXIm End Users Guide July 2003 161 EXCLUDE_BORROW 52 EXCLUDEALL 53 expiration date 118 F feature version 118 FEATURE line 117 asset_info 122 dist_info 122 DUP_GROUP 120 expiration date 118 feature version 118 FLOAT_OK 120 HOST_BASED 121 HOSTID 120 ISSUED 121 ISSUER 121 license count 119 NOTICE 121 OVERDRAFT 121 PLATFORMS 121 serial number 121 SIGN 119 signature 119 SN 121 START 121 SUPERSEDE 122 syntax 123 TS_OK 122 USER_BASED 122 user_info 122 vendor daemon name 118 vendor_info 122 VENDOR_STRING 122 Feature line SUITE_DUP_GROUP 121 FLEXid with FLOAT_OK 100 flexid exe 18 flexidsilent exe 18 FLEXIm components 13 configuration 19 getting started checklist 20 installing client applications 20 FLEXIm Programmers Gu
64. ays status of all license files listed in SVENDOR LICENSE FILE or SLM LICENSE FILE on server Or on all servers if server is not specified FLEXIm End Users Guide July 2003 93 Imstat 94 9 E vendor Lists all users of vendor s features timeout_value Sets connection timeout to timeout_value This limits the amount of time 1mstat spends attempting to connect to server The output of 1mstat a looks similar to License server status 270008myhost1 License file s on myhost install dir flexlm v9 2 sun4 u5 counted lic myhost license server UP MASTER v9 2 Vendor daemon status on myhostl demo UP v9 2 Feature usage info Users of fl Total of 4 licenses issued Total of 1 license in use f1 v1 0 vendor demo floating license daniel myhost2 19 26 18 26 v1 0 myhost1 27000 102 start Fri 5 3 7 29 where daniel user User name myhost2 user host Host where user is running 19 26 18 26 display Display where user is running v1 0 version Version of feature myhost1 server_host Host where license server is running 27000 port TCP IP port on server_host where license server is running 102 handle License handle start Fri 5 3 checkout time Time that this license was checked 7 29 out License Administration Tools Note 7 13 Imswitch The users user host display server host port and handle information is used when removing licenses with 1mremo
65. can examine it The log file often contains useful information Examine it when you have a problem and be prepared to answer questions about it when you talk to a support person If the license server appears to have started correctly which you can determine from the log file try running 1mstat a and 1mdiag to see if that program has the same problem as your application If your application is FLEX m v4 1 or later v5 or later on Windows you can use the FLEXLM DIAGNOSTICS environment variable Set FLEXLM DIAGNOSTICS to 1 2 or 3 A setting of 3 gives more information than 2 2 gives more information than 1 in particular the feature name that was denied See Section C 2 FLEXLM DIAGNOSTICS for more information When you talk to a support person be prepared with answers to the following questions What kind of machine is your license server running on What version of the operating system What machine and operating system is the application running on What version of FLEX m does the FLEX m licensed application use Use the 1mver script or on UNIX execute the following command on your 1mgrd vendor daemon and application strings binary name grep Copy Alternatively lmgrd v gives the 1mgrd version and this works with the vendor daemon also FLEXIm End Users Guide July 2003 129 FLEXLM_DIAGNOSTICS C 2 Note C 2 1 C 2 2 130 What error or warning messages appear in the l
66. cation for details Name of an item of type t ype for which license borrowing is included Name of the group for which license borrowing is included To include user tom in the list of users able to borrow feature f1 INCLUDE BORROW f1 USER tom INCLUDEALL INCLUDEALL type name group name Includes a user or pre defined group of users etc in the list of who is allowed to use all features served by this vendor daemon Anyone not in an INCLUDEALL statement is not allowed to use these features type The Options File One of USER HOST DISPLAY INTERNET PROJECT GROUP or HOST GROUP See the section Type Specification for details 5 2 12 LINGER Note Options File Syntax name Name of an item of type t ype for which license usage is included group_name Name of the group to include To allow the user jane to use all features served by this vendor daemon INCLUDEALL USER jane LINGER feature keyword value seconds A lingering license stays checked out for a specified period of time beyond its checkin or licensed application exit whichever comes first This option extends the default linger time configured by the vendor in the licensed application The vendor must have added enabled this feature in the licensed application for it to work Contact your software vendor to find out if this feature is implemented feature Name of the feature keywo
67. cause with three server redundancy only one of the three servers is master capable of issuing licenses Since all clients must contact the master all clients must have reliable networking to a single machine Selecting Server Machines Counted vs Uncounted Licenses 4 3 3 Comparing Three Server to License File List 4 4 ARE THERE ANY DRAWBACKS TO USING THE LICENSE FILE LIST FOR REDUNDANCY Yes By default once a license job has successfully checked out a license from one host all subsequent checkouts must be satisfied from the same host If the application requires more than one license this could result in a license denial when the license is available on another server An application bypasses this restriction if it is coded with the use of multiple FLEXIm license jobs Only your application vendor knows if their application is programmed in this manner If the application supports license queueing all licenses are queued only from the first host on the list rather than the request moving to another server on the list Finally if one server becomes unavailable some licenses are unavailable WHEN IS IT RECOMMENDED TO USE A LICENSE FILE LIST FOR REDUNDANCY RATHER THAN THREE SERVER REDUNDANT SERVERS When there s less system administration available to monitor license servers e When load balancing is needed for FLEX m licensed applications located far apart e g London and Tokyo make servers avai
68. chines and vendor daemons and at least one line of data called FEATURE or INCREMENT lines for each licensed product Each FEATURE line contains a license key or signature based on the data in that line the hostids specified in the SERVER line s and other vendor specific data FLEX m licensed applications that are licensed with a node locked uncounted license need only read a valid license file to run they do not need a license server Most applications have an expected location for the license file documented by that application Override this location by setting the environment variable LM LICENSE FILE to point elsewhere or by following instructions supplied with the licensed application If your site has software from multiple vendors with incompatible license files due to different sets of servers keep the data in separate files and set the LM LICENSE FILE variable to reference multiple files It is recommended that you keep a link on UNIX a shortcut on Windows or copy of the license file in the vendor s expected license location so that users do not need to set LM LICENSE FILE to run their applications For license files containing counted floating licenses it is recommended to place a USE SERVER line directly after the SERVER line For details see Appendix B License File Format See also Appendix D FLEXIm Environment Variables THE FLEXLm LICENSED APPLICATION The
69. chr continues only until the vendor daemon is shut down or its options file is reread via 1mreread When the vendor daemon is restarted or its options file is reread it looks for a REPORTLOG line in the options file to determine whether or not to write report log output to a file and if so what file to write SEE ALSO Section 5 2 17 REPORTLOG e Section 7 8 Imnewlog e Section 7 11 lmreread Appendix F The Report Log File Imver The 1mver utility reports the FLEX m version of a library or binary file Usage is lmver filename where filename is one of the following the name of an executable file built with FLEX m imgrd alicense administration tool e a vendor daemon For example if you have an application called spell type lmver spell License Administration Tools LMTOOLS for Windows For the 32 bit Windows platforms a graphical user interface to the license manager tools is provided called LMTOOLS Always use the newest version of LMTOOLS as possible it is available for download from www macrovision com FLEXIm End Users Guide July 2003 97 License Administration Tools LMTOOLS for Windows Some of the functions LMTOOLS performs include starting stopping and configuring FLEX m license servers getting system information including hostids getting server status LMTOOLS has two modes in which to configure a license server Configuration using a license file Configuratio
70. configuring FLEX m Generally however installing FLEX m licensing requires the following steps 1 Select your license server machines and get their hostids See Chapter 4 Selecting Server Machines and Appendix A Hostids for FLEXIm Supported Machines 2 Give the hostids to your software vendor and get a license file or the data to enter in the license file in return 3 Consider how to manage license files from multiple vendors See Chapter 3 Managing Licenses from Multiple Vendors 4 Determine if an options file is desired and if so set it up 5 Determine where to install the FLEX m utility programs such as lmgrd and lmutil 1mstat 1mdown etc and install them unless your vendor s installation script does so for you 6 Start Lmgrd the license manager daemon manually you may also want to set it up to start automatically at boot time See Chapter 6 The License Manager Daemon These steps are discussed briefly below LICENSE SERVER MACHINE AND HOSTIDS Before running any FLEX m licensed application using floating licenses you first need to set up your license server machine or machines You must select which machine or machines to run your license servers on and provide the hostids of those machines to your software vendor For pointers on selecting your server machine see Chapter 4 Selecting Server Machines Introduction and Overview 1 6 2 Getting Started Checklist Get the ho
71. cription 88 System clock has been set back 89 This platform not authorized by license 90 Future license file format or misspelling in license file The file was issued for a later version of FLEX m than this program understands 91 ENCRYPTION SEEDS are non unique 02 Feature removed during Imreread or wrong SERVER line hostid 93 This feature is available in a different license pool This is a warning condition The server has pooled one or more INCREMENT lines into a single pool and the request was made on an INCREMENT line that has been pooled 94 Attempt to generate license with incompatible attributes 95 Network connect to this_host failed Change this_host on the SERVER line in the license file to the actual host name 96 Server machine is down or not responding See the system administrator about starting the server or make sure that you re referring to the right host see LM_LICENSE_FILE environment variable 97 The desired vendor daemon is down 1 Check the 1mgrd log file or 2 Try 1mreread 98 This FEATURE line can t be converted to decimal format 99 The decimal format license is typed incorrectly 100 Cannot remove a linger license FLEXIm Error Codes Error Code Descriptions Table 8 1 FLEXIm Error Codes Continued Error Code Description 101 All licenses are reserved for others The system administrator has reserved all the l
72. d license file feature by user UNSUPPORTED FEATURE request The user has requested a feature that this vendor daemon does not support This can happen for a number of reasons the license file is bad the feature has expired or the daemon is accessing the wrong license file Unknown host host The host name specified on a SERVER line in the license file does not exist in the network database probably etc hosts 152 The Debug Log File Debug Log Messages G2 3 Daemon Software Error Messages Message accept message Description An error was detected in the accept system call Can t allocate server table space A malloc error Check swap space Connection to host TIMED OUT The daemon could not connect to host Illegal connection request to vendor A connection request was made to vendor but this vendor daemon is not vendor read error message An error in a read system call was detected select message An error in a select system call was detected This is usually a sign of a system networking failure Server exiting The server is exiting This is normally due to an error FLEXIm End Users Guide July 2003 153 Debug Log Messages 154 The Debug Log File FLEX m Versions H 1 Version Compatibility and Components In general always use the latest Imgrd and lmutil LMTOOLS which are available from w
73. d introduced in v8 0 FLEXIm client library license manager daemon and vendor daemon All components must be v8 04 in order to use BORROW Node locked to a User Name If a license is to be used exclusively by one user on different machines that license can be node locked to the user s user name The license file is copied to the different machines on which the user might work the user s user name must be identical on each machine For this method to be useful individual user names in an organization need to be unique Fulfilled from a Prepaid License Pool In this method the end user buys a prepaid number of license days from the vendor The end user can then fulfill a license using a partial amount of the total license days for the given borrow period node locked to a particular machine For example in preparation for a business trip or even during a business trip the end user fulfills a license that expires in 5 days that is node locked to their laptop Each fulfillment can be node locked to a different machine or even multiple times to the same machine thus allowing mobility of license usage within the pre paid number of license days This model is like pay per use because each fulfillment is made from a decreasing number license days It is different than other pay per use models because once node locked to a machine that machine is allowed unlimited use of the application until the license expires This short term license canno
74. d license file 2 Invalid license file syntax 3 No server for this feature 4 Licensed number of users already reached 5 No such feature exists 6 No TCP IP port number in license file and FLEXIm service does not exist pre v6 only 7 No socket connection to license manager service 8 Invalid inconsistent license key or signature The license key signature and data for the feature do not match This usually happens when a license file has been altered FLEXIm Error Codes Error Code Descriptions Table 8 1 FLEXIm Error Codes Continued Error Code Description 9 Invalid host The hostid of this system does not match the hostid specified in the license file 10 Feature has expired 11 Invalid date format in license file 12 Invalid returned data from license server 13 No SERVER lines in license file 14 Cannot find SERVER host name in network database The lookup for the host name on the SERVER line in the license file failed This often happens when NIS or DNS or the hosts file is incorrect Workaround Use IP address e g 123 456 789 123 instead of host name 15 Cannot connect to license server The server 1mgrd has not been started yet or the wrong port host or license file is being used or the TCP IP port or host name in the license file has been changed 16 Cannot read data from license server 17 Cannot write data to license
75. daemon type name group name One of USER HOST DISPLAY INTERNET PROJECT GROUP or HOST GROUP See the section Type Specification for details Name of an item of type t ype for which license usage is excluded Name of the group to exclude To exclude any user on the machine chaos from using all features served by this vendor daemon EXC UD GROU GRO Defines P EALL HOST chaos UP group name user list a group of users for use in INCLUDE INCLUDEALL EXCLUDE EXCLUDEALL and RESERVE option lines group name Name of the group being defined Group names are case sensitive FLEXIm End Users Guide July 2003 53 Options File Syntax Note 5 2 7 5 2 8 54 user_list List of user names in that group Names are case sensitive Set the FLEXLM_GROUPCASEINSENSITIVE environment variable to turn on case insensitivity See Appendix D Environment Variables To define the group Hackers consisting of bob howard and james GROUP Hackers bob howard james Multiple GROUP lines for the same group name add all the specified users into the group USER_GROUP is an alias for GROUP GROUPCASEINSENSITIVE GROUPCASEINSENSITIVE OFF ON If set to ON user names and host names specified with the options file GROUP and HOST_GROUP keywords respectively are treated as case insensitive By default
76. daemons that have been added In addition all currently running vendor daemons are signaled to reread the license file and their end user options files for changes in feature licensing information or option settings If report logging is enabled any report log data still in the FLEXIm End Users Guide July 2003 91 Imreread Note vendor daemon s internal data buffer is flushed 1mreread recognizes changes to server machine host names but cannot be used to change server TCP IP port numbers If the optional vendor daemon name is specified only the named daemon rereads the license file and its end user options file in this case 1mgrd does not reread the license file Usage is lmreread c license file list vendor vendor all where c license file list Use the specified license file s vendor vendor Only this one vendor daemon rereads the license file 1mgrd restarts the vendor daemon if necessary all If more than one 1mgrd is specified instructs all 1mgras to reread To stop and restart a single vendor daemon use 1mdown vendor vendor then use Imreread vendor vendor which restarts the vendor daemon If you use the c 1icense file list option the license file s specified are read by 1mreread not by 1mgrd lmgrd rereads the file it read originally You can protect the unauthorized execution of 1mreread when you start up the license manager daemon 1mgrd SEE ALSO e Section 6 1 Imgrd Command Line S
77. e list as described in Section 3 5 Managing Multiple License Files Each 1mgrd starts the vendor daemon referred to in its license file s Managing Licenses from Multiple Vendors 3 3 One Machine with Multiple License Servers One Machine with Multiple License Servers In this model each vendor daemon and its associated license file or files is served by its own Imgrd process and everything is contained in one server machine Figure 3 2 depicts this scheme XE N ceo Imgrd 9 Imgrd 9 Imgrd E o o B D Vendor 9 Vendor Vendor o c e 2 ABC o DEF D XYZ c Daemon S Daemon S Daemon S E c o ts Vendor ABC s f Vendor DEF s F Vendor XYZ s f o License Files License Files License Files S Sees L o Bx 030 32 D a ane COSES g a Figure 3 2 Multiple Imgrds Multiple License Files When maintaining separate license servers on the same machine keep in mind Ifthe TCP IP port number is specified on the SERVER line it must be different for each license server Use a standard text editor to change the TCP IP port number in each license file so that they are all different If you are running 10 license servers or less you can omit all port numbers and 1mgrd will choose unique ones for you within the default range of 27000 27009 You must make s
78. ed licenses sampled opt The options keyword introduced in the v5 0 vendor daemon USE SERVER Line USE SERVER takes no arguments and has no impact on the server When the application sees USE SERVER it ignores everything in the license file except preceding SERVER lines and transfers checkout validation to the vendor daemon USE SERVER is recommended since it improves performance when a license server is used For uncounted features USE SERVER is used to force logging of usage by the daemons FEATURE INCREMENT Lines A FEATURE line describes the license required to use a product An INCREMENT line can be used in place of a FEATURE line as well as to incrementally add licenses to a prior FEATURE or INCREMENT line in the license file Only the first FEATURE line for a given feature is processed by the vendor daemon If you want to have additional copies of the same feature for example to have multiple node locked counted features then you must use multiple INCREMENT lines INCREMENT lines form license groups or pools based on the following fields feature name version FLEXIm End Users Guide July 2003 117 License File Syntax e DUP GROUP FLOAT OK HOST BASED HOSTID PLATFORM USER BASED VENDOR STRING if configured by the vendor as a pooling component If two lines differ by any of these fields a new group of licenses called a license pool is created in the vendor daemon and this group
79. eds 1mdiag indicates this If the checkout fails 1mdiag gives you the reason for the failure If the checkout fails because 1mdiag cannot connect to the license server then you have the option of running extended connection diagnostics These extended diagnostics attempt to connect to each TCP IP port on the license server machine and detects if the port number in the license file is incorrect Imdiag indicates each TCP IP port number that is listening and if FLEXIm End Users Guide July 2003 83 Imdown 7 5 84 it is an 1mgrd process 1mdiag indicates this as well If 1mdiag finds the vendor daemon for the feature being tested then it indicates the correct port number for the license file to correct the problem SEE ALSO Section C2 FLEXLM_ DIAGNOSTICS Imdown The 1mdown utility allows for the graceful shutdown of selected license daemons both 1mgrd and selected vendor daemons on all machines Usage is lmdown c license file list vendor vendor daemon q all force where c Use the specified license file s Note that license file list specifying c license file listis always recommended with 1mdown vendor Shut down only this vendor daemon vendor daemon lmgrd continues running Requires v6 0 1mdown and l1mgrd q Don t prompt or print a header Otherwise lmdown asks Are you sure y n all If multiple servers are specified automatically shuts down all of them q is implied with
80. ems that are frequently rebooted or shut down for one reason or another Redundant license server machines are any supported server machines FLEX m supports two methods of redundancy e viaa license file list in the LM LICENSE FILE environment variable viaa set of three redundant license servers With LM LICENSE FILE list redundancy each one of a group of license servers serves a subset of the total licenses The end user sets LM LICENSE FILE to a list of license files where each license file refers to one of the license servers The application then tries each server in the list in order until it succeeds or gets to the end of the list With three server redundancy if any two of the three license servers are up and running two out of three license servers is referred to as a quorum the system is functional and serves its total complement of licenses SEE ALSO Section 3 5 Managing Multiple License Files FLEXIm End Users Guide July 2003 41 Redundant License Servers 4 3 1 4 3 2 42 Redundancy via License File List This is best explained by example If ten licenses are desired for both f1 and f2 the vendor issues two sets of licenses with a count of 5 for each of f1 and f2 The server machines unlike three server redundancy can be physically distant The license files look like License 1 for chicago SERVER chicago 17007ea8
81. ending debug log path with the character appends logging entries Start 1mgrd by a user other than root since processes started by root can introduce security risks If 1mgrd must be started by the root user use the su command to run 1mgrd as a non privileged user su username c lmgrd c license file list 1 debug log path where username is a non privileged user You must ensure that the vendor daemons listed in the license file have execute permissions for username The paths to all the vendor daemons in the license file are listed on each VENDOR line Automatically On UNIX edit the appropriate boot script which may be etc rc boot etc rc local etc rc2 d Sxxx sbin rc2 d Sxxxx etc Include commands similar to the following See the notes following for a full explanation bin su daniel c echo starting lmgrd gt home flexlm v5 12 hp700 u9 boot log bin nohup bin su daniel c umask 022 home flexlm v5 12 hp700 u9 lmgrd c home flexlm v5 12 hp700 u9 license dat gt gt home flexlm v5 12 hp700 u9 boot log bin su daniel c echo sleep 5 gt gt home flexlm v5 12 hp700 u9 boot log s bin sleep 5 bin su daniel c echo lmdiag gt gt home flexlm v5 12 hp700 u9 boot log bin su daniel c home flexlm v5 12 hp700 u9 lmdiag n c home flexlm v5 12 hp700 u9 license dat gt gt home flexlm v5 12 hp700 u9 boot log SS bin su daniel c echo exi
82. er host name host Functionally equivalent to the ANY hostid it runs on any machine The difference is that the license is unique and is used to identify the customer This hostid is used to lock the license server on the SERVER line or the licensed application on the FEATURE INCREMENT line The number can have dashes included for readability the dashes are ignored Examples ID 12345678 is the same as ID 1234 5678 is the same as IDz1 2 3 4 5 6 7 8 Locks the software to an Internet IP address or group of IP addresses Wildcards are allowed For example 198 156 means any host with a matching internet IP address The main use is to limit usage access by subnet implying geographic area For this purpose it is used on the FEATURE INCREMENT line as a hostid lock Locks the software to user name user 110 Hostids for FLEXIm Supported Machines Special FLEXIm Hostids EXAMPLES FEATURE f1 demo 1 0 1 jan 2005 uncounted HOSTID FLEXID 6 a6300015f SIGN AB28E0011DA1 or FEATURE f1 demo 1 0 1 jan 2005 uncounted HOSTID INTERNET 10 10 10 SIGN EB78201163B0 FLEXIm End Users Guide July 2003 111 Special FLEXIm Hostids 112 Hostids for FLEXIm Supported Machines License File Format License files usually begin with a SERVER line or three lines for three server redundant servers followed by one or more VENDOR lines followed by one or more FEATURE or INCREMENT lines In
83. erved Licenses for details Licenses are not served by a license server but are available directly to the application This is commonly referred to as an uncounted or unserved license model See Section 1 3 2 Unserved Licenses for details 1 3 1 Served Licenses For served licenses there are four required FLEX m components The FLEXIm Licensed Application with the FLEX m static client library linked into it The License Manager Daemon Imgrd The Vendor Daemon which along with the license manager 1mgrd comprises the license server The License File FLEXIm End Users Guide July 2003 13 FLEXIm Components 1 3 2 14 In addition to these four components there are three optional components Debug Log File created and written by 1mgrd Report Log File created and written by the vendor daemon for use by SAMreport End User Administration Options File file created and maintained by the end user Figure 1 1 shows the relationship these components have to one another See Section 1 3 3 Component Overview for a description of each component FLEX m License Server Components Licensed Application DE 70 License Server Debug FLEXIm _ Pi Log TCP IP License Manager i File zT Port D aho Administration Vendor zc Options l Daemon i EET y File V4 M Tu rr N Report License Aj Log File s i Ti Your Application Code FLEX m Client Library
84. es An example of a license file that provides floating licenses is SERVER lulu 17007ea8 VENDOR sampled FEATURE f1 sampled 1 00 1 jan 2005 2 SIGN signaturel F F EATURE f2 sampled 1 00 1 jan 2005 6 SIGN signature2 EATURE 3 sampled 1 00 1 jan 2005 1 SIGN signature3 This license file specifies that two licenses for feature f1 six licenses for feature f2 and one license for feature f3 are available anywhere on the network that can access the license server lulu 1mgrd uses one of the default FLEX m ports Node Locked Licenses Node locking means the licensed software can only be used on one machine or a set of machines A node locked license has a hostid on any FEATURE line that is node locked to a particular host There are two types of node locked licenses uncounted and counted If the number of licenses is set to 0 or uncounted then the license is uncounted and unlimited use is permitted on the specified machine This configuration does not require an 1mgrd or a vendor daemon because it is not going to count the concurrent usage of the features The following license file allows unlimited usage of feature f1 on the machines with hostids of 17007ea8 and 1700ab12 FEATURE f1 sampled 1 000 1 jan 2005 uncounted SIGN signaturel Y HOSTID 17007ea8 FEATURE f1 sampled 1 000 1 jan 2005 uncounted SIGN signature2 N HOSTID 1700ab12 Alternately t
85. es are borrowed 121 FLOAT_OK license must have exactly one dongle hostid 122 Unable to delete local borrow info 123 Support for returning a borrowed license early is not enabled The vendor must have enabled support for this feature in the vendor daemon Contact the vendor for further details 124 An error occurred while returning a borrowed license to the server 125 Attempt to checkout just a PACKAGE Need to also checkout a feature 126 Error initializing a composite hostid 127 A hostid needed for the composite hostid is missing or invalid 128 Error borrowed license doesn t match any known server license Indicates errors due to an operating system failure FLEXIm Error Codes The Report Log File The license server produces both report log files and debug log files The focus of this appendix is report log files For information on debug log files see Appendix G The Debug Log File The report log file contains feature usage information and is generated by the vendor daemon However a vendor daemon does not write report log output by default Report log output is not human readable and is only used by the SAMreport and FLEXbill products Therefore unless you are using either of these two Macrovision products or intend to use them in the future there is no reason to enable report logging F 1 Managing Report Log Output As a vendor daemon runs for a period of time the volume of report l
86. es in the application grant or deny usage based solely upon the contents of the license file Configuring FLEX m Most of the parameters of FLEX m are configurable by the license administrator The license administrator can set the Location of the license file though it s recommended that a copy or link of the license remains at the location where the application expects it Location of all executables Location of all log files TCP IP port number used by the license manager process 1mgrd In addition the license administrator can reserve licenses for specific users machines or groups and control other license related options Changing parameters is discussed in Chapter 5 The Options File Refer to your vendor s documentation before attempting to change file names locations or contents FLEXIm End Users Guide July 2003 19 Getting Started Checklist 1 6 1 6 1 20 Getting Started Checklist The following sections provide a quick overview of how to set up and use licensing for FLEX m licensed products Installing Licensed Software As a license administrator you are responsible for setting up licensing on your system or network This section tells you how to do that If you are an end user of the application and you are not involved in installing it then go to Section 1 6 2 Notes for End Users Remember that the installation guide for your application software is the final word on installing and
87. files are located To finish entering type q on a line by itself or enter two blank lines When an input file is specified with no output file specified output goes to stdout if neither input nor output file is specified 1minstall assumes that input comes from stdin and prompts the user for an output file name l1minstall is also used to convert licenses from readable to decimal format and between different versions of FLEX m license formats To convert from readable to decimal lminstall i in l1ic file o out lic file odecimal To convert to FLEX m v5 1 format lminstall i in l1ic file o out lic file overfmt 5 1 To enforce a maximum line length of for example 50 characters FLEXIm End Users Guide July 2003 87 Imnewlog 7 8 7 9 88 lminstall maxlen 50 Conversion errors are reported as necessary and can be written to a file by specifying e err file lminstall has a limit of 1000 lines of input Imnewlog The 1mnew1og utility switches the report log file by moving the existing report log information to a new file then starting a new report log with the original report log file name If you rotate report logs with 1mnewlog instead of lmswitchr you do not have to change the file name in the REPORTLOG line of the vendor s options file Requires a v7 1 vendor daemon Usage is lmnewlog c license file list feature renamed report log Or lmnewlog c license f
88. hese two FEATURE lines could have been issued by your software vendor with a hostid list FEATURE f1 sampled 1 000 1 jan 2005 uncounted SIGN signature HOSTID 17007ea8 1700ab12 If these were the only FEATURE lines in this license file no 1mgrd daemon is necessary and you do not need to start one FLEXIm End Users Guide July 2003 27 Types of License Files 2 3 3 28 The following license file provides three licenses for feature f1 locked to the machine with hostid 1300ab43 Since the license server and licenses are locked to the same machine the daemons run on the same machine that runs the licensed application SERVER lulu 1300ab43 1700 VENDOR sampled etc sampled FEATURE f1 sampled 1 00 1 jan 2005 3 SIGN signature HOSTID 1300ab43 Mixed Node Locked and Floating Licenses Uncounted node locked and concurrent usage licenses can be mixed in the same license file The following license file allows unlimited use of feature f1 on machines 17007ea8 and 1700ab12 while allowing two other licenses for feature f1 to be used anywhere else on the network SERVER lulu 17001234 1700 VENDOR sampled C flexlm sampled exe FEATURE f1 sampled 1 00 1 jan 2005 uncounted SIGN signaturel V HOSTID 17007ea8 FEATURE f1 sampled 1 00 1 jan 2005 uncounted SIGN signature2 HOSTID 1700ab12 FEATURE f1 sampled 1 00 1 jan 2005 2 SIGN signature3
89. hh mm in the FLEX m licensed application s local time If time is unspecified the checkout lasts until the end of the given end date For example lmborrow sampled 20 aug 2001 13 00 This has the effect of setting LM BORROW with the borrow period in either the registry Windows or in HOME flexlmrc UNIX To borrow licenses for the desired vendor on the same day and the same machine that the user runs 1mborrow run the application s to check out the license s If you run the application s more than once that day no duplicate licenses are borrowed No licenses are borrowed if the application is run on a day different than the date borrowing is initiated In addition to the 1mborrow utility there are other ways to initiate borrowing Using the borrowing interface in application if provided in the application e Setting the LM BORROW environment variable directly License Administration Tools Imborrow See Section 8 4 1 Initiating License Borrowing for more information on these other ways CLEARING THE BORROWED LICENSE SETTING To clear the LM BORROW setting in the registry or SHOME flexlmrc issue the command lmborrow clear Clearing the LM BORROW setting stops licenses from being borrowed until borrowing is initiated again A user might run 1mborrow clear after he has borrowed licenses for features that are used offline if before disconnecting from the network he wants to run an applica
90. host if the license file SERVER line uses a default TCP IP port or specifies a port in the default port range 27000 27009 Applications accept an environment variable or Windows Registry named VENDOR_LIC ENS E FILE where VENDOR is the vendor daemon name e g ENS GSI_LIC E FILI those applications from vendor VENDOR E This environment variable s scope is limited to just With 1mgrd and 1mutil 1mstat lmdown etc the c option overrides the setting of the LM LICENSE FILE environment variable Note Some applications do not recognize the LM LICENS variable FLEX m enabled Java applications in particular do not recognize it SEE ALSO E FIL E environment Section 3 5 Managing Multiple License Files for more information about LM LICENSE FILE e Appendix D FLEXIm Environment Variables FLEXLM VERSION NOTES e Default TCP IP port number range introduced in v6 0 of Imgrd License file location dialog introduced in v6 0 of the FLEXIm client library FLEXIm End Users Guide July 2003 25 License File Format Overview 2 2 2 3 26 License File Format Overview License files usually begin with a SERVER line or three lines for three server redundant servers followed by one or more VENDOR lines followed by one or more FEATURE or INCREMENT lines In some cases the license file requires no SERVER line and no V
91. icenses for others Reservations are made in the options file The server must be restarted for options file changes to take effect 102 A FLEXid borrow error occurred 103 Terminal Server remote client not allowed 104 Cannot borrow that long 106 License server out of network connections The vendor daemon can t handle any more users See the debug log for further information 110 Dongle not attached or can t read dongle Either the hardware dongle is unattached or the necessary software driver for this dongle type is not installed 112 Missing dongle driver In order to read the dongle hostid the correct driver must be installed These drivers are available at www macrovision com or from your software vendor 113 Two FLEXlock checkouts attempted Only one checkout is allowed with FLEX ock enabled applications 114 SIGN keyword required but missing from license This is probably because the license is older than the application You need to obtain a SIGN version of this license from your vendor 115 Error in Public Key package 116 CRO not supported for this platform 117 BORROW failed 118 BORROW period has expired FLEXIm End Users Guide July 2003 143 Error Code Descriptions 144 Table 8 1 FLEXIm Error Codes Continued Error Code Description 119 Imdown and Imreread must be run on license server machine 120 Cannot Imdown the server when licens
92. ide x FLEXIm Reference Manual x FLEXLM BATCH 134 FLEXLM DIAGNOSTICS 130 level 1 130 level 2 130 level 3 131 FLEXLM_TIMEOUT 134 FLOAT_OK 120 floating license 27 G GROUP type 53 GROUPCASEINSENSITIVE 54 H HOST type 49 host SERVER line 114 HOST_BASED 121 HOST_GROUP type 54 HOSTID 120 hostid ANY 109 COMPOSITE 109 DEMO 109 DISPLAY 110 HOSTNAME 110 ID 110 INTERNET 110 SERVER line 114 special 109 table by platform 108 USER 110 HOSTNAME hostid 110 162 FLEXIm End Users Guide July 2003 I ID hostid 110 INCLUDE 55 INCLUDE_BORROW 56 INCLUDEALL 56 INCREMENT line 117 installing client applications 20 INTERNET hostid 110 type 50 ISSUED 121 ISSUER 121 L license borrowing 102 concurrent 27 floating 27 mixed 28 mobile 99 network license 27 node locked 27 license count 119 license directory 69 71 license file compatibility between different versions 37 DAEMON line 115 decimal format 127 expected location 16 FEATURE line 117 format 26 how to combine 35 INCREMENT line 117 LM LICENSE FILE 16 Iminstall 87 order of lines 28 128 overview 16 PACKAGE line 124 rereading after an update 91 SERVER lines 37 specifying location 23 types 26 UPGRADE line 127 USE SERVER line 117 VENDOR line 115 with multiple servers 69 license manager daemon 15 67 license pool 48 118 license rehosting 99 license request process 19 license server debugging 129 deciding number of nodes 41 disk space used 40 insta
93. ile list vendor renamed report log where c license file list Use the specified license file s feature Any feature in this license file vendor Vendor daemon in this license file renamed report log New file path where existing report log information is to be moved Impath The 1mpath utility allows direct control over FLEX m license path settings It is used to add to override or get the current license path settings Usage is Impath add override vendor all license file list License Administration Tools Impath where add Prepends 2icense file list to the current license file list or creates the license file list 1f it doesn t exist initializing it to license file list Duplicates are discarded override Overrides the existing license file list with license file list If license file list is the null string the specified list is deleted lmpath override all Deletes the value of LM LICENSE FILE lmpath override vendor Deletes the value of VENDOR LICENSE FILE vendor A vendor daemon name Effects the value of VENDOR LICENSE FILE Borat Refers to all vendor daemons Effects the value of LM LICENSE FILE license file list A colon separated list on UNIX and a semi colon separated list on Windows If license file list is the null string then the specified entry is deleted Note 1mpath works by setting the FLEX m registry entry on Windows or SHOME flexlmrc on UNIX
94. in the v7 1 FLEXIm client library and vendor daemon For v7 1 through v8 0 FLEXIm client libraries and vendor daemons the FEATURE INCREMENT line must have a SIGN signature and for backward compatibility with pre v8 1 can contain a license key FEATURE INCREMENT feature vendor feat version exp date num lic license key SIGN sign optional attributes license key obsoleted in v8 1 FLEXIm client library and vendor daemon The keyword permanent for exp date introduced in v6 FLEX m client library The keyword uncounted for num 1ic introduced in v6 FLEXIm client library BORROW keyword introduced in v8 0 FLEX m client library and vendor daemon FLOAT OK keyword introduced in v8 0 FLEXIm client library and vendor daemon TS OK keyword introduced in v8 0 FLEX m client library and vendor daemon FLEXIm End Users Guide July 2003 123 License File Syntax B 1 6 PACKAGE Lines The purpose of the PACKAGE line is to support two different licensing needs To license a product SUITE or To provide a more efficient way of distributing a license file that has a large number of features which largely share the same FEATURE line arguments A PACKAGE line by itself does not license anything it requires a matching FEATURE INCREMENT line to license the whole package A PACKAGE line is shipped by your software vendor with a product independent of any licenses Later when you purchase
95. iring licenses available When compl or comp is checked out suite is also checked out PACKAGE suite sampled 1 0 SIGN 2CBF44FCB9C1 COMPONENTS apple 1 5 2 orange 3 0 4 FEATURE suite sampled 1 0 1 jan 2005 3 SIGN 321E78A17EC1 SN 123 In this example the component version overrides the feature version and the number of licenses available for any component is the product of the three licenses for suite and the number of licenses for that component The result is equivalent to FEATURE cl sampled 1 5 1 jan 2005 6 SIGN 0D3AD5F26BEC SN 123 FEATURE c2 sampled 3 0 1 jan 2005 12 SIGN EB16C5AE61F0 SN 123 FLEXLM VERSION NOTES 126 Ability to store PACKAGE lines in separate files introduced in v6 FLEXIm client library e pkg version field required in pre v7 1 FLEXIm client library License File Format Decimal Format B 1 7 UPGRADE Lines Note B 2 UPGRADE feature vendor from_feat_version to_feat_version exp_date num_lic options SIGN sign All the data is the same as for a FEATURE or INCREMENT line with the addition of the from_feat_version field An UPGRADE line removes up to the number of licenses specified from any old version gt from_feat_version and creates a new version with that same number of licenses For example the two lines INCREMENT f1 sampled 1 000 1 jan 2005 5 SIGN 9BFAC0316462 UPGRADE f1 sampled 1 000 2 000
96. is counted independently from other license pools with the same feature name A FEATURE line does not give an additional number of licenses whereas an INCREMENT line always gives an additional number of licenses The basic FEATURE INCREMENT line format is FEATURE INCREMENT feature vendor feat version exp date num lic SIGN sign optional attributes The six fields after the FEATURE INCREMENT line keyword are required and have a fixed order They are defined by the vendor and cannot be changed Table B 1 presents these fields in the order they must appear Table B 1 FEATURE INCREMENT Line Required Fields Field Description feature Name given to the feature by the vendor vendor Name of the vendor daemon also found in the VENDOR line The specified daemon serves this feature feat version Version of this feature that is supported by this license exp date Expiration date of license in the format dd mrm y y y y e g 07 may 2005 Note If exp date is the string permanent or the year is O or 00 000 0000 then the license never expires 118 License File Format License File Syntax Table B 1 FEATURE INCREMENT Line Required Fields Continued Field Description num lic Number of concurrent licenses for this feature If the num 1icis set to the string uncounted or 0 the licenses for this feature are uncounted and no 1mgrd is required but a hostid on the FEATURE
97. is daemon was run on an invalid host name host Wrong hostid exiting The hostid is wrong for host BAD CODE for feature The specified feature name has a bad license key or signature It was probably typed in wrong or modified by the end user CANNOT OPEN options file file The options file specified in the license file could not be opened Couldn t find a master The daemons could not agree on a master FLEXIm End Users Guide July 2003 151 Debug Log Messages Message License daemon lost all connections Description This message is logged when all the connections to a server are lost which often indicates a network problem Lost lock exiting Error closing lock file Unable to re open lock file The vendor daemon has a problem with its lock file usually because of an attempt to run more than one copy of the daemon on a single node Locate the other daemon that is running via a ps command and kill it with kill 9 No DAEMON line for vendor The license file does not contain a DAEMON or VENDOR line for vendor No DAEMON lines exiting The license daemon logs this message 1f there are no DAEMON or VENDOR lines in the license file Because there are no vendor daemons to start there is nothing for the license daemon to do No features to serve A vendor daemon found no features to serve This could be caused by a corrupted or incorrectly entere
98. ks for the vendor daemon binary in e the current directory the path specified in 1mgrd s PATH environment variable inthe directory where 1mgrd is located If vendor daemon path is blank then any options or TCP IP port number specifications require the opt ions and port strings options file Full path to the end user options file for this path daemon FLEX m does not require an options file If omitted the vendor daemon by default looks for a file called vendor opt where vendor is the vendor daemon name located in the same directory as the license file port Vendor daemon TCP IP port number The default if port is not specified is chosen by the operating system at run time Sites with Internet firewalls need to specify the TCP IP port number the daemon uses If a TCP IP port number is specified on the VENDOR line there may be a delay restarting the vendor daemon until all the clients have closed their connections to the vendor daemon SEE ALSO Chapter 5 The Options File for further information regarding options file contents License File Format B 1 4 License File Syntax FLEXLM VERSION NOTES vendor daemon pathrequired in pre v6 0 vendor daemon e options file path required in pre v6 0 vendor daemon VENDOR lines are known as DAEMON lines in the pre v6 0 1mgrd and vendor daemon v6 04 VENDOR sampled pre v6 0 DAEMON sampled etc sampled etc sampl
99. lable locally with remote servers available as backup License file list is more forgiving if you lose quorum License file list is not limited to three servers any number work Clients do not require reliable networking to a single machine with license file list so this is recommended where networking itself requires redundancy Counted vs Uncounted Licenses The license file determines whether a license server is needed If all the FEATURE or INCREMENT lines have a license count of 0 unlimited or uncounted then no server is needed This type of license is called uncounted Alternatively if any FEATURE lines have a non zero license count then a server is required to count those licenses If a vendor wants to use FLEX m without a server they must issue uncounted licenses The license server is able to serve uncounted licenses as well This is done so that transactions can be logged into the report log for all license requests which can then be reported on by SAMreport FLEXIm End Users Guide July 2003 43 Counted vs Uncounted Licenses options file constraints can be applied to the licenses To have uncounted licenses served include a SERVER line in the license file and put the USE SERVER line immediately after the SERVER line The vendor daemon serves the uncounted licenses and the USE SERVER line indicates to applications that requests must go to the license server for authorization FLEXL
100. line is required See Section 4 4 Counted vs Uncounted Licenses SIGN sign SIGN signature to authenticate this FEATURE line Table B 2 lists attributes that may appear in a FEATURE or INCREMENT line They are supplied at the discretion of the vendor to provide particular licensing behavior If present in the FEATURE or INCREMENT line they must remain there and cannot be altered by the end user These attributes have a keyword value syntax where keyword is in uppercase In places where value is a string surrounded with double quotes the string can contain any characters except a quote Table B 2 Vendor Supplied Attributes Attribute Description BORROW 7n Enables license borrowing for a particular FEATURE INCREMENT line n is the number of hours that the license is borrowed The default borrow period is 168 hours or one week FLEXIm End Users Guide July 2003 119 License File Syntax 120 Table B 2 Vendor Supplied Attributes Continued Attribute DUP_GROUP Description The syntax is DUP_GROUP NONE SITE UHDV U DUP_USER H DUP_HOST D DUP_DISPLAY V DUP_VENDOR_DEF Any combination of UHDV is allowed and the DUP_MASK is the OR of the combination For example DUP_GROUP UHD means the duplicate grouping is DUP USERIDUP HOSTIDUP DISPLAY so for a user on the same host and display additional uses of a feature do not consume additional license
101. ll lmgrds Support registry Windows and HOME flexlmrc UNIX for FLEX m environment variables Automatically install license path in registry or HOME flexlmrc after successful checkout Options support for LM PROJECT with PROJECT Performance improvements especially for Windows NT Intel Pentium III CPU ID v7 0d November 1999 Aucusr 2000 Security enhancements SIGNz keyword in license l1mnewlog utility v7 1 vendor daemon v7 2 DECEMBER 2000 Performance enhancements v8 0 OCTOBER 2001 lmborrow v8 0 components 1mpath v8 04 vendor daemon l1mswitch v8 04 vendor daemon utilities lmreread rereads end user options file and SERVER host name License borrowing with BORROW keyword v8 1 JANUARY 2002 CRO Security enhancements v8 2 Aucusr 2002 Support added for Windows XP compliancy v8 3 OCTOBER 2002 Support added for returning borrowed licenses early v8 4 JANUARY 2003 Support for reserved package suites v9 0 MARCH 2003 Support for COMPOSITE hostid type FLEXIm End Users Guide July 2003 159 Version Summary v9 2 JULY 2003 Options file keywords added GROUPCASEINSENSITIVE and MAX BORROW HOURS 160 FLEXIm Versions Index A about this manual ix ANY hostid 109 asset_info 122 B BORROW_LOWWATER 50 borrowing 102 C commands x COMPOSITE hostid 109 concurrent license 27 configuring FLEXIm files 19 conventions X converting license formats 87 cre
102. ll as Windows service 98 sockets used 39 license file list 33 license file list redundancy 42 LINGER 57 LM BORROW 134 LM LICENSE FILE 134 to reference multiple files 16 LM PROJECT 135 reporting on project 60 use in options file 50 Imdiag syntax 83 troubleshooting 83 Imdown disabling 68 restricting access 68 syntax 84 Imgrd and redundant servers 69 compatibility between versions 67 debug log file 148 memory usage 40 overview 15 67 shutting down 84 FLEXIm End Users Guide July 2003 163 starting 67 69 starting automatically at boot time 21 starting debug log 68 syntax 67 use latest 155 Imhostid syntax 85 Imhostid syntax 85 Iminstall license file format 87 syntax 87 Imnewlog syntax 88 Imremove disabling 68 restricting access 68 syntax 90 Imreread restricting access 68 syntax 91 Imstat output for Imreread 93 syntax 93 Imswitch syntax 95 Imswitchr syntax 96 LMTOOLS 18 97 Imutil Imdiag 83 Imdown 84 Imhostid 85 Iminstall 87 Imnewlog 88 Imremove 90 Imreread 91 Imstat 93 Imswitch 95 Imswitchr 96 Imver 97 Imver syntax 97 M MAX 58 MAX BORROW HOURS 59 MAX OVERDRAFT 59 memory usage daemons 40 mixed licenses 28 mobile licensing borrowing 102 FLEXid with FLOAT OK 100 node locked to FLEXid 99 node locked to laptop 99 node locked to user name 106 prepaid license pool fulfillment 106 N network bandwidth and FLEXIm 40 network license 27 node locked license 27 NOLOG 59 NOTICE 121
103. log output to new debug 10g The effect of 1mswitch continues only until the vendor daemon is shut down or its options file is reread via 1mreread When the vendor daemon is restarted or its options file is reread it looks for a DEBUGLOG line in the options file to determine whether or not to write its debug log output into its own file and if so what file to write SEE ALSO e Section 5 22 DEBUGLOG e Section 7 11 lmreread Appendix G The Debug Log File Imswitchr The 1mswitchr utility switches the report log file by closing the existing report log and starting a new report log with a new file name It also starts a new report log file if one does not already exist Usage is lmswitchr c license file list feature new report log or with v5 0 vendor daemon lmswitchr c license file list vendor new report log where c license file list Use the specified license file s feature Any feature in this license file vendor Vendor daemon in this license file new report log Path to new report log file License Administration Tools Note 7 15 7 16 Imver If report logging is not enabled for the vendor daemon 1mswitchr tells it to start writing its report log output to new report 1log lfreport logging is already enabled for the vendor daemon 1mswitchr tells the vendor daemon to close its report log file and start writing its new report log output to new report log The effect of Lmswit
104. low checkouts from a terminal server TS OK keyword in the feature line the USER HOST and DISPLAY names can be different from one another The types listed above take a single member For example EXCLUDE coolsoft USER joe To specify a list of users or hosts first define the list using the GROUP or HOST GROUP option lines then use the GROUP or HOST GROUP type to specify the group name For example GROUP stars joe barbara susan EXCLUDE coolsoft GROUP stars FLEXLM VERSION NOTES e IP address as a HOST specification introduced in v8 vendor daemon LM PROJECT environment variable introduced in V5 FLEXIm client library and vendor daemon e Colons in feature names introduced in v8 vendor daemon BORROW LOWWATER BORROW LOWWATER feature keyword value n Sets the number of licenses for a BORROW feature that cannot be borrowed feature Name of feature being affected The Options File 5 2 2 Options File Syntax keyword value Feature name modifier to denote a group of licenses See the section Feature Specification for details n Number of licenses that cannot be borrowed via license borrowing For example if a feature f1 has a count of 10 and borrowing is enabled in the application and on the FEATURE line FEATURE fl 10 BORROW SIGN the following line in the options file allows only 7 licenses to be borrowed BORROW LOWWATER f1 3 DE
105. ltiple vendors into one file initially and over time STARTING THE LICENSE SERVER Invoke the license manager daemon once on the server machine lmgrd c combined license fil CRITERIA FOR COMBINING LICENSE FILES Your product s license file s define the license server s by host name and hostid in the SERVER line s in the license file License files are candidates for combining under the following conditions The number of SERVER lines in each file is the same The hostid field of each SERVER line in one file exactly matches the hostid field of each SERVER line in the other file Some possible reasons license files may not be compatible are FLEXIm End Users Guide July 2003 35 Additional Considerations License files are set up to run on different server machines so hostids are different e One file is set up for single server has only one SERVER line the other is set up for a three server redundant license server has multiple SERVER lines Hostids for the same machine use different hostid types For example the SERVER line in one license file uses INTERNET for its hostid type and the other file uses the ethernet MAC address for its hostid type If your license files are compatible as described above then you have the option of combining license files as summarized in Figure 3 4 and below in How to Combine License Files Note that you are not required to combine compatible license files There is n
106. m implementation details consult your vendor for this information The number of sockets available to the license server is defined by the per process system limit for file descriptors The total number of sockets used by the license server is slightly larger than the total number needed by the FLEX m enabled applications which are served by it When using UDP there is no limit to the number of applications per license server because they can share a single socket from the server If the number of sockets required by the license server on a single machine becomes excessive then it s probably good to split the license file into more than one file onto different servers to lighten the networking traffic which requires the vendor to agree to issue new licenses Licensed applications then check out licenses from multiple servers using a license file list via the LM LICENSE FILE environment variable 4 1 2 CPU Time For small numbers of clients the license servers use very little CPU time The servers might have only a few seconds of CPU time after many days FLEXIm End Users Guide July 2003 39 Resources Used by the Server 40 For a large number of clients who are each exchanging heartbeat messages with the server or for high checkout checkin activity levels hundreds per second the amount of CPU time consumed by the server may start to become significant although even here CPU usage is normally not high In this case y
107. mgrd and each vendor daemon v Displays 1mgrd version number and copyright and exits help Displays usage information and exits Starting the License Manager Daemon on UNIX Platforms If any licenses in the license file are counted license count gt 0 the license manager daemon and hence the license server must be started before the FLEXIm licensed application can be used The license manager daemon Imgrd is started either manually on the command line or automatically at system startup Both methods are discussed in the following sections Start 1mgrd only on the server node specified on the SERVER line in the license file If you are running three server redundant license servers maintain a separate copy of the license file as well as the 1mgrd and the vendor daemons binaries on each server node If you do not do this you lose all the advantages of having redundant servers since the file server holding these files becomes a single point of failure Manually Start 1mgrd from the UNIX command line using the following syntax lmgrd c license file list L debug log path where e license file list is one or more of the following the full path to a single license file a directory where all files named 1ic in that directory are used FLEXIm End Users Guide July 2003 69 Starting the License Manager Daemon on UNIX Platforms 6 2 2 70 e debug log path is the full path to the debug log file Prep
108. n order for Imgrd and hence the license server to start up automatically at system start up time you first must configure it as a license manager service Follow the procedure in Section 6 3 2 Configuring the License Manager as a Windows Service before proceeding Then continue 74 The License Manager Daemon Starting the License Manager Daemon on Windows 1 With LMTOOLS started and the desired service name selected click the Config Services tab LMTOOLS by Macrovision Corporation http www macrovision com File Edit Mode Help Service License File System Settings Utilities Start Stop Reread Server Status Server Diags Config Services Borrowing Save Service Configure Service Service Name Myvendor License Manager X Browse Path to the Imgrd exe file EflesimVmard exe eose Path to the license file JC Mflexim myvendor lic Browse Path to the debug log fie C VlesimNmaid d Browse View Log Elsa Los v Start Server at Power Up IV Use Services Step 3 a Step 2 2 Make this license manager a Windows service check the Use Services check box otherwise it becomes a FLEXIm service 3 Configure it to start at system startup time by checking the Start Server at Power Up check box From now on when the machine is rebooted this license manager starts automatically as a Windows service FLEXIm End Users Guide July 2003 75 Starting the License Manager Daemon on Windows 7
109. n using services 7 16 1 Configuration Using License File Operations are performed on a particular license file The file can be either local or remote In this mode you cannot start the 1mgrd process but you can do everything else To configure this mode perform the following 1 Invoke LMTOOLS 2 Click the Configuration using License File radio button 3 Enter one or more the license file names or port host specifications 7 16 2 Configuration Using Services Operations are performed on a service which allows starting 1mgrd processes local to the system on which LMTOOLS is running For details on configuring services see Section 6 3 2 Configuring the License Manager as a Windows Service 98 License Administration Tools Mobile Licensing End users often want to use applications on computers that do not have a continuous connection to a FLEX m license server These situations include Working on a laptop Using a computer both at work and at home Working from several different computers not connected to a license server FLEX m supports licenses that allow one of several kinds of mobile licensing Node locked to a laptop Node locked to a FLEXid Windows only Node locked to a FLEXid with FLOAT_OK keyword Windows only License borrowing with BORROW keyword Node locked to a user name Fulfilled from a prepaid license pool License rehosting is the consequence of an end user wanting to move a license without usi
110. nclude those described in Section 3 2 Multiple Machines Section 3 3 One Machine with Multiple License Servers or Section 3 4 One Machine with One License Server and Multiple License Files SEE ALSO Section 2 1 1 Setting the Path with an Environment Variable Section 4 3 1 Redundancy via License File List e Appendix D FLEXIm Environment Variables Additional Considerations Combining license files If you have two or more products whose licenses are intended for the same machine as specified by their SERVER lines you may be able to combine the license files into a single license file The license files for the models described in Section 3 3 One Machine with Multiple License Servers and Section 3 4 Managing Licenses from Multiple Vendors Additional Considerations One Machine with One License Server and Multiple License Files could be combined if they met certain criteria Figure 3 4 shows one possible scenario using a combined license file Imgrd D 5 Vendor Vendor Vendor op ABC DEF XYZ D 2 Daemon Daemon Daemon Q amp n C BET o sr o 2 Combined P License File 2 D E oO Figure 3 4 One lmgrd One License File ADVANTAGES Asingle license file to administer Low administrative overhead DISADVANTAGE tis complicated to decide how to combine license lines from mu
111. nfiguration Using Services 0000005 98 Chapter 8 Mobile Licensing 2 222 ener oce ed eere pits dee je 99 8 1 Node Locked to a Laptop Computer 99 8 2 Node locked to a FLEXid Windows Only 99 FLEXIm End Users Guide July 2003 V 8 3 Node Locked to a FLEXid with FLOAT OK Windows Only 100 8 3 1 Initiating FLEXid with FLOAT OK 100 8 3 2 Returning a FLEXid with FLOAT OK License 101 8 3 3 FLEXid with FLOAT OK Example 101 8 4 License Borrowing with BORROW 4 102 8 4 1 Initiating License Borrowing 20065 103 8 4 2 Borrowing a License 0 0 0 eee eee 104 8 4 3 Support for License Borrowing 0020 00s 105 8 5 Node locked to a User Name 0 0 00 000s ee 106 8 6 Fulfilled from a Prepaid License Pool 106 Appendix A Hostids for FLEX m Supported Machines 107 AT Hostid Formats poU eeDUeni suene erimus 107 A 2 Expected FLEX m Hostids elleeeeeee 108 A 3 Special FLEX m Hostids 0 0 0 eee eee eee 109 Appendix B License File Format 113 B 1 License File Syntax 0 0 eee eee 114 B 1 1 Sample License File 0 0 0 0 0005 114 B 12 SERVER LINES Rede REY hee ee une 114 B 1 3 VENDOR Eines ced sebo EES kee Ra mrt 115 B 1 4 USE SERVER Line 00 0 eee eee eee 117 B 1 5 F
112. ng one of these methods This means a new node locked license file is generated by the vendor for each new client computer Rehosting incurs administrative overhead because the vendor is involved for each move 8 1 Node Locked to a Laptop Computer If a license is to be used exclusively on one laptop computer that license is simply node locked to an address associated with that computer The license file resides on the laptop computer 8 2 Node locked to a FLEXid Windows Only If a license is to be moved between different Windows machines it is node locked to a FLEXid a dongle that connects to a parallel or USB port This license is moved between machines by installing a copy of the license file on FLEXIm End Users Guide July 2003 99 Node Locked to a FLEXid with FLOAT_OK Windows Only 8 3 8 3 1 100 each machine and moving the FLEXid from one machine to another Since the license is tied to the FLEXid only the machine with the FLEXid has use of the license Node Locked to a FLEX d with FLOAT_OK Windows Only This method of license mobility has an advantage over simply using a license node locked to a FLEXid because the FLEXid is attached to a license server machine and its license floats on the network Licenses with a FLOAT_OK keyword that are node locked to a FLEXid are supported only where both the FLEX m licensed application and the license server are running on Windows A vendor issues a license file with
113. ngle user name or group listed To affect more than one user name create a GROUP For example to exclude bob howard and james from using the feature called toothbrush create the following options file EXCLUDE toothbrush USER bob EXCLUDE toothbrush USER howard EXCLUDE toothbrush USER james However there is an easier way Create a GROUP and exclude the list of users from using the feature Like the previous example the following options file excludes bob howard and james from using the feature called toothbrush First define the group Hackers GROUP Hackers bob howard james Then exclude the group EXCLUDE toothbrush GROUP Hackers Now when you want to allow or deny access to any feature to that group you have an alias list to make it simple The Options File 5 5 3 5 5 4 Options File Examples Use HOST_GROUP to allow deny or reserve licenses for multiple hosts For example to exclude all users logged in on the hosts fred and barney from using a feature called f1 add these lines to your options file HOST_GROUP writers fred barney EXCLUDE f1 HOST GROUP writers SEE ALSO e Section 5 2 8 HOST GROUP for more information about defining groups EXCLUDE Example First Define the group painters GROUP painters picasso mondrian klee EXCLUDE spell GROUP painters EXCLUDE spell USER bob EXCLUDE
114. notices OVERDRAFT n The overdraft policy allows your vendor to specify a number of additional licenses which users are allowed to use in addition to the licenses they have purchased This allows your users to not be denied service when in a temporary overdraft state Usage above the license limit is reported by the SAMreport reporting tool PLATFORMS Usage is limited to the listed platforms SN serial_num Serial number used to identify FEATURE or INCREMENT lines START dd mmm yyyy Start date SUITE_DUP_GROUP Similar to DUP_GROUP but affects only the enabling FEATURE line for a package suite It limits the total number of users of the package to the number of licenses and allows the package to be shared among the users that have the SUITE checked out FLEXIm End Users Guide July 2003 121 License File Syntax Table B 2 Vendor Supplied Attributes Continued Attribute Description SUPERSEDE If this appears all licenses issued before the UBL VEEL Guest date specified in ISSUED are superseded by this line and become ineffective TS OK FLEX m detects when a node locked uncounted license is running under Windows Terminal Server To run on Terminal Server remote machines TS OK must be added to the FEATURE line Without TS OK a user running on a Terminal Server client is denied a license USER BASED n User
115. nt exe Required if vendor supports FLEXid dongle hostids flexid exe is used to install FLEXid drivers for use with FLEXid dongles Alternatively the vendor may supply flexidsilent exe to silently install the drivers as part of the software installation Introduction and Overview 1 4 1 5 Note The License Request Process The License Request Process When you run a counted FLEX m licensed application the following occurs 1 The license module in the FLEX m licensed application finds the license file which includes the host name of the license server machine and TCP IP port number of the license manager daemon 1mgrd 2 The FLEX m licensed application establishes a connection with the license manager daemon 1mgrad and tells it what vendor daemon it needs to talk to 3 1mgrd determines which machine and TCP IP port correspond to the master vendor daemon and sends that information back to the FLEX m licensed application 4 The FLEX m licensed application establishes a connection with the specified vendor daemon and sends its request for a license 5 The vendor daemon checks in its memory to see if any licenses are available and sends a grant or denial back to the FLEX m licensed application 6 The license module in the application grants or denies use of the feature as appropriate Uncounted features where the license count is 0 do not require a license server and the FLEX m client library routin
116. o performance or system load penalty for not combining the files 36 Managing Licenses from Multiple Vendors Additional Considerations How TO COMBINE LICENSE FILES If your license files are compatible use any text editor to combine them To combine license files read all of the compatible license files into one file then edit out the extra SERVER lines so that only one set of SERVER lines remains Save the resulting data and you have your combined license file Figure 3 5 shows an example of combining license files Vendor ABC s License File SERVER alpha 17007ea8 VENDOR ABC Combined License File INCREMENT f1 ABC INCREMENT f2 ABC SERVER alpha 17007ea8 VENDOR ABC Men VENDOR DEF Vendor DEF s License File VENDOR XYZ SERVER alpha 17007ea8 INCREMENT f1 ABC VENDOR DEF INCREMENT f2 ABC INCREMENT f3 DEF INCREMENT f3 DEF INCREMENT f4 DEF INCREMENT f4 DEF INCREMENT f5 XYZ Vendor XYZ s License Flle INCREMENT ARE SERVER alpha 17007ea8 VENDOR XYZ INCREMENT f5 XYZ INCREMENT f6 XYZ Vendor GHI s License File SERVER tao 13004dfa This license file cannot be combined VENDOR GHI with the ones above because INCREMENT f5 GHI its server is different INCREMENT f6 GHI Vendor JKL s License File SERVER alpha INTERNET 10 10 10 This license file cannot be combined with the ones above for VENDORJKL server alpha because INCRE
117. ock synchronization is required between the license server machine and the machine running the FLEX m licensed application Mobile Licensing 8 4 1 License Borrowing with BORROW Initiating License Borrowing If a vendor has enabled license borrowing by issuing a license file that contains a FEATURE line with the BORROW keyword an end user initiates license borrowing in one of three ways Using the borrowing interface in application if provided in the application e Running the 1mborrow utility to set LM BORROW e Setting the LM BORROW environment variable directly APPLICATION INTERFACE The user initiates license borrowing this way only if the application provides a borrowing interface Information about this is supplied by the vendor RUNNING THE LMBORROW UTILITY lmborrow is one ofthe 1mut i LMTOOLS utilities To initiate borrowing the user runs 1mborrow from the command line or through LMTOOLS lmborrow vendor all enddate time where vendor is the vendor daemon that serves the licenses to be borrowed or all specifies all vendor daemons in the license server enddate is the date the license is to be returned in dd mmm yy yy format t ime is optional and is specified in 24 hour format hh mm in the FLEX m licensed application s local time If t ime is unspecified the checkout lasts until the end of the given end date For example lmborrow sampled 20 aug 2001 13 00 SETTING THE LM BORROW ENVIRONMENT VARIABLE DIREC
118. og file Did the server start correctly Look for a message such as server xyz started for featurel feature2 What is the output from running 1mstat a Are you running other products which are also licensed by FLEX m Are you using a combined license file or separate license files Are you using a three server redundant license server multiple SERVER lines in your license file FLEXLM DIAGNOSTICS The ability for FLEX m to produce diagnostic output is controlled by your software vendor FLEXLM DIAGNOSTICS is an environment variable that causes the application to produce diagnostic information when a checkout is denied The format of the diagnostic information may change over time On UNIX the diagnostic output goes to stderr On Windows the output is a file in the current directory called flexpid log where pidis the application s process ID Level 1 Content If FLEXLM DIAGNOSTICS is set to 1 then the standard FLEX m error message is be presented plus a complete list of license files that the application tried to use For example setenv FLEXLM DIAGNOSTICS 1 FLEXl1m checkout error Cannot find license file 1 73 2 No such file or directory license file s usr myproduct licenses testing lic license lic Level 2 Content If FLEXLM DIAGNOSTICS is set to 2 then in addition to level 1 output the checkout arguments are presented For example Setenv FLEXLM DIAGNOSTICS 2 FLEX1m checkout error
119. og output increases If you have a lot of license activity these log files grow very large You need to consider where to put these files and how often to rotate and archive them Therefore it may be necessary to rotate or switch report log output into different files over time each file containing license activity over a particular period of time Report log data is collected by the vendor daemon into an internal data buffer area before being flushed to the output file The daemon s internal buffer is flushed once a minute or whenever it gets full whichever occurs first To ensure the freshest data possible in the report log file flush the buffer on demand with the 1mreread command Use standard file compression tools to reduce the size of a report log file when it is no longer being written To avoid corruption and for performance it is suggested that the vendor daemon write its report log to a file on a disk local to the system running the vendor daemon Each vendor daemon must write to its own report log file FLEXIm End Users Guide July 2003 145 Enabling Report Log Output for a Vendor Daemon F2 Enabling Report Log Output for a Vendor Daemon There are two ways to enable report logging for a particular vendor daemon either before or after starting the license server e Add the REPORTLOG line to the options file for that vendor daemon See Section 5 2 17 REPORTLOG for more details e Invoke 1mswitchr on the vendor daemon
120. on for details type One of USER HOST DISPLAY INTERNET PROJECT GROUP or HOST GROUP See the section Type Specification for details name Name of an item of type t ype for which license usage is included group name Name of the group for which license usage is included To include user bob in the list of users able to use feature f1 INCLUDE f1 USER bob INCLUDE is required for USER BASED or HOST BASED features The system administrator specifies which users are allowed to use the product via INCLUDE and the license limits the number of users that are INCLUDEd FLEXIm End Users Guide July 2003 55 Options File Syntax 5 2 10 INCLUDE BORROW 5 2 11 56 INCLUDE BORROW feature keyword value type name group name Includes a user or pre defined group of users etc in the list of who is allowed to borrow the BORROW feature Anyone not in an INCLUDE BORROW statement is not allowed to borrow licenses EXCLUDE BORROW supersedes INCLUDE BORROW conflicts between the EXCLUDE BORROW list and the INCLUDE BORROW list are resolved by the EXCLUDE BORROW taking precedence feature keyword value type name group name Name of the feature being affected Feature name modifier to denote a group of licenses See the section Feature Specification for details One of USER HOST DISPLAY INTERNET PROJECT GROUP or HOST GROUP See the section Type Specifi
121. on the VENDOR line for the application s vendor daemon For example VENDOR sampled etc sampled options sample_app sampled licenses sampled opt enables the sampled vendor daemon to look at the specified options file If the path is omitted the vendor daemon automatically looks for a file according to the following criteria the name of the file is vendor opt where vendor is the vendor daemon name e it is placed it in the same directory as the license used by 1mgrd it is automatically used at server startup FLEXLM VERSION NOTES e The default options file name vendor opt introduced in v6 vendor daemon 5 2 Options File Syntax Below is an overview of the options file syntax See Section 5 5 Options File Examples for examples and additional information Each line of the file controls one option Table 5 1 lists the option keywords Table 5 1 Option Keywords Option Keyword Description BORROW LOWWATER Set the number of BORROW licenses that cannot be borrowed DEBUGLOG Writes debug log information for this vendor daemon to the specified file v8 0 vendor daemon EXCLUDE Deny a user access to a feature 46 The Options File Options File Syntax Table 5 1 Option Keywords Continued Option Keyword Description EXCLUDE_BORROW Deny a user the ability to borrow BORROW licenses EXCLUDEALL Deny a user access to all fea
122. optional a short sentence 80 characters explaining the system error Other supporting information optional Error messages were improved in v6 FLEX m Error Explanation and supporting information are only available in applications using v6 04 These error messages may occurin two formats available with FLEX m or may appear in a format customized by the application E 1 1 Format 1 short FLEXlm error text 1m errno minor num sys errno sys error text The system error information may be missing Example Can t connect to license server 15 12 61 Connection refused FLEXIm End Users Guide July 2003 137 Error Code Descriptions E 1 2 Format 2 long version 6 0 E 2 138 FLEXl1lm error text FLEXlm error explanation Optional Supporting information FLEXlm error l1m errno minor num System Error sys errno system error text Example Cannot connect to license server The server lmgrd has not been started yet or the wrong port host or license file is being used or the port or hostname in the license file has been changed Feature f1 Server name localhost License path localhost license dat lic FLEX1m error 15 12 System Error 61 Connection refused Error Code Descriptions The following table lists the most common errors produced by FLEX m licensed products Table 8 1 FLEXIm Error Codes Error Code Description 1 Cannot fin
123. ort numbers If no TCP IP port number is specified one of the default ports in the range of 27000 and 27009 is used Example SERVER my_server 17007ea8 21987 SEE ALSO Section B 1 5 FEATURE INCREMENT Lines for more information about uncounted features Chapter 4 Selecting Server Machines for more information about redundant servers FLEXLM VERSION NOTES IP address specification for host introduced in v5 0 1mgrd vendor daemon and FLEX m client library port specification is required with a pre v6 0 1mgrd vendor daemon and FLEX m client library VENDOR Lines The VENDOR line specifies the daemon name and path 1mgrd uses this line to start the vendor daemon and the vendor daemon reads it to find its options file The format of the VENDOR line is shown below VENDOR vendor vendor daemon path N options options file path port port where Field Description vendor Name of the vendor daemon used to serve some feature s in the file This name cannot be changed by the administrator FLEXIm End Users Guide July 2003 115 License File Syntax 116 Field Description vendor_daemon Optional path to the executable for this daemon _path Generally the license administrator is free to install the daemon in any directory It is recommended however that it be installed in a local directory on the license server machine If omitted 1mgrd loo
124. otepad that can display UTF 8 encoded strings FLEXIm End Users Guide July 2003 107 Expected FLEXIm Hostids The following table lists alternate methods to obtain the required hostid for each machine architecture FLEX m also supports a group of special hostids and vendor defined hostids Hardware Hostid Type this command on Example Platform the license server AIX 32 bit hostid uname m returns 02765131 RS 6000 000276513100 then PPC remove last two digits and use remaining last eight digits DEC Alpha ethernet netstat i 080020005532 address HP 32 bit hostid uname i and convert 778DA450 or 32 bit and to hex or prepend with 2005771344 64 bit platforms non Itanium HP machine getconf ID_STRING 9c76631 64 bit identification CS PARTITION 9 db72 d411 af62 Itanium IDENT then prefix with O060b05e4c05 ID_STRING Linux ethernet sbin ifconfig 00400516E525 address etho and remove colons from HWaddr 00 40 05 16 E5 25 SCO Hostid String uname x Serial is ID STRING SCO00354 SCO00354 then prefix with ID_STRING SGI 32 bit hostid etc sysinfo s 69064C3C or convert to hex or prefix 1762020412 SUN 32 bit hostid hostid 170a3472 108 Hostids for FLEXIm Supported Machines Special FLEXIm Hostids Hardware Hostid Type this command on Example Platform the license server Windows ethernet lmutil lmhostid 00B0A9DF9A32 address Disk serial DIR C look for DIS
125. oth users and license administrators Users make more efficient use of fewer licenses by sharing them on the network License administrators control who uses the licensed application and the machine s where the licenses are available See Section 2 3 Types of License Files for details about the different licensing models supported by FLEX m 1 2 Howto Use This Manual This manual is written for two different audiences Administrators of FLEX m licenses and license servers End users of FLEX m enabled applications 1 2 1 License Administrator If you are a license administrator read these chapters Chapter Explains Preface Overview of this manual FLEXIm End Users Guide July 2003 11 How to Use This Manual Chapter Chapter 1 Introduction and Overview Chapter 2 License File Basics Chapter 3 Managing Licenses from Multiple Vendors Chapter 4 Selecting Server Machines Chapter 5 The Options File Chapter 6 The License Manager Daemon Chapter 7 License Administration Tools Chapter 8 Mobile Licensing In addition refer to Explains FLEX m basics license manager and vendor daemons the license file configuring FLEX m the license request process License file basics setting the path at start up different types of licensing policies Using license files from multiple software vendors Selecting which machines run the license servers resources required b
126. ou may need to ensure that the server machine you select has enough CPU cycles to spare Disk Space The only output files created by the license servers are the debug and report log files The report log files are used to generate accurate usage reports by SAMreport If you have a lot of license activity these log files grow very large You need to consider where to put these files and how often to rotate and archive them The license administrator has the option to suppress log file output if disk space is at a premium It is recommended that the log files are local files on the server machine s to avoid networking dependencies SEE ALSO Section 2 1 1 Setting the Path with an Environment Variable Section 6 2 Starting the License Manager Daemon on UNIX Platforms Appendix F The Report Log File Appendix G The Debug Log File Memory The FLEX m daemons use little memory On SunOS 1mgrd uses approximately2 MB and the vendor daemons use approximately 2 MB each although memory usage increases in the vendor daemon with the size of the license file size of the options file and the number of concurrent users Network Bandwidth FLEX m sends relatively small amounts of data across the network Each transaction such as a checkout or checkin is typically satisfied with less than 1 KB of data transferred This means that FLEX m licensing can be effectively run over slow networks such as dial up SLIP lines for small n
127. rd value Feature name modifier to denote a group of licenses See the section Feature Specification for details seconds Number of seconds the license lingers The vendor sets a minimum value If you specify a value for seconds that is smaller than the vendor s minimum the minimum is used To set the linger value for feature f1 to one hour 3600 seconds LINGER f1 3600 The actual linger time varies somewhat since the vendor daemon checks all lingering licenses just once per minute If however a new license request is made that would otherwise be denied a check of the lingering licenses is made immediately to attempt to satisfy the new request FLEXIm End Users Guide July 2003 57 Options File Syntax 5 2 13 MAX MAX num_lic feature keyword value type name group_name 58 Limits usage for a group or user num_lic feature keyword value type name group_name Usage limit for this user or group Feature this limit applies to Feature name modifier to denote a group of licenses See the section Feature Specification for details One of USER HOST DISPLAY INTERNET PROJECT GROUP or HOST_GROUP See the section Type Specification for details Name of an item of type type for which usage is limited Name of the group to limit For example to limit the user jan to 5 licenses for feature 1 include the following line in the option file MAX 5 f1 USE
128. report log to a new file name lmver Reports the FLEX m version of a library or binary file FLEXLM VERSION NOTES The 1 The 1 The The 1 mpath utility introduced in the v7 0 FLEXIm utilities mborrow utility introduced in the v8 0 FLEXIm utilities lmswitch utility introduced in v8 0 vendor daemon mswitchr utility introduced in v8 0 vendor daemon 7 4 Running Administration Tools All FLEXIm utilities are packaged as a single executable called 1mutil lmutil is either installed as individual commands either by creating links to the individual command names or making copies of 1mut i1 as the individual command names or as a wrapper that runs the individual command as lmutil command For example lmutil lmstat or lmutil lmdown On Windows systems the 1mutil command form of the commands are available There is also a graphical user interface available for these commands see Section 7 16 License Administration Tools LMTOOLS for Windows 78 License Administration Tools Universal Imutil Arguments 7 2 Universal Imutil Arguments The following are valid arguments for most 1mut i1 utilities c license file path Most lmutil utilities need to know the path to the license file This is specified with a c license file path argument or by setting the LM LICENSE FILE environment variable Otherwise the default location is used The utilities also honor all VENDOR_LICENSE_FILE environment v
129. rrect FEATURESET line in license file 56 Cannot compute FEATURESET data from license file 140 FLEXIm Error Codes Error Code Descriptions Table 8 1 FLEXIm Error Codes Continued Error Code Description 57 socket call failed 59 Message checksum failure 60 Server message checksum failure 61 Cannot read license file data from server 62 Network software TCP IP not available 63 You are not a license administrator 64 Imremove request before the minimum Imremove interval 67 No licenses to borrow 68 License BORROW support not enabled 69 FLOAT_OK can t run standalone on SERVER 71 Invalid TZ environment variable 73 Local checkout filter rejected request 74 Attempt to read beyond end of license file path 5 SYS SETIMR call failed VMS 76 Internal FLEXIm error please report to Macrovision 77 Bad version number must be floating point number with no letters 82 Invalid PACKAGE line in license file 83 FLEXIm version of client newer than server 84 USER_BASED license has no specified users see server log 85 License server doesn t support this request 87 Checkout exceeds MAX specified in options file FLEXIm End Users Guide July 2003 141 Error Code Descriptions 142 Table 8 1 FLEXIm Error Codes Continued Error Code Des
130. rt of the standard FLEX m distribution kit Macrovision Corporation also provides the SAMsuite and SAMreport asset management tools for more advanced license server control and reporting SAMwrap is another Macrovision product that allows end users to provide FLEX m license management for applications without embedded FLEX m license management Please contact Macrovision Corporation by email at info globes com or on the Internet at www macrovision com for more information about SAMsuite SAMreport or SAMwrap Keep in mind that certain topics such as password encryption are vendor specific and proprietary so they are not documented in any detail Also because FLEX m does not enforce a particular licensing strategy each vendor s implementation has subtle differences If you do not find out what you need to know here contact your vendor s technical support group Versions of FLEX m This manual covers features of interest to license administrators and end users in FLEX m versions 5 0 through 9 2 The text presents FLEX m v9 2 behavior and functionality Differing behavior and functionality if any between the current and past versions for a particular feature is noted at the end of the its section Additionally Appendix H FLEXIm Versions covers version differences in detail FLEXIm End Users Guide July 2003 ix Related Documents from Macrovision Related Documents from Macrovision The SAMsuite Users Guide describes the SAMs
131. ry for you to separate old debug log output from current output either archive or delete the old output For performance it is suggested that each debug log file be a on disk that is local to the machine that is running 1mgrd and its vendor daemons However if the debug log file must be on a remotely mounted disk and you find that the license server is too slow start 1mgrd with the nfs_log option to improve performance See Section G2 Debug Log Messages for a description of the debug log output format G1 1 Capturing Debug Log Output for a License Server By default 1mgrd and the vendor daemons it manages write debug log output to standard out To put this debug log output in a file either redirect the output of the license server to a file or start 1mgrd with the 1 debug log path option FLEXIm End Users Guide July 2003 147 Debug Log Messages G1 2 G1 3 G1 4 G2 148 Capturing Debug Log Output for a Particular Vendor Daemon The debug log output from different vendor daemons controlled by the same license server can be written to their own files v8 0 vendor daemon There are two ways to do this e Add the DEBUGLOG line to the options file for each vendor daemon See Section 5 2 2 DEBUGLOG for more details e Invoke 1mswitch on the vendor daemon See Section 7 13 Imswitch for more details Note that 1mgrd writes its own debug log output to standard out Redirecting Debug Log Output for a
132. ry support 1ic automatically used License files require no editing for use at the end user site Optional path on DAEMON VENDOR line PATH environment variable used Decimal license format with 1minstall utility for typing in licenses FEATURE lines are shorter easier to understand and type in PACKAGE lines can be shipped in separate files that never require user editing Default TCP IP port numbers make SERVER line port number optional Default end user options file path this host host name supported on SERVER line VENDOR LICENSE FILE supported e g GST LICENSE FILE host supported where default port numbers are used Windows only user prompted for license file or license server name License files are optionally case insensitive lmdown and lmreread accept vendor vendor argument START dd mmm y yyy optional license attribute V6 1 JUNE 1998 Performance improvements v7 0 Aucusr 1999 License Certificate Manager support for automatic license fulfillment Support for try before you buy licensing License file handles inserted newlines from emailers License lines automatically optimally sorted Improved LMTOOLS interface for Windows FLEXIm Versions Version Summary lmgrd when run at command line on Windows runs in background by default Improved three server redundancy reliability v7 0 vendor daemon and 1mgrd lmreread and 1mdown take a11 argument to shut down or reread a
133. s FLOAT OK server_hostid Enables mobile licensing via FLEXid with FLOAT_OK for a particular FEATURE INCREMENT line This FEATURE INCREMENT line must also be node locked to a FLEXid When FLOAT OK server hostidis specified on a FEATURE line The server hostid mustrefer to the same host that appears on the SERVER line of the license file The license server runs only on the machine with the hostid that lmhostid returns equal to the server hostid specified with FLOAT OK HOSTID hostidl hostid2 hostidn Id of the host to which the feature line is bound hostid is determined with the lmhostid utility This field is required for uncounted licenses but can be used for counted licenses as well See Appendix A Hostids for FLEXIm Supported Machines for more information License File Format License File Syntax Table B 2 Vendor Supplied Attributes Continued Attribute HOST_BASED n Description Host names must be specified in INCLUDE statements in the end user options file and the number of hosts is limited to num_lic or the number specified in n ISSUED dd mmm yyyy Date issued ISSUER Issuer of the license LINGER n The vendor defined lingering interval for this license Use LINGER in the options file to extend this time See Section 5 2 12 LINGER for more information NOTICE A field for intellectual property
134. s LMTOOLS by Macrovision Corporation http www macrovision com File Edit Mode Help Service License File System Settings Utilities Statt Stop Reread Server Status Server Diags Config Services Borrowing Save Service Configure Service Service Name Myvendor License Manager Remove Service il Browse Path to the Imgrd exe file C flexim Imgrd exe IM Path to the license file C MlexlmNmyvendar lic Browse Path to the debug log fle C MleximNImgrd di View Log Use Services Start Server at Power Up 7 To save the new Myvendor License Manager service click the Save Service button 6 3 3 Manually from LMTOOLS A graphical user interface to the license manager tools is provided called LMTOOLS Some of the functions LMTOOLS performs include 72 The License Manager Daemon Starting the License Manager Daemon on Windows starting stopping and configuring FLEX m license servers getting system information including hostids getting server status In order to control the operation of 1mgrd from the LMTOOLS user interface you first must configure it as a license manager service Follow the procedure in Section 6 3 2 Configuring the License Manager as a Windows Service before proceeding Once the license manager service is configured Imgrd is started by starting the service from the LMTOOLS interface 1 Start LMTOOLS LMTOOLS by Macrovision Corporation http
135. s must be specified in INCLUDE statements in the end user options file and the number of users are limited to num 1ic or the number specified in n VENDOR STRING Vendor defined string enclosed in double Maaa quotes The following attributes listed in Table B 3 are optional and are under control of the end user These attributes have a keyword value syntax where keyword is in lowercase Table B 3 End User Attributes Attribute Description asset_info Additional information provided by the license reist administrator for asset management dist info Additional information provided by the software Nuus distributor user info Additional information provided by the license Neu administrator vendor info Additional information provided by the software exse vendor 122 License File Format License File Syntax Examples B EATURE sample app sampled 2 300 31 dec 2005 20 SIGN 123456789012 INCREMENT f1 sampled 1 000 permanent 5 HOSTID INTERNET 195 186 NOTICE Licensed to Sample corp SIGN 901234567890 FLEXLM VERSION NOTES Pre v7 1 FEATURE INCREMENT line format uses 212cense key FEATURE INCREMENT feature vendor feat version exp date num lic license key optional atributes The pre v7 1 format is understood by the current FLEXIm client library and vendor daemon The SIGN keyword introduced
136. s the option to all of the components in the package TYPE SPECIFICATION The following option keywords restrict who may use licenses or where licenses may be used EXCLUDE EXCLUDEALL EXCLUDE BORROW INCLUDE INCLUDEALL INCLUDE BORROW MAX and RESERVE These options take a t ype argument which specifies whether the restriction is based on USER HOST DISPLAY INTERNET or PROJECT e USER user name of the user executing the FLEX m licensed application User names are case sensitive HOST machine host name or IP address where the application is executing Host names are case sensitive The IP address can contain wildcard characters FLEXIm End Users Guide July 2003 49 Options File Syntax 5 2 1 50 DISPLAY display where the application is displayed On UNIX DISPLAY is dev ttyxx which is always dev tty when an application is run in the background or the X Display name On Windows it is the system name or in the case of a terminal server environment the terminal server client name Display names are case sensitive INTERNET IP address of the machine where the application is executing wildcard characters can be used in the IP address e PROJECT LM PROJECT environment variable set by the user who is executing the FLEX m licensed application Project names are case sensitive On Windows without terminal server the HOST and DISPLAY names are both set to the Window s system name For licenses that al
137. se file above allows the license server my server with the hostid 17007ea8 to serve ten floating licenses for each feature f1 and f2 to any user on the network SERVER Lines The SERVER line specifies the host name and hostid of the license server and the TCP IP port number of the license manager daemon 1mgrd Normally a license file has one SERVER line Three SERVER lines mean that you are using a three server redundant license server The absence of a SERVER line means that every FEATURE and INCREMENT line in the license file is uncounted The hostids from the SERVER lines are computed into the license key or signature on every FEATURE and INCREMENT line For this reason make sure you keep SERVER lines together with any FEATURE INCREMENT lines as they were sent from the vendor The format of the SERVER line is SERVER host hostid port where Field Description host The system host name or IP address String returned by the UNIX hostname or uname n command On NT 2000 XP ipconfig all on Windows 95 98 ME winipcfg all return the host name hostid Usually the string returned by the 1mhostid command This is changed only by your software supplier License File Format License File Syntax Field Description port TCP IP port number to use A valid number is any unused port number between 0 and 64000 On UNIX choose a port gt 1024 since those lt 1024 are privileged p
138. sed application for it to work Contact your software vendor to find out if this feature is implemented feature Name of the feature keyword value Feature name modifier to denote a group of licenses See the section Feature Specification for details seconds Number of seconds after which inactive license is reclaimed The vendor sets a minimum value If you specify a value for seconds that is smaller than the vendor s minimum the minimum is used To set the timeout for feature f1 to one hour 3600 seconds TIMEOUT f1 3600 TIMEOUT checks in the licenses if the FLEX m licensed application has been inactive for a period longer than the specified time period The daemon declares a process inactive when it has not received heartbeats from it whereas an active FLEX m licensed application sends heartbeats A TIMEOUT line must be present in the options file in order to take advantage of the vendor enabled timeout feature 5 2 20 TIMEOUTALL 5 3 62 TIMEOUTALL seconds Same as TIMEOUT but applies to all features How the Vendor Daemon Uses the Options File When the vendor daemon is started by 1mgrd the vendor daemon reads its options file There is only one options file per vendor daemon and each vendor daemon needs its own options file For any changes in an options file to take effect the vendor daemon must read its options file The 1mreread utility causes the vendor daemon to reread its options file
139. some cases the license file requires no SERVER line and no VENDOR line You can modify these elements in the license file Host names on the SERVER line s TCP IP port numbers on the SERVER line s e Paths on the VENDOR line s Options file paths on the VENDOR line s Optional TCP IP port numbers on the VENDOR line s for firewall support only USE SERVER line e Values in keyword value pairs on FEATURE lines if keyword is specified in lowercase Use the V line continuation character to break up long lines 8 bit Latin based characters are fully supported in license files options files log files and FLEXIm licensed application environments See Section 4 4 Counted vs Uncounted Licenses for more information on SERVER and VENDOR line requirements FLEXLM VERSION NOTES USE SERVER introduced in the v5 0 FLEXIm client library e Line continuation character is required with the pre v7 0 FLEXIm client library 8 bit Latin based character support introduced in the v8 0 FLEXIm client library FLEXIm End Users Guide July 2003 113 License File Syntax B 1 B 1 1 114 License File Syntax Sample License File This is an example of a license file for a single vendor with two features SERVER my_server 17007ea8 1700 VENDOR sampled F EF EATURE fl sampled 1 000 01 jan 2005 10 SIGN 9BFAC0316462 EATURE f2 sampled 1 000 01 jan 2005 10 SIGN 1B9A308CCOF7 The licen
140. spell INTERNET 123 123 123 This options file 99 66 e Prevents the users picasso mondrian and klee from using the feature spell on any machine on the network e Prevents the user bob from using the feature spell on any machine on the network Prevents any user logged into a host with an IP address in the range 123 123 123 0 through 123 123 123 255 from using the feature spell Allows any other user as long as they are not on the excluded IP addresses and they are not a member of the painters GROUP and they are not bob to use feature spell by implication Note that bob could have been added to the group painters However painters might be used for some other purpose in the future so the license administrator chose to handle bob as a special case here In this case the two EXCLUDE statements concatenate to create a list of four users INCLUDE Example INCLUDE paint USER picasso INCLUDE paint USER mondrian INCLUDE paint HOST bigbrush This options file e Allows the user picasso to use the feature paint on any machine on the network e Allows the user mondrian to use the feature paint on any machine on the network FLEXIm End Users Guide July 2003 65 Options File Examples e Allows any user as long as they are on the host bigbrush to use feature paint
141. ss for each vendor who has a FLEX m licensed product on the network This process is called the vendor daemon The vendor daemon keeps track of how many licenses are checked out and who has them FLEX m licensed applications communicate with the vendor daemon through TCP IP network communications The FLEX m licensed application and the daemon processes the license server can run on separate machines on your network across any size wide area network Also the format of the traffic between the FLEX m licensed application and the vendor daemon is machine independent allowing for heterogeneous networks This means the license server and the computer running an application can be either different hardware platforms or even different operating systems Windows and UNIX for example FLEXIm End Users Guide July 2003 15 FLEXIm Components 16 If the vendor daemon terminates for any reason all users lose their licenses though this does not mean the applications suddenly stop running Users normally regain their license automatically when lmgrd restarts the vendor daemon though they may exit if the vendor daemon remains unavailable This behavior is defined by the vendor in the FLEX m licensed application THE LicENSE FiLE Licensing data is stored in a text file called the license file The license file is created by the software vendor and edited and installed by the license administrator It contains information about the server ma
142. stid of the server machine by running FLEX m s 1mhostid utility on that machine If you don t have 1mhost id get the hostid of your machine by using the appropriate command as described in Appendix A Hostids for FLEXIm Supported Machines Using the hostid of your server machines your vendor issues a license file to you that enables the application software LICENSE FILES AND LMGRD Once you have received a license file from your vendor you must install it on your system and start up the license manager daemon 1mgrd Your software vendor may have selected a default location for your license file If not use any location you wish For more details see Chapter 2 License File Basics e To start Lmgrd automatically at boot time you have to modify your system files UNIX or use LMTOOLS Windows For details see Section 2 2 License File Format Overview ADMINISTRATION TOOLS Macrovision supplies administration tools to your software vendor The vendor usually includes these utilities with their product Download the latest version from www macrovision com See Chapter 7 License Administration Tools for more information about how to use the FLEXIm utilities OPTIONS FILES The options file controls various options such as reservations and timeouts of licenses Most users run without an options file but you may decide you want to use some options For example many administrators use an option to limit the q
143. t be returned early once fulfilled those license days cannot be refunded Other pay per use models charge based on the number of times the application is used Mobile Licensing Hostids for FLEX m Supported Machines FLEXI m uses different machine identifications for different machine architectures For example all Sun Microsystems machines have a unique hostid whereas all DEC machines do not For this reason the ethernet address is used on some machine architectures as the hostid An ethernet address is a 6 byte quantity with each byte specified as two hexadecimal digits Specify all twelve hex digits when using an ethernet address as a hostid For example if the ethernet address is 8 0 20 0 5 ac specify 0800200005ac as the hostid A 1 Hostid Formats Numeric 32 bit hostids are normally used in hexadecimal format On some systems the system command returns the ID in decimal format Use a before the hostid to indicate a decimal number For example if the system command returns 2005771344 FLEXIm accepts 200577 1344 Alternatively convert the decimal value to hexadecimal A 2 Expected FLEX m Hostids The lmhostid utility prints the exact hostid that FLEX m expects to use on any given machine If your hostid contains characters other than ASCH A through Z a through z or 0 through 9 use the utf8 option with Imhostid To view a correct representation of the resulting hostid use a utility such as N
144. t hostid Platform Independent Hostids user Current user name display Current display name On Windows it is the system name or in the case of a terminal server environment the terminal server client name On UNIX it is in the form dev ttyxx or the X Display name hostname Current host name 86 License Administration Tools 7 7 Iminstall internet IP address of current platform in the form The output of this command looks as follows lmhostid Copyright c 1989 2002 Macrovision Corporation The FLEXlm hostid of this machine is 69021c89 SEE ALSO Appendix A Hostids for FLEXIm Supported Machines Iminstall Introduced in v6 0 1minstall is designed primarily for typing in decimal format licenses to generate a readable format license file Usage is lminstall i in lic file maxlen n e err file o out lic file overfmt 2 3 4 odecimal i Be See b Zee RERAN Normally to convert from decimal to readable format 1minstall is used with no arguments you are prompted for the name of the output license file The default file name is today s date in yyyymmdd 1ic format Move this file to the application s default license file directory if specified by the software vendor Otherwise use the LM LICENSE FILE Or VENDOR LICENSE FILE environment variables to specify the directory where the 1ic
145. the License Manager Daemon on UNIX Platforms 69 62T Manually ie io ef eere Ree Salis bee Heiss 69 6 2 2 Automatically eseese entia E ere SepEUUA T 70 6 3 Starting the License Manager Daemon on Windows 71 6 3 1 Manually from the Command Line 71 6 3 2 Configuring the License Manager as a Windows Service 72 6 3 3 Manually from LMTOOLS 0 0 0008 72 6 3 4 Automatically at System Start Up 004 74 Chapter 7 License Administration Tools 0 0 0 0c ce eee ee eee 77 7 1 Running Administration Tools 0 0 0 0000020 e eee 78 7 2 Universal Imutil Arguments 0 0 0 0 eese 79 7 3 AMDOMOW cuoco T NERO DUST NAE ES DNA 79 T4 Imdiag esc rh hr hh ER LEE ub areas 83 T3 Amd OW iis i uso te desee eredi tete 84 h6 Imhostid 2 ese Meee REA RES ME Ve CH YE 85 Tots Imanstall at Ge ects poteet oe ars koe Varga 87 T8 Imnewlog ve hs gee chisel me mat E WE we be ite we eli 88 1 95 Um pathic oL Se eat en een eee a 88 FAQ ImremoVe ood eser eee pt et ae Ret ee EG 90 Tb Imrere d 4 ifl seed ae CRINES Pe PS Ses 91 T 12 IIImstat i oed Re ook hee Ne a ie SIE SIE nS 93 PAB Umswitch Lue REDE E S E 95 1 14 ImswWitchir sss saei dos urge etetevyu seat og Reet pese 96 PAS MVR is iie eim ELE 4 ate Va e EAR e rea 97 7 16 License Administration Tools LMTOOLS for Windows 97 7 16 1 Configuration Using License File 98 7 16 2 Co
146. ting gt gt home flexlm v5 12 hp700 u9 boot log Please note the following about how this script was written All paths are specified in full because no paths are assumed at boot time The License Manager Daemon Note 6 3 6 3 1 Starting the License Manager Daemon on Windows Because no paths are assumed the vendor daemon must be in the same directory as 1mgrd or the VENDOR lines in the license file must be edited to include the full path to the vendor daemon The su command is used to run 1mgrd as a non root user daniel It is recommended that 1mgrd not be run as root since it is a security risk to run any program as root that does not require root permissions 1mgrd does not require root permissions Daniel has a csh login so all commands executed as daniel must be in csh syntax All commands not executed as daniel must be in bin sh syntax since that is what is used by the boot scripts The use of nohup and sleep are required on some operating systems notably HP UX and Digital UNIX These are not needed on Solaris and some other operating systems but are safe to use on all lmdiag is used as a diagnostic tool to verify that the server is running and serving licenses This does not start the daemon until you reboot your license server machine Starting the License Manager Daemon on Windows Manually from the Command Line Start lmgrd as an application from a Windows
147. tion that checks out additional features served by vendor that are not meant to be borrowed Clearing LM BORROW does not change the status for already borrowed licenses DETERMINING BORROWED LICENSE STATUS To print information about borrowed features issue the following command on the machine from which they are borrowed lmborrow status The borrowing system does not have to be connected to the network to determine the status RETURNING A BORROWED LICENSE EARLY To return a borrowed license early first reconnect the borrowing system back to the network and then from the same machine that initiated the borrowing issue the command lmborrow return c license file list c display feature FLEXIm End Users Guide July 2003 81 Imborrow where c license_file_list Use the specified license file s In some configurations the license file needs to be specified in order to return the license file early d display Used to specify the display from which the borrow was initiated Required if your current display is different than what was used to initiate the borrow On Windows it is the system name or in the case of a terminal server environment the terminal server client name On UNIX it is in the form dev ttyxx or the X Display name feature The name of the borrowed feature to be returned early Use lmborrow status to get a list of borrowed feature names Returning the license early has the effect
148. to denote a package suite If set the corresponding feature of the same name as the package is checked out in addition to the component feature being checked out If not set then the corresponding feature of the same name as the package is removed once the package is enabled it is not checked out when a component feature is checked out OPTIONS SUITE RESERVED Optional field If set reserves a set of package components Once one package component is checked out all the other components are reserved for that same user SUPERSEDE Optional field Used in conjunction with ISSUED pl p2 date Replaces all PACKAGE lines for the same package name with ISSUED dates previous to dd mmm yyy y ISSUED Optional field Used in conjunction with dd mmm yyyy SUPERSEDE Replaces all PACKAGE lines for the same package name with ISSUED dates previous to dd mmm yyy y FLEXIm End Users Guide July 2003 125 License File Syntax Table B 4 PACKAGE Line Fields Continued Field Description SIGN License key or SIGN signature pkg_sign Examples PACKAGE suite sampled 1 0 SIGN 3B24B2F508CB COMPONENTS compl comp2 OPTIONS SUIT FEATURE suite sampled 1 0 1 jan 0 5 SIGN 4193E6ABCCCB 4 2 E This is a typical OPTIONS SUITE example There are two features compl and comp2 which are each version 1 0 each with five non exp
149. tures served by this vendor daemon GROUP Define a group of users for use with any options GROUPCASEINSENSITIVE Sets case sensitivity for user and host lists specified in GROUP and HOST_GROUP keywords HOST_GROUP Define a group of hosts for use with any options v4 0 INCLUDE Allow a user to use a feature INCLUDE_BORROW Allow a user to borrow BORROW licenses INCLUDEALL Allow a user to use all features served by this vendor daemon LINGER Allow a user to extend the linger time for a feature beyond its checkin MAX Limit usage for a particular feature group prioritizes usage among users MAX BORROW HOURS Changes the maximum borrow period for the specified feature AX OVERDRAFT Limit overdraft usage to less than the amount specified in the license NOLOG Turn off logging of certain items in the debug log file REPORTLOG Specify that a report log file suitable for use by the SAMreport license usage reporting tool be written FLEXIm End Users Guide July 2003 47 Options File Syntax Table 5 1 Option Keywords Continued Option Keyword Description RESERVE Reserve licenses for a user or group of users hosts TIMEOUT Specify idle timeout for a feature returning it to the free pool for use by another user TIMEOUTALL Set timeout on all features FLEXLM VERSION NOTES 48 BORROW
150. uantity and content of logged messages To set up an options file see Chapter 5 The Options File Notes for End Users As a user of a FLEX m licensed application you may need to know a few things to use the system effectively The main things you need to know are How to tell an application which license file to use How to query the system to find out who is using a license How TO SPECIFY A LICENSE FILE LOCATION The license file determines what features are available to a FLEX m licensed application It also contains information telling the application how to connect to the license server FLEXIm End Users Guide July 2003 21 Getting Started Checklist 22 For information about the standard way of specifying the location of a license file for an application see Chapter 2 License File Basics GETTING INFORMATION ABOUT LICENSES To find out who is using a license run 1mstat described in Chapter 7 License Administration Tools Introduction and Overview License File Basics The license file contains information required by FLEX m to manage licenses for a FLEX m licensed application This information includes License server names and hostids Vendor names and paths to vendor daemon executables Feature information In general the license file or a copy of it must be accessible to every machine that runs a FLEX m licensed application and to each machine designated as a license server
151. uite license administration tool for managing FLEX m enabled applications the SAMreport Users Guide describes the SAMreport license usage reporting tool and the SAMwrap Users Guide describes SAMwrap for administrators who wish to provide FLEX Im license management for applications shipped without embedded FLEX m license management The FLEXIm Programmers Guide and FLEXIm Reference Manual are for programmers responsible for incorporating FLEX m into their products Typographic Conventions The following typographic conventions are used in this manual The first time a new term is used it is presented in italics Commands and path file and environment variable names are presented ina fixed font Other variable names arein an italic fixed font API function calls are in a sans serif font Introduction and Overview This chapter explains the basics of floating network licensing and gives a quick overview of the components of FLEX m It explains where license administrators have control and where end users have control Section 1 6 Getting Started Checklist tells both license administrators and end users how to start managing FLEXIm 1 1 Introduction to FLEX m FLEX m is the most popular license manager used in the software industry FLEXIm is best known for its ability to allow software licenses to be available or float anywhere on a network instead of being tied to specific machines Floating licensing benefits b
152. umbers of clients For a large number of FLEX m licensed applications hundreds each of which exchange heartbeat messages with the vendor daemon the network bandwidth used may start to become significant In this case run the FLEX m licensed application and server on the same local area network which may Selecting Server Machines 4 2 4 3 Remote Mounted Disks require splitting licenses between two files for two servers Users can use a license file list in the LM_LICENSE_FILE environment variable to have effective access to both servers SEE ALSO Section 2 1 Specifying Location of the License File Remote Mounted Disks Macrovision recommends that you do not use remote mounted disks when you run the license server In other words it is recommended that 1mgrd the vendor daemons the license file and the debug and report log files are all on locally mounted disks If any of these files is on a remote mounted disk you double the points of failure which could lead to a temporary loss of all of your licenses When all files are mounted locally the licenses are available as long as the server machine is up but when the files are on a different machine then the loss of either the license server machine or the file server machine causes the licenses to be unavailable Redundant License Servers If you wish to use redundant servers select stable systems as server machines in other words do not pick syst
153. ure that you are using a compatible version of 1mgrd for each particular license file This is done by using an explicit path to lmgrd See Section 3 6 2 Version Component Compatibility The number of license servers is limited only by the CPU memory and networking of the machine ADVANTAGES The license files for each vendor are independent from one another License servers are maintained separately If one server goes down the other servers continue to serve licenses for their vendors Each server has its own debug log FLEXIm End Users Guide July 2003 31 One Machine with One License Server and Multiple License Files DISADVANTAGES Administrative overhead is high e Ifthe machine goes down all licensing is disabled Licensing load is concentrated to one machine STARTING THE LICENSE SERVER Invoke each license server e For Server 1 1mgrd c vendor ABC license dir list e ForServer2 Imgrd c vendor DEF license dir list e ForServer3 1mgrd c vendor XYZ license dir list Where vendor nnn license listisalicense file list as described in Section 3 5 Managing Multiple License Files Each 1mgrd starts the vendor daemon referred to in its license file s 3 4 One Machine with One License Server and Multiple License Files In this scenario one 1mgrd process runs on the server machine and serves one or more vendor daemons each with one or more license files the license files usually are in the same directory
154. ve lmstat aisa potentially expensive command With many active users this command generates a lot of network activity FLEXLM VERSION NOTES e Ability to list all active users using the A option available in FLEX m lmstat utility v8 3 and earlier Imswitch The 1mswitch utility switches the debug log file written by a particular vendor daemon by closing the existing debug log for that vendor daemon and starting a new debug log for that vendor daemon with a new file name It also starts a new debug log file written by that vendor daemon if one does not already exist Usage is lmswitch c license file list vendor new debug log where c license file list Use the specified license file s vendor Vendor daemon in this license file new debug log Path to new debug log file By default debug log output from lmgrd and all vendor daemons started by that lmgrd get written into the same debug file 1mswitch allows companies to keep separate log files for different vendors and control the size of their debug log file FLEXIm End Users Guide July 2003 95 Imswitchr Note 7 14 96 If debug log output is not already directed to a separate file for this vendor daemon 1mswitch tells the vendor daemon to start writing its debug log output to a file new debug 1og lf this vendor daemon is already writing to its own debug log 1mswitch tells the vendor daemon to close its current debug log file and start writing its debug
155. ww macrovision com and you ll automatically enjoy many of the enhancements available in the most recent versions of FLEX m However some enhancements require a vendor daemon built with a newer version of FLEX m and yet others require a FLEX m licensed application built with a newer version of FLEX m Contact your software vendor for the most current version of their vendor daemon The rules about FLEX m version compatibility are summarized as Version of lmutil LMTOOLS must be gt Version of 1mgrd which must be gt Version of vendor daemon which must be gt Version of FLEX m licensed application which must be gt Version of license file format Except for the license file use 1mver to discover the version of all these components For the vendor daemon 1mgrd and 1mutil you can also use the v argument to print the version H 2 Howto Tell the License File Version The following rules apply to individual FEATURE INCREMENT or UPGRADE lines It s possible to have a mix of versions in a single file Only the features that a particular application checks out determine the version of the license for that feature Version 2 Blank quotes or a quoted string at the end of the FEATURE line gt Version 3 INCREMENT or UPGRADE line FLEXIm End Users Guide July 2003 155 Version Summary H 3 156 gt Version 4 OVERDRAFT DUP_GROUP INTERNET or PACKAGE appear gt Version 5 SUPERSEDE ISSUED USER_BASED HOST_B
156. www macrovision com File Edit Mode Help Service License File System Settings Utilities Start Stop Reread Server Status Server Diags Config Services Borrowing Services allow FLEXLM Servers to run in the background r Server List Configuration using License File Configuration using Services vendor License Manager Ui LMTOOLS appears with the Service License File tab open 2 Click the Configuration using Services radio button 3 Select the service name from the list presented in the selection box In this example the service name is Myvendor License Manager FLEXIm End Users Guide July 2003 73 Starting the License Manager Daemon on Windows 4 Click the Start Stop Reread tab LMTOOLS by Macrovision Corporation http www macrovision com File Edit Mode Help Service License File System Settings Utilities Start Stop Reread Server Status Server Diags Config Services Borrowing Flexlm license Services installed on this computer Start Server Stop Server ReRead License File Force Server Shutdown GORI Se NOTE This box must be checked to shut down a license server when licenses are borrowed Using License File C flexim myvendor lic 5 Start Myvendor License Manager by clicking the Start Server button Myvendor License Manager license server starts and writes its debug log output to c flexlm lmgrd dl 6 3 4 Automatically at System Start Up I
157. y the servers multiple servers quorums redundant license servers Creating and editing the options file Using the license manager daemon lmgrd Managing FLEX m using Macrovision supplied utilities Licensing to allow working on a computer disconnected from the license server Appendix B License File Format Appendix C Troubleshooting Guide 1 2 2 End User If you are an end user read these chapters Chapter Explains Preface Overview of this manual 12 Introduction and Overview FLEXIm Components Chapter Explains Chapter 1 FLEX Im basics license and vendor daemons Introduction and the license file configuring FLEX m the Overview license request process Chapter 2 License License file basics setting the path at start up File Basics different types of licensing policies Chapter 8 Mobile Licensing to allow working on a computer Licensing disconnected from the license server In addition refer to Appendix C Troubleshooting Guide 13 FLEX m Components FLEX m components are organized based on the license model used by your software vendor License models are classified according to their requirement for a license server Licenses are served by a license server This is commonly referred to as a served license model License files supplied by your software vendor that include SERVER VENDOR and optionally USER SERVER lines require a license server See Section 1 3 1 S
158. yntax for details about securing access to lmreread FLEXLM VERSION NOTES 92 Ability for vendor daemon to participate in rereading of its option file introduced in v8 0 vendor daemon License Administration Tools 7 12 Imstat Imstat The 1mstat utility helps you monitor the status of all network licensing activities including Daemons that are running License files Users of individual features Users of features served by a specific vendor daemon BORROW licenses borrowed lmstat prints information that it receives from the license server therefore it does not report on unserved licenses such as uncounted licenses To report on an uncounted license the license must be added to a served license file and the application must be directed to use the license server for that license file via host port host or USE_SERVER Queued users and licenses shared due to duplicate grouping are also not returned by 1mstat Usage is imstat a c license file list f feature i feature s server S vendor t timeout value where a Displays all information c license file list Uses the specified license file s f feature Displays users of feature If feature is not specified usage information for all features is displayed i feature Displays information from the FEATURE INCREMENT line for the specified eature or all features if feature is not specified s server Displ

End Users Guide

Contents

Download Pdf Manuals

Related Search

Related Contents