Four Js License Manager usage scenarios

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

FLM can prove to be very useful in both development and user environments as it allows for easier management of licensing for different machines, platforms, Genero products, and product versions connected across a network.

Scenario 1: Development and/or runtime License Sharing

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

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

On the network:
  • Install the Four Js License Manager (FLM) on a server.
  • In the FLM configuration file, $FLMDIR/etc/lmprofile:
    • Set the resource flm.server to the name of the machine that hosts FLM.
    • Set the flm.service to the port number for the communication between the license controller and FLM.
    • Set the resource flm.license.shared=1 (1 is the default setting).
  • Start the FLM service. Run flmprg -r on UNIX® /Linux® and flmprg --service-start on Windows®.
On the user server:
  • Update the Genero product FGLPROFILE file:
    • Set the flm.server and flm.service with details of the FLM
    • Add details of the license in the flm.license.number and flm.license.key configuration. Only one license needs to be specified in the FGLPROFILE file.
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.

Scenario 2: 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.00 and three users may be using version 3.10. With FLM this scenario is supported.

Implementation

On the network:
  • Install the Four Js License Manager (FLM) on a server.
  • In the FLM configuration file, $FLMDIR/etc/lmprofile:
    • Set the resource flm.server to the name of the machine that hosts FLM.
    • Set the flm.service to the port number for the communication between the license controller and FLM.
  • Start the FLM service. Run flmprg -r on UNIX® /Linux® and flmprg --service-start on Windows®.
On the user server:
  • Update the Genero product FGLPROFILE file:
    • Set the flm.server and flm.service with details of the FLM
    • Add details of the license in the flm.license.number and flm.license.key configuration.
      Tip: When you install a new product version, just add details of the license in the Genero product FGLPROFILE file. With FLM there is no need to register the license (get the installation key).

Scenario 3: 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 on the network.
  • In the FLM configuration file, $FLMDIR/etc/lmprofile:
    • Set the resource flm.server to the name of the machine that hosts FLM.
    • Set the flm.service to the port number for the communication between the license controller and FLM.
  • Start the FLM service. Run flmprg -r on UNIX® /Linux® and flmprg --service-start on Windows®.
On the QA and developer servers:
  • Update the Genero product FGLPROFILE file:
    • Set the flm.server and flm.service with details of the FLM
    • Add details of the license in the flm.license.number and flm.license.key configuration.
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.