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 Edgeware products, unless written permission is given in advance by Edgeware AB.

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 References

[1] License generation in Xops and ScientaMedia for SW Licenses

5 Basic license support

5.1 General information

The SW Repackager supports a basic form of license validation. It communicates with an external 3rd party service which keeps track of the number of concurrent active instances of a SW Repackager service and the assigned license validity.

First the license must be registered by Edgeware TV and published. It is accessible via License & SW portal. The SW Repackager only uses obtained license reference and has no knowledge of the license details. For more information about license generation please refer to [1].

5.2 Customizations

The SW Repackager is shipped with one license support variant, which sends requests to backend for verifying the license. To switch between Convoy CMS and Scienta Media backend, please refer to the parameter validation_type in Service configuration.

5.3 Service configuration

To properly configure the SW Repackager service the following configuration must be placed in the /etc/ew-repackager/license.json

{
    "license_ref": "1209-company_name-esb3002-repackager_vod-fhrODMD671HDWWd",
    "service_name": "the_name",
    "status_query_interval" : "2m",
    "loglevel": "DEBUG",
    "validation_type": "offline"
}

where:

After applying the new configuration, ew-repackager-license and services must be restarted

[root@esb3002 ~]#  systemctl restart ew-repackager-license

5.3.1 Variant specific configuration

For the validation method offline, the convoy-1 name to IP mapping must be added to /etc/hosts, manually.

5.4 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.5 Troubleshooting

For more information please try the following:

[root@esb3002 ~]#  journalctl -fu ew-repackager-license
[root@esb3002 ~]#  tail -f /var/log/edgeware/ew-repackager/repackaging.log