ESB3002 Software Repackager Licensing User Guide
1 Confidentiality notice
This document is confidential and may not be reproduced, distributed or used for any purpose other than by the recipient for the assessment, evaluation and use of AgileTV products, unless written permission is given in advance by AgileTV.
2 About this document
This document covers an overview of the SW Repackager license model support. No prior knowledge about the system is assumed. Intended audiences include system administrators who install the system, operators who use it, and anyone who is interested in learning more about the product.
3 How to use this document
This document aims to be used as a foundation to build an understanding around the product. The document is to be used a guideline when working with the product. This document does not define any specific information on feature development in specific releases, please refer to “Release Notes”. Neither does this document define any applications relying on the specific product, please refer to “Application Notes”.
4 History
| Version | Date | Changes |
|---|---|---|
| A1 | 2021-04-12 | Initial version |
| A2 | 2022-01-11 | More details about each license variants |
| A3 | 2022-10-05 | Update license error behaviour |
| A4 | 2023-05-10 | Unify license package variants |
| A5 | 2024-02-21 | Unify installer variants |
| A6 | 2024-10-23 | Introduce sb-license type |
5 Basic license support
5.1 General information
The SW Repackager can run with three different kinds of licenses
- ScientaMedia: Requires an internet connection
- Convoy: Requires a Convoy installation, but no external internet
- Standalone: Requires neither internet nor Convoy
The actual license, must be acquired from Agile Content TAC, and the license type depends on the agreement with Agile Content.
5.2 Service configuration
For all license types the license file is: /etc/ew-repackager/license.json
After updating the file, the services must be restarted:
[root@esb3002 ~]# systemctl restart ew-repackager-license ew-repackager5.2.1 ScientaMedia and Convoy licenses
You may receive either a complete file (or a license_ref string). The license file must be replaced (or edited) accordingly.
For example:
{
"license_ref": "1209-company_name-esb3002-repackager_vod-123456789",
"service_name": "ew-repackager",
"status_query_interval" : "2m",
"loglevel": "DEBUG",
"validation_type": "offline"
}validation_type must be online for ScientaMedia, and offline for Convoy licenses.
5.2.2 Standalone license
In this case you will receive a complete file in a different format. Here the entire license file must be replaced without any editing.
5.2.3 Variant specific configuration
For Convoy licenses, the convoy-1 and IP to the Convoy nod must be added to /etc/hosts, manually.
5.3 License statuses
The table below briefly sums up the possible license statuses returned by the license server. Currently only an expired license will cause the SW Repackager to stop processing requests.
| Status | Description | Impact on running instances | Possible action |
|---|---|---|---|
| Valid | License is valid. | None. | None. |
| Concurrency Limit | The concurrency limit | Discard requests. | Contact TAC support. |
| of the running instances | HTTP 509 error will be returned | ||
| was exceeded. | |||
| Expired | The acquired license has | Discard requests. | Contact TAC support. |
| expired (reached its | HTTP 509 error will be returned | ||
| lifetime or was | |||
| invalidated). | |||
| Error | An unexpected error | None. If the SW Repackager | Restart the service. |
| occured. 3rd party | service detects this kind | If the problem | |
| service is | license status it ignores | persists contact | |
| inaccessibility or an | it and lets the service | TAC Support. | |
| internal error occured. | work as intended. |
5.4 Troubleshooting
For more information please try the following:
- The
ew-repackager-licenseservice log which can be viewed with journalctl.
[root@esb3002 ~]# journalctl -fu ew-repackager-license- Additional details can be found in the
repackaging.log.
[root@esb3002 ~]# tail -f /var/log/edgeware/ew-repackager/repackaging.log