When running in stand-alone mode, the license server code that is part of the application can be configured using most of the environment variables. These variables are used in the same way as they would be with a network license server. Those variables which are only appropriate for a network configuration are ignored by the stand-alone application. The differences between the use of these variables in stand-alone and network mode is described below.
This variable can be used to specify the file that is used to store the stand-alone license codes used by the application.
This variable can be used to set the default location of the license code and log files.
Your application may have been built to support both stand-alone and network licensing. If it includes this capability then it will first try to obtain a stand-alone license using the license server capability that is built into the application. If unsuccessful then the application will try to obtain a network license by communicating with a license server located somewhere on the same subnet. You can disable the network broadcast by setting LSHOST to NO-NET. With this setting, the application only looks for a stand-alone license code.
This variable can be set to configure the application license management options in a way that is similar to its use on a server computer to configure a license server. It’s recommended that the -z and -x options be used to control the size of the usage file if logging has been enabled. The -u and -q options aren’t meaningful in a stand-alone configuration and shouldn’t be used. The remaining options are better set using a specific environment variable.
This variable can be used to specify the configuration file that is used with the stand-alone application.
Note: The LSPORT and the license queuing environment variables are only meaningful when used with a license server.