FLM 6.00 upgrade guide
These topics describe product changes you must be aware of when upgrading to version 6.00.
This is an incremental upgrade guide that covers only topics related to the Four Js License Manager version specified in the page title. Check prior upgrade guides if you migrate from an earlier version, and complete the migration tasks for all versions between your existing version and the target version in order. Make sure to also read about the new features for this version.
Corresponding new features page: Licensing 6.00 new features.
The FLM configuration file has changed
The default configuration file for FLM 6.00 is now $FLMDIR/etc/flmprofile; the file $FLMDIR/etc/lmprofile is no longer relevant and is no longer provided. The new configuration file involves a new format and has new entries. For more information and to discover available configuration options, see Configure the License Manager.
You can enter your configuration details in the default file provided, or you can specify a different configuration file, as described next.
Specifying the configuration file
You can define environment variables to specify the FLM configuration file (FLMPROFILE) or the license controller configuration files (FGLLICENSE and GRELICENSE) to use.
Starting at FLM 6.00.10, the FLM reads a single configuration file only. If the environment variable for the FLM configuration file or the license controller configuration file environment variable is set, the file identified by that variable is used; otherwise, the default file located in the product installation directory is used.
For example, if FLMPROFILE is set, the file specified will be used and the FLM configuration file $FLMDIR/etc/flmprofile will be ignored.
For more information on setting these environment variables, see Specify the licensing configuration file.
FLM default communication port
Service or port number for the communication between the license controller and FLM has changed from 6399 to 6800.
For more information, see Configure the License Manager and Configure a Genero license controller.
Sharing similar licenses between a user pool is currently unavailable
Starting at FLM 5.19, you were able to use the resource flm.license.shared
to
combine licenses of the same product, type, and extension to create a cumulative user pool. For
example, if one license had 5 users and the other license had 10 users, setting this resource
allowed you to share these two licenses amongst a cumulative pool of 15 users.
This functionality is not yet available for FLM 6.00.
flmprg command --validate-configuration
Starting at version 6.00.12, the flmprg --validate-configuration command is added to validate the FLM configuration. After making changes to the flmprofile FLM configuration file, it is advised to run this command to validate the configuration entries.
For more information about flmprg see FLM (flmprg) options.