The following files should be distributed to end users:
Component | Description | |
|---|---|---|
Windows Filename(s) | Unix Filename(s) | |
lmx-serv.exe lmx-serv.cfg | lmx-serv lmx-serv.cfg | License server for end users along with its configuration file. The license server can either be run from a console or as a service (on Windows) or daemon (on Unix). For more information, see LM-X License Server. |
liblmxvendor.dll | liblmxvendor.so/dylib | Vendor-specific file containing all vendor-implemented extensions to the license server. This file must be distributed to end users along with the license server file. On Windows, the liblmxvendor.dll file must be placed in the same directory as the license server. On Unix, the startup scripts provided in $platform/enduser should be used for starting the LM-X License Server. |
lmxendutil.exe | lmxendutil | End-user command line utility. For more information, see LM-X end-user utility. |
lmxconfigtool.exe | N/A | End-user GUI configuration tool (Windows only). For more information, see LM-X End-user Configuration Tool. |
With most installers under Windows, you can automate the license server registration as a service, because the license server is installed through a set of command line parameters. Also see Performing a silent installation. To automate license server registration, make sure your installer first copies the file to its destination, and then executes it with the appropriate parameters to install it as a service. If the installation is successful, the return code is zero; otherwise, it is non-zero.
In addition to the files listed above, vendors can provide additional SDK utilities to end users as needed to reset their system clock, reset their trial period, and resolve issues related to borrowed licenses.