Page tree
Skip to end of metadata
Go to start of metadata

You can set the environment variables listed in the table below as needed. Note that the environment variables available to you may be limited depending on whether your vendor has allowed their use as part of your software license.

All environment variables are undefined by default, and can be defined by setting the value to a number greater than 0, for example, 1. Any additional details on variable values are given in the Value column below.

Important: You must restart the client for changes to environment variables to take effect.

Variable name

Value

Description

VENDOR_LICENSE_PATH
or
LMX_LICENSE_PATH

The path to one or more LM-X managed licenses.

For example:
LMX_LICENSE_PATH=6200@server1,

This environment variable lets you set the path to the license file.

You may specify a particular vendor using VENDOR_LICENSE_PATH, where VENDOR is the name of the application vendor, as specified in the license file. LMX_LICENSE_PATH is a generic environment variable used by all applications protected by LM-X.

See Search paths for information on how an LM-X application searches for licenses.

You can set the license path using the LM-X End-user Configuration tool. Adding or removing license files from the path using the LM-X End-user Configuration tool, or manually, as described in section 3.3.2, Adding license files to the path manually.

VENDOR_AUTOMATIC_SERVER_DISCOVERY
or
LMX_AUTOMATIC_SERVER_DISCOVERY

A string that can be set to 1 (or any other integer) to enable running an automatic server discovery.

For example:
LMX_AUTOMATIC_SERVER_DISCOVERY=1

When this environment variable is set, automatic server discovery is enabled.
You may specify a particular vendor using VENDOR_AUTOMATIC_SERVER_DISCOVERY, where VENDOR is the name of the application vendor, as specified in the license file.

LMX_AUTOMATIC_SERVER_DISCOVERY is a generic environment variable used by all applications protected by LM-X.

You can set this environment variable in the same manner as described in Adding license files to the path manually.

VENDOR_AUTOMATIC_SERVER_DISCOVERY_SERVER
or
LMX_AUTOMATIC_SERVER_DISCOVERY_SERVER

A string that can be set to 1 (or any other integer) to enable running an automatic server discovery within a client.

For example:
LMX_AUTOMATIC_SERVER_DISCOVERY_SERVER=1

To disable automatic server discovery, unset the environment variable.

For example:

LMX_AUTOMATIC_SERVER_DISCOVERY_SERVER=

When this environment variable is set in combination with LMX_AUTOMATIC_SERVER_DISCOVERY (described above), the client will start responding to automatic server discovery requests issued by other clients. This enables the client to relay information about another server, thereby acting as a proxy. 

Only one Automatic Server Discovery server (either a license server or one client acting as a server) can be active at one time on one machine. This is handled automatically.

Example:
You may have a license server over the Internet and several clients on a local network. In this situation, the first client can enable the broadcast server and the other clients on the same local network will get the server address from the client machine instead of manually setting the server address. For example:

  1. Client A has enabled the LMX_AUTOMATIC_SERVER_DISCOVERY and LMX_AUTOMATIC_SERVER_DISCOVERY_SERVER flags.
  2. Client A checks out a license for Vendor A from Server A. Server A is located on a remote network, where automatic server discovery is not working due to firewall restrictions.
  3. Client B requests automatic server discovery to check out the Vendor A software.
  4. Client A gets the automatic server discovery request from Client B, and manually sets the address of the server, and then Client B gets the server information from Client A. 
    You may specify a particular vendor using VENDOR___AUTOMATIC_SERVER_DISCOVERY_SERVER, where VENDOR is the name of the application vendor, as specified in the license file. LMX_AUTOMATIC_SERVER_DISCOVERY_SERVER is a generic environment variable used by all applications protected by LM-X.

    You can set this environment variable in the same manner as described in Adding license files to the path manually.

VENDOR_BORROW
or
LMX_BORROW

The desired number of hours to allow license borrowing, from 1 - 8760.
or
<0 (e.g., -1) to allow early checkin of borrowed licenses.

Examples:
To set the borrow limit to 2 days:
LMX_BORROW=48
To allow early checkin:
LMX_BORROW=-1

Setting this environment variable to a number greater than 0 sets the number of hours for license borrowing.

Setting this environment variable to a number less than 0 enables early return of borrowed licenses.

You may specify a particular vendor using VENDOR_BORROW, where VENDOR is the name of the application vendor, as specified in the license file. LMX_BORROW is a generic environment variable used by all applications protected by LM-X.

You can set this environment variable in the same manner as described in Adding license files to the path manually.

VENDOR_BORROW_FORCE_RETURN
or
LMX_BORROW_FORCE_RETURN

A string that can be set to enable forcing a borrow return. Valid values are 0 or 1.

For example:
LMX_BORROW_FORCE_RETURN = 1

When this environment variable is set to 1 and LMX_BORROW=-1 (see above), the borrowed feature will be returned on the client side, even if there is no connection with the license server.

You may specify a particular vendor using VENDOR_BORROW_FORCE_RETURN, where VENDOR is the name of the application vendor, as specified in the license file.LMX_BORROW_FORCE_RETURN is a generic environment variable used by all applications protected by LM-X.

Caution: Use this variable carefully, because it can create an inconsistency between the client and the license server.

LMX_RANDOMIZE_PATH

A string that can be set to enable using a random path.

For example:
LMX_RANDOMIZE_PATH=1

When this environment variable is set, LM-X chooses a random path from a list for each server request. If you have multiple license servers, you can set this variable to balance the load amongst the servers.

You can set this environment variable in the same manner as described in Adding license files to the path manually.

VENDOR_EXTENDEDLOG
or
LMX_EXTENDEDLOG

The path to the extended client-side log.

For example:
LMX_EXTENDEDLOG=C:\LM-X\My_LM-X_Log_Directory\client.log

This environment variable lets you set the path and filename for the extended client-side log, which contains information about all client activity.

You may specify a particular vendor using VENDOR_EXTENDEDLOG, where VENDOR is the name of the application vendor, as specified in the license file. LMX_EXTENDEDLOG is a generic environment variable used by all applications protected by LM-X.

Important: Using extended logging delays checkouts up to 15 seconds, because it gathers more information about environment than when using normal logging.

You can set this environment variable in the same manner as described in Adding license files to the path manually.

VENDOR_CONNECTION_TIMEOUT
or
LMX_CONNECTION_TIMEOUT

The desired number of seconds, from 1 - unlimited.
The default value is 30.

For example:
LMX_CONNECTION_TIMEOUT=10

This environment variable lets you adjust the connection timeout setting. The connection timeout is set to 30 seconds by default unless you set it to a different value using this environment variable.

Increasing the timeout value can be useful for highly loaded networks. For example, if you set LMX_CONNECTION_TIMEOUT = 60, the client can wait up to 60 seconds before timeout.

You may specify a particular vendor using VENDOR_CONNECTION_TIMEOUT, where VENDOR is the name of the application vendor, as specified in the license file. LMX_CONNECTION_TIMEOUT is a generic environment variable used by all applications protected by LM-X.

You can set this environment variable in the same manner as described in Adding license files to the path manually.

VENDOR_PROJECT
or
LMX_PROJECT
 

A string specifying a project name.

For example:
LMX_PROJECT=Doorlatch_Design

This environment variable lets you set a project name for which all or vendor-specific LM-X licensed applications are being used. The project name is reported in lmxendutil -licstat. (See LM-X End-user utility.)

This lets you track for what purpose the application was used. For example, an application may be used for three different projects being run under different departments. Tracking which of the three projects the application was used for can help with accurate cost splitting amongst the projects.

VENDOR_QUEUE
or
LMX_QUEUE

A string that can be set to enable license queuing.

For example:
LMX_QUEUE=1

This environment variable enables license queuing for all checkout requests.

You may specify a particular vendor using VENDOR_QUEUE, where VENDOR is the name of the application vendor, as specified in the license file. LMX_QUEUE is a generic environment variable used by all applications protected by LM-X.

You can set this environment variable in the same manner as described in Adding license files to the path manually.

TMPDIR

A string specifying a path.

For example:
TMPDIR=/var/tmp

This system environment variable lets you specify the directory to be used for temporary files.

You can set TMPDIR before running your LM-X licensed application if you know in advance that you will not have access to /tmp directory.

TMPDIR affects UNIX platforms only.