Date: Thu, 28 Mar 2024 23:25:20 +0100 (CET) Message-ID: <77100447.5306.1711664720037@confluence-server> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_5305_335787214.1711664720036" ------=_Part_5305_335787214.1711664720036 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The= information on this page refers to LM-X v5.4.1, which added search path ca= ching for network licenses. If you are using an older version of LM-X, plea= se refer to documentation for earlier versions. |
Every LM-X protected application h= as a search path for licenses. The application will search for licenses in = the following order.
Order= span> |
Search = Path |
---|---|
1 |
Preset = path and/or automatic server discovery (this information is provided by you= r application vendor). |
2 |
The env= ironment variable VENDOR_<= /em>LICENSE_PATH. The <= span style=3D"color: rgb(17,17,17);">VENDOR name is the same as that specified in the license fi= le. |
3 |
The gen= eric environment variable LMX_LICENSE_PATH, which is used by all applicatio= ns protected by LM-X. |
Note: Paths are sepa= rated with a semicolon ( ; ) and backslashes ( \ ) on Windows systems and a= colon ( : ) and forward slashes ( / ) on Unix systems.
Using the above search paths, the app= lication will try to find a license in the following order:
Note: LM-X attemp= ts to use local licenses before it tries to use counted network licenses to= optimize license utilization.
At each step, if no license is fou= nd in the specified source, the application will continue to the next sourc= e in the path. You may specify= unlimited multiple paths if desired; for example under Windows, LMX_LICENS= E_PATH=3D6200@server1;6200@server2;620= 0@server3. The protected application stops searching as s= oon as it finds a valid license.
For HAL servers, LM-X uses a cache= to check for server connection failures. If one of the HAL server co= nnections fail, LM-X will move the failed server to the end of the search p= ath list, and if the server comes back online, it will be checked for conne= ction again.
If another of the HAL servers does not respond during the connection st= ep, LM-X replaces the information in the cache. Information about the most = recent server connection failure is cached for 10 minutes, thereby decreasi= ng the average connectivity time in cases of restarting or simultaneously s= tarting the LMX client.