Many vendors choose FLEX lm as their license manager, and it is likely that you must administer licenses from more than one vendor, or multiple products from the same vendor.
lmgrdcan only control a single license file.
lmgrd s and license files simplifies initial installation and can increase daily administration of your licenses. For multiple license servers, you have more license servers to monitor. For the one license server, you have only one server, but multiple
lmgrd s to administer.
Your product's license file (or files) define the license server (or servers) by hostname and hostid in the SERVER line (or lines) in the license file. If the license files for two or more products contain identical SERVER lines, then see Using the Same Server Node . If the license files for two products contain different SERVER lines, then the license servers for those products will run on different nodes.
If you have two or more products with license servers run on the same node (as specified by the SERVER lines in the license files), you may be able to combine the license files into a single license file. If the SERVER lines in those files have identical hostids, then you can combine the files into a single file. If the SERVER lines have different hostids, then you must keep the license files separate.
If the license files are not compatible, you must keep the license files separate, and run separate copies of
lmgrd for each license file, as described in Using Separate license files on the same server node .
Note: Combining compatible license files is not required. You always have the option of running separate
lmgrds as described in Using Separate license files on the same server node .
If your license files are compatible (i.e., use the same server nodes), you can combine them with any text editor. 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. Write out this data, and you have your combined license file. If you write the data to license.dat in the default location, you will generally not need to set the
LM_LICENSE_FILE environment variable. If you write the data out elsewhere, or if you were able to combine some but not all of your license files, then you must set the
LM_LICENSE_FILE variable (unless your application uses another method to find the license file).
When you combine license files for two different FLEX lm -licensed products, those products might not use the same version of FLEX lm . FLEX lm is designed to handle this situation, and has two basic compatibility rules for FLEX lm:
2. A newer vendor daemon (or
lmgrd ) can be used with an older client program (such as an application or utility programs like lmstat ), but a newer client program might not work properly with an older vendor daemon.
1. Products using version 2.0 of FLEX lm may not be combined in one license file with products using version 1.5 or earlier of FLEX lm . In this case, you must use separate license files (see Using Separate license files on the same server node ).
2. If you combine a product using version 2.1 or later of FLEX lm with a product using version 1.5 or earlier of FLEXlm , you must use the"-b" (for backwards compatibility) command line option to
lmgrd . You can always use a version of
lmgrd that is newer than the one provided by your software vendor, as long as you are careful to use the "-b" switch if replacing v1.x
lmgrd with a v2.1 or later
Note: FLEX lm v2.4 and later versions of
lmgrddefault to "-b". Do not use the "-b" option if you are using FLEX lmv2.4 or later.
If you have incompatible license files, you must run a separate copy of
lmgrd for each license file. (You can also do this even if your license files are compatible.) When you run
lmgrd separately for each license file, there are two details to remember:
2. You must make sure that you are using a compatible version of
lmgrd when you start it up for a particular license file. This can be done by either using an explicit path to
lmgrd , or by renaming
lmgrd to something specific for that product (some vendors do this to make it easier to identify the lmgrd they ship with their product).
When running client programs (such as a licensed application), you can set the
LM_LICENSE_FILE environment variable to point to multiple license files. For example, you may have a license file from vendor ABC and a license file from vendor XYZ with incompatible servers. You can place the license file from vendor ABC into:
LM_LICENSE_FILEcan point to only one license file for FLEX lm v1.x applications.
If products use different license server nodes, each set of license servers requires separate license files. (When multiple software vendors use the same set of license server nodes, the technique described above in Using the Same Server Node can be used to combine license files.) The resulting (multiple) license files can be installed in convenient locations, and you would set the
LM_LICENSE_FILE environment variable as follows:
Each application queries each license file in the order listed in the
LM_LICENSE_FILE path. If the license server serving the license file listed in lfpath1 was unreachable, perhaps due to an NFS problem, changing the
LM_LICENSE_FILEwould allow a user to obtain a license from another server.
For more information about
LM_LICENSE_FILE and setting the location of the license file, see Specifying Location of the License File .