LLS License End-User Management
The LLS service's license must be activated to use its Licensing API, a fully featured replacement for the cloud version of the Licensing API. As each instance is activated and managed via your Zentitle2 admin dashboard, you can securely deploy an LLS instance to any end-user customer.
This allows you to track who has what and in what state each instance of LLS is with your customers. It also allows you to treat each deployment like any other, with rights controlled centrally. This allows much better control of your products even in dark/offline environments—these can have time and feature limits just like any other form of deployment.
First, you deploy the LLS at the customer site, and then, as the final step, you transfer (export) the license/entitlements to that instance.
LLS is a standalone Zentitle product that can be activated like any other product on the platform using the activation code from the entitlement. Ask the Zentitle support team to configure an LLS license for you.
The person responsible for activating the LLS license (LLS admin) should have access to Zentitle2 and the Local License Server's user interface, which runs on http://localhost:6501/ui by default.
LLS License installation and activation at the end-user
LLS uses the offline activation flow because we assume the machine it runs on might not have internet access.
First, go to the Zentitle2 back end and check the status of your company's LLS.
In Zentitle2, go to the [Account Settings] -> [Local License Server] page and check the status of your Local License Server entitlement.
In this example, you have 1000 instances of LLS left to deploy.
Contact our team to add LLS to your subscription if no entitlement is available.
Now that you have an LLS entitlement and activations, you can start to deploy LLS and use the provided activation code on the right of the screen for any deployment.
The same activation code is used for every deployment - don't worry, the process is secure and will only allow the instances you want to be deployed and activated.
To deploy to the end-user environment, you must install and run the Docker-based Server Interface, as described on the previous document page.
First, run the LLS app. and go to the "license" section on the left-hand navigation.
Next, click on the green Activate button,
Then, paste in the activation code from the Zentitle2 dashboard (as above),
Then, set your custom server name.
We suggest that the server name be set as a reference to your client and location, e.g., Boeing-Inst1-CO, so you can easily recognize this LLS instance from the others.
Click on the Generate activation request button.
Copy or download the generated activation request.
Now go back to the Zentitle2 dashboard where you started.
Click the Enter Activation Request button below where you sourced the activation code in the right-hand panel.
Paste in the activation request token generated in the LLS Server Interface and generate the activation response.
Then, copy/download the activation response.
Now switch back to the LLS Server Interface and enter the activation response by pasting it into the dialog box or uploading the file.
Then click the Activate server button.
If the Activation page has been closed, follow step 2. and skip the activation request generation.
The LLS server's license should be active and visible in both the Server Interface and the Zentitle2 Servers section on the Local License Servers page.
This is the LLS Server showing the newly activated license.
This is the Zentitle2 dashboard showing the newly activated license.
Extending the time for an LLS instance - License Refresh
When the Local License Server's license is going to expire, it needs to be refreshed so that the LLS remains fully functional. This time period is called a "lease period," and you will see a lease expiration date when the LLS stops functioning on the end user site.
Thirty days before the LLS license expiration, your end-user will start getting a permanent warning about server expiration in the Server Interface.
To extend the license (lease) end time of the specific LLS instance, follow the instructions below.
In the Zentitle2 dashboard, find the LLS server name you want to "refresh" the license and click the Refresh button.
Copy or download the generated refresh request for the Local License Server's license.
Open the LLS Server Interface's License page.
Click the GREEN Refresh button on the LLS Server Interface's License page.
Then, paste the refresh request data generated on the Zentitle2 dashboard in the previous step.
Finally, click the BLUE Refresh button at the bottom of the page to verify that the Lease Expiry Date has been updated.
Removing LLS from a customer site - LLS License Deactivation
After the LLS license is deactivated, its Licensing API cannot be used anymore, and no entitlements can be imported into that LLS instance. License deactivation will delete all the imported entitlements and their data from the LLS database and change the entitlements' host back to the Cloud.
It should be performed only when no plan exists to use this server instance.
Follow the steps below to deactivate the license:
On LLS's License page, click on the Deactivate button.
Confirm the deactivation by clicking on the Deactivate & generate deactivation request button.
Make sure to download the deactivation request, as it cannot be generated twice. It's the only artifact that proves the LLS license has been deactivated and all entitlements deleted from its database.
Navigate to the Zentitle2 dashboard.
In the Servers section in Zentitle2, click the Deactivate button
Next, upload/paste the deactivation request provided by the Local License Server in the previous step.
Click the "deactivate" button.
You will then get a success dialog showing the server has been deactivated.
Now, you note that no servers are shown as the server has been removed from the system. If you had a lot of servers in the list, obviously, just one server would be deleted.
After successful license deactivation, all the entitlements hosted in the LLS will be automatically returned to the Cloud, and the server will no longer be available for entitlement export.
Last updated
