To run LuciadFusion, you need a license file that is provided to you by Luciad’s Customer Services department.
LuciadFusion supports two types of licenses: developer licenses and end user licenses. A developer license can be used with the original LuciadFusion jars, in the development phase of your project. It allows you to write, compile, and run LuciadFusion applications. An end user license can only be used with finalized LuciadFusion applications. It allows you to run LuciadFusion applications that have been obfuscated.
on license terminology. The term developer license is used interchangeably with the term development license throughout the product, while the end user license may also be referred to as the deployment license.
In a typical installation, you installed LuciadFusion from the automatic
install.jar installer. The license has been installed automatically from the file location you specified during the installation process.
The license file must be located in the class path of your application. By default, it is named either
deployment_license.txt, corresponding to the license type.
Alternatively, you can use a custom license name. In that case, you must pass the license name to the JVM through the
luciad.license JVM parameter.
Optionally, you can add fallback license files, using sequentially numbered names like
development_license2.txt, and so on. If a license file is not accepted, because of an incorrect IP address or a missing iButton for instance, the
next alternative license file is checked.
This fallback mechanism does not work when the number of licenses exceeds the permitted number of floating licenses.
Depending on your agreement, the license can require a hardware key or a license server.
For hardware key instructions, see Installing the license hardware key.
For license server instructions, see How to install and start the license server for floating licenses.
To automate the startup of the license server, check How to run a license server at startup.
To test your license installation, run one of the decoder samples. If the sample does not work, refer to Common license-related problems and error messages.
Sample problems may also have to do with platform and Java support. See Hardware and software requirements for more information.