Configuring the License Manager

To configure the Four Js License Manager (FLM), edit the $FLMDIR/etc/lmprofile file.

To set the value of a resource in this file, add the line with the following format:

Syntax

name-of-resource="value"
For example:
flm.server="localhost"

The following resources are available:

Table 1. License Manager Configuration Resources
Resource Name Default Value Description
flm.server none Name of the machine that hosts FLM. Set this value to the current machine name or IP address. If your DNS or your hosts file is correctly configured, you can safely use localhost.
Warning: Although no default is provided, this parameter is mandatory.
flm.service 6399 Service or port number for the communication between the license controller and FLM.
flm.check 100 Number of connections between checks of the registered users list for a host machine. The control of active users is important, as it will synchronize real users on the network with the registered users list managed by FLM.

The check is used to recover licenses from user that are no longer alive (in case of vm crash, the associated license may not be recovered).

CAUTION:
To disable this control, set the parameter to -1. However, if you disable it, please be aware that some registered users will never be unregistered by the FLM unless you run the flmprg -u <license number>, see Force a Check of the Registered Users List (flmprg)
flm.license.shared 1 Indicates whether the users are shared between licenses. If you have licenses for the same product, type, and extension, the total number of users will be cumulative. If this resource is set to 0, this will not be done.
flm.cnxlog.enabled 0 Set this entry to 1 to activate the FLM connection log. Support may request that you enable this option and send the generated log files to aide in analyzing licensing issues.
The log files are created in FLMDIR. The files are named using the pattern flm-YYYYMMDD-id.log, where:
  • YYYY = current year
  • MM = current month
  • DD = day of month
  • id = counter value. The counter value is incremented each time the FLM is started.
Note: The flm.storage configuration entry was deprecated in version 5.12.08. If a configuration entry is set for flm.storage, it is silently ignored.