License Manager configuration / Linking a DVM to Four Js License Manager |
To configure your license controller for License Manager, on the server where the DVM is installed, edit its configuration file.
The DVM configuration file, for example $FGLDIR/etc/fglprofile, can be automatically updated with FLM server details when installing Genero on a Unix™ platform, as long as the FLM is installed, and the option to use the FLM is selected at time of installation.
Values for the resources flm.server, flm.license.number, and flm.license.key are required if you want to use FLM.
Resource | Default Value | Description |
---|---|---|
flm.server | none | Name of the machine that holds the license service program. You must set this value to use Four Js License Manager from this machine. |
flm.license.number | none | Value of your current license number. (For example: XXX#XXXXXXXX) |
flm.license.key | none | Value of your current license key. (For example: YYYYYYYYYYYY) |
flm.service | 6399 | Service or port number for the communication between the local license controller and Four Js License Manager. This value should be the same as in the Four Js License Manager configuration file, $FLMDIR/etc/lmprofile. See Configuring the License Manager. |
flm.check | 10 | Number of iterations between two controls of the user list. Default is 10. |
flm.ps | ps -ae | Specifies the command that gives a process list for a
machine. This value is used to synchronize the real user list on the current machine with the
registered users list on Four Js License Manager. Warning: This entry is not used on
most platforms as the default value ps -ae is replaced by a call to an API. This
resource should not be set unless the internal implementation relying on OS specific API calls fail.
|