Reserve shared licenses

Use the license share feature in the FLM to ensure that reserved licenses are shared.

Sharing licenses that are reserved for a group of users or an application is possible using the Four Js License Manager (FLM). A reservation of a license sets aside a number of licenses (a user count) for a designated usage. For more information on license reservation, see Manage license reservation (flmprg).

In a reservation using a share, users are reserved in as many licenses as declared in the shared license list.

To share licenses, you need to have the licenses installed. You must ensure the licenses are for the same product, and are of the same type (development or runtime) and extension (the specific conditions of the license).

After making a configuration change, you will need to restart the FLM (at the command line type flmprg --service-restart to restart the server). For more information, see Starting Four Js License Manager and Stopping license manager.

In this task you will share two licenses in one reservation for developers.

  1. Open your FLM configuration file, FLMDIR/etc/flmprofile, for editing.
  2. Declare license shares. For the purpose of this task we will declare one share named "dev_licenses".
    [shares]
    names="dev_licenses"
  3. Declare the share, and assign it source licenses (you need a minimum of two licenses).
    [share.dev_licenses]
    licenses=TAB#XXXXXXX3 TAB#XXXXXXX6
  4. Declare a reservation for "dev".
    [reservations]
    names=dev
  5. Declare the reservation, and assign it a share as the source of the licenses and a user count.
    [reservation.dev]
    share=dev_licenses        # Declare a reservation on the share "dev_licenses"
    count=10
  6. Test your license server configuration.
    Use the command flmprg --validate-configuration to check the configuration is valid.
    Details of invalid entries are written to stdout. You will need to fix the errors because the server will not start with errors in the configuration. If there are no errors reported, "Ok" is output.
  7. Output the license information.
    Use the command flmprg -a info to output the license information. Entries are written to stdout; it should now include the reservation.
    License      : TAB#XXXXXXX7
    License key  : NSV88HEYXXDE
    Product      : Four Js Universal Compiler
    Type         : Development version
    Users        : 9/10
                   Reserved users: 1
    Extensions   :
    #...
    
    Reservation  : dev
    Share        : devlicenses
    License      : TAB#XXXXXXX7
    Users        : 1
    
    License      : TAB#XXXXXXX8
    License key  : NSV88HEYXXDE
    Product      : Four Js Universal Compiler
    Type         : Development version
    Users        : 1
    Extensions   :
    #...
    
    ==== Shared licenses ====
    
     - Share   : devlicenses
       Users   : 10
    
       Licenses:
         TAB#XXXXXXX7, 9 users
         TAB#XXXXXXX8, 1 users
  8. Restart the license manager.
    Type flmprg --service-restart

    The FLM service is started.

  9. Configure on the client side to use the reserved licenses. For an example, go to Configure license reservation/shares on the client side.