TOCPREVNEXTINDEX


Chapter 3

Managing Licenses from Multiple Vendors


Since more than 2500 vendors have chosen FLEXlm as their license manager, chances are good that you have to administer FLEXlm licenses from more than one vendor.

3.1 Overview of Multiple License Management Strategies

When you are running FLEXlm-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:

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.”

3.2 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 lmgrd. Figure 3-1 shows this arrangement.

Figure 3-1: Multiple Server Machines
Advantages
Disadvantages
Starting the License Server

Invoke the license manager daemon on each machine:

lmgrd -c server_machine_n_license_list

Where server_machine_n_license_list is a license-file list as described in Section 3.5, “Managing Multiple License Files.” Each lmgrd starts the vendor daemon referred to in its license file(s).

3.3 One Machine with Multiple License Servers

In this model, each vendor daemon and its associated license file or files is served by its own lmgrd process, and everything is contained in one server machine. Figure 3-2 depicts this scheme.

Figure 3-2: Multiple lmgrds, Multiple License Files

When maintaining separate license servers on the same machine, keep in mind:

Advantages
Disadvantages
Starting the License Server

Invoke each license server:

Where vendor_nnn_license_list is a license-file list as described in Section 3.5, “Managing Multiple License Files.” Each lmgrd 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 lmgrd 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. The standard filename extension for license files is .lic. The number of vendor daemons is not limited by FLEXlm. Figure 3-3 illustrates this scenario.

Figure 3-3: One lmgrd, Multiple License Files
Advantages
Disadvantages
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 in those files; so, there is no need to enumerate each license file name on the lmgrd command line.

See Also

FLEXlm Version Notes


3.5 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:

Install the license files in convenient locations on the server machine and then define the license_file_list.

Wherever license_file_list is specified it consists of a list of one or more of the following components:

lmgrd 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 include 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

3.6 Additional Considerations

3.6.1 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, “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.

Figure 3-4: One lmgrd, One License File
Advantages
Disadvantage
Starting the License Server

Invoke the license manager daemon once on the server machine.

lmgrd -c combined_license_file

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:

Some possible reasons license files may not be compatible are:

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 no performance or system-load penalty for not combining the files.

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.

Figure 3-5: Combining License Files

3.6.2 Version Component Compatibility

When one lmgrd process manages multiple vendor daemons, it may be the case that those vendor daemons do not use the same version of FLEXlm. By observing the FLEXlm version compatibility rules described in Section H.1, “Version Compatibility and Components,” you are assured that all of your FLEXlm components are compatible.

For specific FLEXlm-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).


TOCPREVNEXTINDEX

 

FLEXlm End Users Guide
August 2004