Configure a Genero license controller

Edit the license controller configuration file to configure a Genero license controller.

To use a license managed by the Four Js License Manager (FLM), you must configure the product's license controller configuration file locally with details regarding the FLM server and the license number for the product.

Locate your product's license controller configuration file.

Table 1. Genero products and license configuration files
Genero product	Default license controller configuration file
Genero Business Development Language (BDL)	$FGLDIR/etc/fgllicense
Genero Report Engine (GRE)	$GREDIR/etc/grelicense

Tip:

Default locations of the license controller configuration files are shown. You can set the location of these files by using the FGLLICENSE or GRELICENSE environment variables.

See Specify the licensing configuration file.

To set the value for the FLM server, add the line in the following format with the name of the server:
```
[server]
host=hostname 
port=port     # Default is 6800
```
To set the value for the license number, add the line in the following format:
```
[license]
# License to use with FLM service
number=license_number
```

Add or update values for the resources shown in Table 2 as required:

Category Description

[server]

Details of the machine that holds the license service program.

Resource	Default value	Description
`host=hostname`	Warning: Although no default is provided, this parameter is mandatory.	This value should be the same as the entry in $FLMDIR/etc/flmprofile.
`port=value`	`6800`	This value should be the same as the entry in $FLMDIR/etc/flmprofile.

[license]

Set either the product license number or license reservation. They are mutually exclusive.

Resource	Default value	Description
`number=license_number`	Warning: Although no default is provided, you must set this value to use Four Js License Manager.	Value of your current license number. (For example: `number=XXX#XXXXXXXX`) Important: If using FLM, the license `number` and `reservation` options are mutually exclusive; you must configure one or the other, but not both. If not using FLM, license reservation is not an option; configure the license number.
`reservation=` `user_group`	none	Identify users for whom licenses are reserved. For example, `reservation=qa`, "qa" must correspond to a value in the `reservations` entry in the FLM configuration file, $FLMDIR/etc/flmprofile, where license reservation is configured. Important: If using FLM, the license `number` and `reservation` options are mutually exclusive; you must configure one or the other, but not both. If not using FLM, license reservation is not an option; configure the license number.
`user.check=value`	`10`	Number of requests between active users check. A value of `-1` disables the feature.

[log]

Enable and configure license controller logs and log rotation. For more information on configuring logs, see .

Resource	Default value	Description
`enabled= { true\| false }`	`false`	Enable or disable logging. `enabled` on its own is the equivalent of `enabled=TRUE`.
`directory=dir-path`	none	Directory where log files are stored. For example, `directory=${TEMP}/log`
`categories=[ error, info, warning, debug ]`	none	Specifies in a comma-separated list categories of errors to log. `categories= "error, info, warning, debug"` .
`maxsize= value { K \| M \| G }`	-1 (no limit, log rotation is not performed)	Specifies log rotation. Set the maximum size for the log file. The size `value` can be in kilobytes, megabytes, or gigabytes. For example, `maxsize=512M`. When the size is reached, the file is closed and a new one is created.
`maxfiles=value`	2	In log rotation, specify a maximum number of log files to keep. For example, `maxfiles=5`. The license controller rotates files by renaming and renumbering them up to the `maxfiles` value, for example, fglwrt.log, fglwrt.1.log, fglwrt.2.log, and so on. It deletes the file that exceeds the `maxfiles` value.
`syslog={ true\| false }`	`false`	Redirect FLM logs to the system log of Unix-like platforms only. Warning: The syslog feature can not be enabled on Windows®.