Java SDK Configuration and Usage
Within this guide, we will meticulously navigate the sequential procedure of enabling your LicenseSpring license by employing the LicenseSpring Java SDK.
As you progress through this tutorial, you will acquire the skills to initiate, deactivate, and verify licenses directly from your Java program.
Functions and methods used throughout this tutorial throw exceptions to understand any potential problems.
For more information about these, see Java Exception Handling.
To initialize the SDK you will need to fill in your application name and version, LicenseSpring API key, shared key and product code.
Both the API key and shared key can be found on your LicenseSpring account under Settings->Keys:
Your product code is located in your product list under "Configure Products":
Please, keep in mind that the product code field is case-sensitive.
When you have the necessary values, create the configuration.
Now you can initialize LicenseManager using this configuration object:
The license keys are located in "Licenses" section on the vendor platform:
To implement user-based licensing please refer to: User-Based Licensing.
To activate a license, create a ActivationLicense using the given key and call activation method.
Note: We immediately check our license after activating because activateLicense only activates the license on the LicenseSpring servers. The license check either creates/updates the local license file, depending on if it existed prior.
Deactivating a license unbinds the device from the license, and decrements the number of total activations.
Depending on the license transfer policy, this usually means that the license is freed up to be activated onto a new device.
Deactivating is done using the following method:
The local license is a copy of the license information that is saved on the end user's local computer. Users who have not activated the license on their end before will not have a local license. By default, the local license is stored: %USERPROFILE%\AppData\Local\LicenseSpring\”Product Code”\License.key.
See Local License File for more information.
If a device already has a license, and you try to activate another license on that device, for the same product, that newly activated license will override the existing license, deleting it from the device. This will be on the developer to make sure that they check if a license exists on the device before a new activation:
It is recommended to perform a local license check at application start to confirm that the local license file belongs to the current device and has not been transferred.
Note: It is also useful to check whether the local license file has been tampered with and whether the local license is still valid.
Online license check refreshes the local license with the data from LicenseSpring backend:
Below you can find a code sample that initializes the SDK, retrieves a local license or activates a new one, and performs the necessary checks.