You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 25 Next »

The information on this page refers to LM-X v4.4.5 and newer, which added the ability to compile a clean SDK. If you are using an older version of LM-X, refer to documentation for v4.4.4 and earlier. 

You install the LM-X SDK using an installation program (for both Windows and Unix), which will let you automatically:

  • Install and compile the SDK
  • Obtain the license file, copy it to the proper directory, and activate the license
  • Copy the security_config.lmx file from a previous LM-X installation to the proper directory
  • Navigate to the installation directory and execute the makefile

The installer places the LM-X license file (lmx.lic) in the config directory. The license file contains the software expiration date (after which xmllicgen will not generate new licenses) and the platforms on which you can compile and run LM-X. The installer will activate the LM-X license for you, or you can activate it manually as described in our Knowledgebase article, Activating licenses using License Activation Center. Note that after each runtime execution, some files will be written to the temp directory and, like any files in the temp directory, can be removed after execution if desired.

Upon first compilation of the LM-X SDK, the LM-X security configuration file (security_config.lmx) is automatically created in the config directory. This file holds various security-related parameters, and is used to create license files and embed the security configuration into the license server and client libraries.

Important: You must reuse this security configuration file for the lifetime of your application. When updating to new builds of LM-X or compiling LM-X on multiple platforms, the installer will let you choose an existing security configuration file. If you do not choose an existing security configuration file while running the installer, you must manually place the file in the config directory after installing the SDK.

See also Performing a silent installation.

  • No labels