Page History

...

To do this, you copy the vendor library liblmxvendor.dll (for Windows) or liblmxvendor.so (for Unix) for the desired platform to your Windows or Unix machine, and run the lmxdev command (see Lmxdev developer tool) to embed the security configuration information into the liblmxvendor.dll/so file. You then ship the LM-X End-user Tools installer (lmx-enduser-tools_version.msi/sh), which also installs the license server and the vendor library to the customer.

This procedure needs to be done only once, for each platform on which you will distribute your software but do not have a physical machine.

...

1. Copy the liblmxvendor.dll/so file from the LM-X distribution to the machine that contains the lmxdev executable.
   
   
2. Run lmxdev using the -embedsecurityconfig option, as follows:
   
   C:\lm-x\win32_x86\no_security_config> ..\lmxdev.exe -embedsecurityconfig ..\..\config\xformation.lmx liblmxvendor.dll
LM-X Developer Tool v3.3
Copyright (C) 2002-2010 X-Formation. All rights reserved.
Licensed to X-FORMATION
Security configuration successfully embedded!
   
   
3. Run lmxdev again using the -embedlicense option, as follows:
   
   lmxdev -embedlicense ../config/lmx.lic liblmxvendor.dll
LM-X Developer Tool v4.4.0
Copyright (C) 2002-2012 X-Formation. All rights reserved.
License file successfully embedded!
   
   
4. Send the LM-X End-user Tools installer and the liblmxvendor.dll/so file to your customers who wish to run the license server on that particular platform.

Note that failure to embed the security configuration file in the liblmxvendor.dll/so file will result in errors such as the following when the user attempts to start up the license server:

[2010-01-16 21:28:17] FAIL: Vendor security configuration is not embedded!