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.

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.

To learn more about how LuciadFusion licensing works, see Introduction to licensing.

Automatic installation

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. In the installed product, you can find the license file in the licenses folder.

Custom installation

The license file must be located in the classpath of your application. By default, it is named either development_license.txt or deployment_license.txt, corresponding to the license type.

Custom license name

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.

Add multiple license files

Optionally, you can add fallback license files, using sequentially numbered names like development_license1.txt, 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.

Use hardware keys or license servers

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.

Updating a license

When you need to update a license, because the existing license has expired for example, you can replace the existing license file with the new license file. When you installed the product from the automatic install.jar installer, you can find the license file in the licenses folder. In all other cases, the license file is located in the classpath of your application. By default, it is named either development_license.txt or deployment_license.txt, corresponding to the license type.

Testing and troubleshooting the license installation

To test your license installation, run one of the decoder samples. If the sample does not work, refer to Common startup and deployment errors and solutions.

Sample problems may also have to do with platform and Java support. See Hardware and software requirements for more information.