Licensing 6.00 new features
Review this topic for information about new features and changes in existing functionality that have been introduced in this release of the Genero Licensing manual.
Corresponding upgrade guide: Upgrade Guides for Licensing
Previous new features page: Licensing 5.20 new features.
Version 6.00 Overview | Reference |
---|---|
Four Js License Manager (FLM) 6.00 introduces a new license manager. This version is a rebuild of the existing architecture with several notable improvements to its functionality and performance. | No additional reference. |
FLM 6.00 supports Genero Business Development Language (BDL) and the Genero Report Engine (GRE). | No additional reference. |
FLM 6.00 supports licensing of Genero 4.00, 3.20, and 3.10 products. Genero 3.20 and 3.10 products must be configured for compatibility mode to work with FLM 6.00. | See Configure compatibility for Genero prior to 4.00 |
"flmprofile" is the FLM 6.00 configuration file, replacing the "lmprofile" of previous versions, and includes enhancements for license configuration. | See |
Four Js delivers a license string encoding the license
details (to include the license number, license key, maintenance or subscription key, and
login name.) You can install the license using the flmprg
--install-license-string option by simply pasting the string at the end of the
command. Tip:
You can create a license string from your existing license details using the
|
See |
There are log configuration enhancements, including options to configure log categories,
generate debug logs, and rotate log files. The flmprg --log-rotate command option
allows you to start log rotation at any time; even while log files are in use. |
See: |
FLM 6.00 introduces environment variables to specify the location of the license controller configuration file. | See Specify the licensing configuration file |
The batch mode (flmprg --batch ) and batch console
(flmprg --batch-console ) commands output to standard out in JSON format. |
See FLM (flmprg) options |
Starting at 6.00.10 | |
The FLM has a license reservation feature. You can reserve licenses for a named group of users, ensuring licenses are always available for them. License reservation applies only to User type licenses (not CPU licenses.) | See Manage license reservation (flmprg) |
The FLM can detect and release licenses consumed by inactive sessions. The
client pings the FLM at regular intervals while active; if the ping is not received, the FLM kills the session and
recovers the license. Configure this feature with the client.interval.ping resource in the
flmprofile file. |
See Configure the License Manager |
Starting at 6.00.12 | |
Use environment variables to specify the location of multiple license controller configuration files. | See Specify the licensing configuration file |
The flmprg
--validate-configuration command option allows you to check the FLM configuration
file for invalid configuration entries. |
See FLM (flmprg) options |