...
To upgrade the server at the end user site :
...
simply uninstall and remove the old LM-X license server and install the new one obtained from your software vendor.
Important: When upgrading LM-X to a newer version, note the following compatibility considerations:
Existing deployed client applications and existing license files will continue to work with the new version. However, new license files cannot be used by older applications.
If you distribute floating licenses, your end users must also upgrade their LM-X license server, because the old license server cannot support new licenses (i.e., we cannot provide "future" compatibility). In most cases, borrowed licenses will also continue to work. However, borrowed licenses rely on using Secure Store, so if Secure Store is changed (which is rare), borrowed licenses will not be backward compatible.
- If you are using any external shared libraries—for example, for .NET, Java, etc.—you must also deploy these new versions with your software.
- When generating network licenses for clients using releases older than v3.5, use the switch xmllicgen -base32 to enable older clients to continue to work with v3.5.
- You can install multiple versions of LM-X, but do not mix files between different distributions, as this can cause problems such as compilation or runtime errors. The only file that can safely be shared between platforms is the security configuration file, security_config.lmx.
Compatibility switches
You can use special switches for the License Generator to maintain compatibility after breaking changes:
- To use the new license generator to generate a license file for a v3.3 license server, but for pre-v3.3 license clients, use the switch xmllicgen -oldhostid.
Be sure to read the release notes for all new LM-X releases to learn of any issues that may affect version compatibility.