For Standalone Applications

In standalone mode, the License Manager 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 Manager. Those variables which are only appropriate for a network configuration are ignored by the standalone application. The differences between the use of these variables in standalone and network mode is described below.

This variable can be used to specify the file that is used to store the standalone license codes used by the application.

This variable can be used to set the default location of the license code and log files.

The LSHOST environment variable is used on a computer that is running a protected application. It tells the application one or more License Manager computers to contact.

When the variable is set, the application will send directed calls to the License Managers that are in the LSHOST list along with broadcast to the network. The application will traverse the list of License Managers that respond starting from the first License Manager in the list and moving down the list. If none of the specified License Managers is found, then the application will pick the first License Manager that has responded to the broadcast. The wait for the License Manager response time when LSHOST is set is the same as the broadcast interval.

When this variable is not set, the application will perform a broadcast for any License Manager that can authorize the application to run.

Separate License Manager host names with a tilde (~).

NOTE   A colon (:) was used to separate License Manager host names up to RMS v8.2.x (Windows) and 8.4.x (UNIX).

You can use the LSFORCEHOST environment variable to force the application to look for only one License Manager computer. If the License Manager listed in the variable cannot be found, the application stops broadcasting and returns an error. LSFORCEHOST overrides the LSHOST environment variable or LSHOST/lshost file, and prevents a network broadcast from being done.

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 Manager. 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 are not meaningful in a standalone configuration and should not 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 standalone application.

NOTE   The LSPORT and the license queuing environment variables are only meaningful when used with a License Manager.

The LSUSGHOSTNAME environment variable is used to customize the hostname (where either RMS License Manager or standalone application is running) in the usage log to hide the real information. This environment variable is applicable to cloud-based usage log only.

An example

Operating System Example Outcome
Windows SET LSUSGHOSTNAME= CUSTOMHOSTNAME

Customizes the hostname
UNIX export LSUSGHOSTNAME= CUSTOMHOSTNAME