|
Answers to developers' commonly asked questions about LM-X.
|
(Page 1 of 3)
«« |
Prev |
1 |
2 |
3 |
Next |
»»
|
There were 59 articles found in this category:
 Upgrading LM-X
To upgrade LM-X in order to get a newer version of the software, or after subscription renewal to avoid software expiration, follow the steps below. Download LM-X by logging into the X-Formation Support Portal and following the Download instructions. Unpack the downloaded distribution to a tem ...
- Licensing your software to run on virtual machines
LM-X detects most virtualization technologies, including VMWare, Microsoft Virtual Server, and VirtualBox. Virtual machine environments are typically undesirable for licensed software due to the inherent risk of overuse. With LM-X, you can choose to allow or prohibit your application to run in a ...
- Which hostid should I lock my license to?
The following table lists the hostid types that LM-X supports and indicates each type's level of security and flexibility, so you can decide which hostid type(s) work best for your needs. Hostid Type Security Flexibility Notes Hostname Low High Easy to move. Username Low High Easy to move ...
- Should I lock my license to only one hostid or use multiple hostids?
In most cases, locking to an Ethernet card, BIOS or harddisk hostid is enough. If you need more security, you may lock to multiple hostids using one of the following methods: Multiple hostids with 1:1 matching. For example, you might lock a feature to the license server machine hostname, Ethern ...
- Which hostid should I use to lock my floating license application to a particular license server machine?
A good choice for locking a floating license to a particular server machine is to use the Ethernet hostid (the MAC address of the Ethernet card). Almost all machines have an Ethernet card, and information about the Ethernet hostid is available on all platforms. For optimal security, locking to t ...
- Which hostid should I use to lock my node-locked license application to a particular machine?
A good choice for locking a node-locked license to a particular machine is to use the Ethernet hostid (the MAC address of the Ethernet card). Almost all machines have an Ethernet card, and information about the Ethernet hostid is available on all platforms. For optimal security, locking to the B ...
- Can LM-X detect virtual enviroment?
With LM-X you can allow or forbid to use your application in a virtual enviroment. LM-X detects most of virtualization technologies including VMWare, Microsoft Virtual Server, VirtualBox. Virtual machine environments are typically undesirable for use with software licensing. Normally, operating ...
- How does software protected by LM-X find a license file?
Every LM-X protected application has a search path for licenses. The application will search for licenses in the following order: 1. Preset path and/or automatic server discovery (this information is provided by your application vendor). 2. The environment variable VENDOR_LICENSE_PATH. The VEND ...
- Using dongles under Linux x64 with LM-X v3.3 and v3.31
For LM-X v3.3 and 3.31, we updated our dongle library from Hasp HL to Sentinel HASP v5.0. Our supplier, Aladdin, does not compile the dongle library under Linux x64 using the -fPIC flag. Unfortunately, this means that you cannot use our shared object liblmx-vendor.so together with dongles. To ma ...
- Providing demo versions of your software
Often, you may wish to provide potential customers with demo versions of your software. LM-X gives you a number of ways to supply such users with restricted versions of your software. This section describes some, but far from all, such options LM-X offers. You may find that employing a single m ...
- Using a pre-compiled LM-X SDK
Typically, the first time you use the LM-X SDK, you need to compile it using nmake or gnu make, depending on your platform. This one-time compilation of the SDK creates the security configuration file vendor.lmx (if it doesn't already exist) and compiles examples and platform-specific files. As ...
- LM-X v3.3 Release Notes
LM-X License Manager version 3.3 includes the following enhancements and fixes. Most of these changes 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 developm ...
- LM-X v3.3 now uses non-obfuscated hostids
With LM-X v3.3, hostids are no longer obfuscated, thereby making it easier to determine to what hardware item the license is locked and how the licensing is performed. For example, versions of LM-X previous to v3.3 used a 16-digit Ethernet hostid (the obfuscated MAC address of the Ethernet card) ...
- Can I specify username and hostname for web application checkouts?
By default, if the application is located on a web server and the client is a web browser, every license will be consumed by the same user (the web server), instead of a license being consumed for each individual client. You can override this behavior by specifying a custom username and hostname ...
- How many concurrent clients can LM-X support on Linux?
Under Linux for LM-X v3.3 and newer, the LM-X license server can support more than 10,000 concurrent clients. In order to allow the LM-X license server to use more sockets than the default 1024 for Linux, the Linux kernel must support epoll (introduced in Linux kernel 2.5.44), and you must raise ...
- Using CPU cores for node-locked licenses
Specifying CPU cores for node-locked licenses can be useful in cases such as high-tech computing and application virtualization. This license model enables you to base licensing on the customer's computing resource requirements, increasing the pricing depth for your software offerings. For examp ...
- LM-X v3.2 Release Notes
LM-X License Manager version 3.2 includes the following enhancements and fixes. Most of these changes 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 developm ...
- Using CPU cores for floating licenses
Specifying CPU cores for floating licenses can be useful in cases such as high-tech computing and application virtualization. This license model enables you to base licensing on the customer's computing resource requirements, increasing the pricing depth for your software offerings. For example, ...
- What are the requirements for initially compiling LM-X?
When compiling the LM-X SDK under Windows, one of the following is required: Visual Studio (Express, Standard, Pro or better) MinGW v4.3.x When compiling the LM-X SDK under Unix, GCC is required. In addition, when using Java, you will need to ship your application with a JNI dll, thus making ...
- How does LM-X provide compatibility between different versions?
LM-X is designed to be platform independent and work on a number of platforms. Therefore, you can easily create licenses on one platform and use them on another. Similarly, you can run license servers on one platform and license clients on another. Due to this design, there are seldom any cross- ...
(Page 1 of 3)
«« |
Prev |
1 |
2 |
3 |
Next |
»»
|
Search the Knowledgebase
Browse by Category or Article ID
