Four Js License Manager usage scenarios

Use the scenarios described here to understand some ways you can implement an FLM in your network.

FLM is useful in both development and runtime environments, as it allows for easier management of licensing for different machines, platforms, Genero products, and product versions connected across a network.

Scenario 1: Different versions of Genero products

In this scenario, you have a five-user developer license. You have five developers whose workload on any given day could be divided between the following:
  • Working on the next release of your products
  • Supporting the current release of your product
  • Supporting one or more older releases of your product
For example, two users may be using Genero product version 3.10 and three users may be using version 3.20. FLM supports this scenario.

Implementation

On the network:
  • Install the Four Js License Manager (FLM) on a server.
  • Edit your FLM configuration file, $FLMDIR/etc/flmprofile:
    [server] # FLM host # host=localhost # Default service port port=6800
    • Set the host resource to the name of the machine that hosts FLM. The default is localhost.
    • Set the port to the port number for the communication between the license controller and FLM. If not set, the default is 6800.
  • Start the FLM service. Run flmprg -r on UNIX® /Linux® and flmprg --service-start on Windows®.
On the user server:
  • Update your Genero product license configuration file (fgllicense or grelicense):
    • Set the host and port with details of the FLM. These values should be the same as the entry in the FLM configuration file ($FLMDIR/etc/flmprofile).
      [server] # FLM service host host=localhost # FLM service port port=6800
                      
    • Add the license number in the configuration
      [license] # License to use with FLM service 
      number=TAB#XXXXXXXX
      All licenses need to be installed on the FLM (run the command flmprg -l to install licenses), but only one license needs to be specified in the product license configuration file.
Tip: When you install a new product version, just add details of the license in the Genero product license configuration file. With FLM there is no need to register the license (get the installation key).

Scenario 2: Sharing licenses on different servers for QA and Development

In this scenario, you have more than one server in your development environment. There are three servers dedicated to QA: a Windows®, a Linux®, and a Mac® server. You have five QA team members and on any given day they could be testing on Windows, Linux, or Mac versions of your product. You also have ten-users on a developer server.

In a local license scenario all four servers need separate Genero licenses:
  • A ten-user license for your development server
  • A two-user license for your Linux QA server
  • A two-user license for your Windows QA Server
  • A two-user license for your Mac QA Server
Using FLM you only need one license that all these different servers share. You might, for example, decide to have a fourteen-user license that is shared by all users as demand permits.

Implementation

On the network:
  • Install the Four Js License Manager (FLM) on a server.
  • Edit your FLM configuration file, $FLMDIR/etc/flmprofile:
    [server] # FLM host # host=localhost # Default service port port=6800
    • Set the host resource to the name of the machine that hosts FLM. The default is localhost.
    • Set the port to the port number for the communication between the license controller and FLM. If not set, the default is 6800.
  • Start the FLM service. Run flmprg -r on UNIX® /Linux® and flmprg --service-start on Windows®.
On the QA and developer servers:
  • Update your Genero product license configuration file (fgllicense or grelicense):
    • Set the host and port with details of the FLM. These values should be the same as the entry in the FLM configuration file ($FLMDIR/etc/flmprofile).
      [server] # FLM service host host=localhost # FLM service port port=6800
                      
    • Add the license number in the configuration
      [license] # License to use with FLM service 
      number=TAB#XXXXXXXX
      All licenses need to be installed on the FLM (run the command flmprg -l to install licenses), but only one license needs to be specified in the product license configuration file.

Scenario 3: Development and/or runtime License Sharing

Warning: Sharing licenses of the same product, type, and option between a cumulative group of users, as previously set by flm.license.shared, is not yet available in FLM 6.00.
In this scenario you have two or more development and/or runtime licenses for the same Genero product used by different teams. In a local licensing scenario you have, for example:
  • Five users on one license
  • Ten users on a second license
Often the demand for licenses can change from one team to the other.

Using FLM, you can combine the licenses. Instead of having five users on one license and ten users on the other, you now have fifteen users using the two licenses as demand requires.

Note: This license sharing solution applies only to licenses for the same product, type (runtime or developer), and extension (specific conditions of the license). The total user count can not exceed the number of users allowed for by the combined licenses.
The image illustrates the scenario where two development teams are connecting to the Four Js License Manager and sharing the developer licenses. This scenario can equally be applied for runtime purposes.
Figure: Four Js License Manager Scenario

The image illustrates a scenario where users in two development teams are connecting to the Four Js License Manager to share developer licenses.

Implementation

Details on implementation will be added when this feature is made available.
Note: The license server included in Windows DVM distributions version 2.60 and earlier is not compatible with Four Js License Manager. This earlier license server module (which only existed on Windows operating systems) can be replaced by Four Js License Manager.