Specify the licensing configuration file

An FLM or license controller configuration file provides the details for licensing your Genero product. You can enter the license details in the default license controller configuration file, or you can set an environment variable to specify an alternate license controller configuration file.

Table 1 identifies the environment variables that allow you to specify an alternate licensing configuration file. If the environment variable is not set, the default configuration file is used.

Table 1. License environment
Package	Environment variable	Use	Default
FLM	FLMPROFILE	Specify the FLM license configuration file.	$FLMDIR/etc/flmprofile
FGLGWS	FGLLICENSE	Specify the Four Js License Controller for BDL (fglWrt) configuration file (or multiple configuration files).	$FGLDIR/etc/fgllicense

Do I need multiple license controller configuration files?

You may find multiple files useful when using a Four Js License Manager (FLM) and you need to have different settings for logs, license reservations, and license shares.

For example, you have a Genero BDL license with 100 users. You can define one configuration file with the base FLM server settings (for example, fgllicense.base) and specify the reservation in another configuration file (for example, fgllicense.dev).

For the development team that needs 20 users, the development environment is set:

$FGLLICENSE=/mydir/fgllicense.dev;/mydir/fgllicense.base

For the remaining licenses used by the rest of the company, the environment is set:

$FGLLICENSE=/mydir/fgllicense;/mydir/fgllicense.base

When defining multiple license configuration files, the filenames must be separated by the operating system specific path separator. The path separator is ":" on UNIX™ platforms and ";" on Windows® platforms.

on UNIX:
export FGLLICENSE=/mydir/fgllicense.dev:/mydir/fgllicense.base

on Windows:
set FGLLICENSE=c:\mydir\fgllicense.dev;c:\mydir\fgllicense.base