| User Opinions (1 vote) |
100%
0%
|
|
Thank you for rating this answer.
|
Article ID: 291
Last Updated: 10th May 2011 08:46:53 am
LM-X License Manager version 3.7 includes many fixes and enhancements. The fixes made in this release, listed below, were made in response to customer feedback. For more information about how we incorporate customer feedback into our development process, see our Knowledgebase article, "Customer-driven development."
LM-X v3.7 includes the following enhancements.
Issue #
|
Description |
| LMX-60 |
A new feature setting, REPLACES, lets you replace one license with another license. By replacing an old license with a new license, this setting ensures that customers can no longer use the old license. |
| LMX-541 |
A new environment variable, LMX_AUTOMATIC_SERVER_DISCOVERY_SERVER, can be set to enable a client to query other clients to find a server that is serving licenses for the same vendor. This environment variable is used in addition to LMX_AUTOMATIC_SERVER_DISCOVERY. |
| LMX-676 |
A new LMX_SetOption flag, LMX_OPT_HOSTID_CACHE_CLEANUP_INTERVAL, lets you control the cache cleanup interval. Setting this flag appropriately helps to avoid devices being used as hostids because they were cached. For example, a user could make a checkout using a dongle, then move the dongle to another computer and use it again while the dongle hostid is cached. |
LMX-807
|
You can now use LMX_GetLicenseInfo to obtain token dependencies for token-based features. |
LMX-913
|
It is now possible to refresh borrow. The client computer can borrow a license or return the license early using a normal checkout with the new environment variable LMX_BORROW_FORCE_RETURN enabled. Then, if a feature is borrowed for more than one hour, and the client reestablishes a connection with the license server, the client will refresh the borrow time. |
LMX-917
|
Support IPv6 only. |
LMX-922
|
Heartbeat callbacks are now called whenever they are set, on each heartbeat, regardless whether automatic heartbeats are enabled. |
LMX-924
|
A new LMX_SetOption flag, LMX_OPT_ALLOW_MULTIPLE_SERVERS, lets you switch between using one server or using multiple servers simultaneously during checkout. If this flag is enabled, each feature can be checked out from a separate server. |
LMX-927
|
A new API function, LMX_Putenv, lets you change environment variables. This function is intended a) to ensure that environment variable changes are properly propagated to the LM-X client for the LM-X- DLL library on Windows; or b) when using Java, which does not support simple manipulation of environment variables. Otherwise, the putenv function included in the C API can be used. |
| LMX-949 |
Support for using more than one HASP dongle at once. |
LMX-951
|
Support for Visual Studio 2010 Service Pack 1 (VS2010 SP1).
|
| LMX-981 |
Make licenses smaller by reducing number of new lines. |
LM-X v3.7 includes the following fixes.
Issue #
|
Description |
| LMX-896 |
Bug in Grace licensing. |
| LMX-898 |
Bugs with HAL messages. |
| LMX-901 |
Remove Mac OS X 10.4 support. |
| LMX-903 |
Problems with automatic heartbeat callbacks. The connection lost callback is now called each time the connection to the license server is lost and heartbeats are failing. |
LMX-905
|
In previous releases, the number of failed heartbeats was per client, so if the client was connected to multiple license servers, it created inconsistencies. Now, the number of failed heartbeats is separate for each licenses server, so the number will change only for the server for which heartbeats failed. |
| LMX-910 |
Problems with system serial encoding. |
| LMX-915 |
LM-X server crashes with segmentation fault with incorrect settings. |
| LMX-928 |
Server callbacks gave feature names in lowercase instead of the original case; e.g., "GlobalZoneAM" was printed as "globalzoneam." |
| LMX-930 |
Inconsistencies with lmxendutil -removeuser behavior. |
| LMX-945 |
License holding bug. |
| LMX-963 |
Make IPv6 errors (e.g., "FAIL: Unable to set socket to IPv6 only") conditional, so that the server does not stop. |
| LMX-979 |
Missing line in log for extended logging. |
|