The master license is installed on a server Gateway. A master license allocates certain number of licenses to the connecting nodes. The License Server tab displays all the available licenses in a Server Gateway. The pooled licenses are installed in the configured License Server. The License clients request component licenses from the License Server.
In the "License Server" tab, the "Outstanding Licenses" table only shows pooled licenses because, for non-pooled ones, one key serves all gateways.
Therefore, in the "Licenses" tab of the License Server, all the keys that refer to the same product and don't have a counter associated are duplicates and can be removed, leaving just one.
If a license shows as "Unknown", update your Workbench to the latest version.
| Term | Description |
|---|---|
| Lease Duration in Seconds | The period of time in which acquired license is valid in a License Client node. If the License Client does not renew the lease for an acquired license before it expires, the License Client will disable the device using the license. For the acquired licenses that do not have the lease renewed, the License Manager will release the acquired licenses back to the pool of available licenses. |
| Renewal Interval in Seconds | The client's time interval to renew the license. Default is 3600 seconds. The lease duration will be reset, every time a gateway renews its license. |
| Gateway Usage | The number of gateway licenses used among the total number of available licenses. |
| Device Usage | The number of device licenses used. |
| HTTP Connection Usage | The number of HTTP Connection licenses used. |
The Outstanding License section displays information of all nodes that are License Clients. Each License Client is represented by a row in the table, as shown in the above figure:
| Column | Description |
|---|---|
| Client | The IP address of the License Client. |
| Hardware ID | The hardware identifier of the License Client. |
| Device Count | The number of devices currently acquired by the gateway. |
| HTTP Count | The number of http connection currently acquired by the gateway. |
| Expiration | The lease expiration for the acquired licenses. |
License Server node configuration
To configure a node as a License Server:
- From Licenses tab, add pooled component licenses to
the node.
The HTTP Server's https port is used for the communication between the License Client and the License Server. The HTTP Server must be configured and Started. For more information, see HTTP Server. - The License Server node can be configured to use
pooled component licenses. To do so,
configure the License Manager Address
and License Manager Port parameters to
point to itself.
The License Server node and the configured License Client nodes will share the pooled component licenses. - Configure the Lease Duration in Seconds parameter.
- Click Save.
License Server node run-time behavior
The License Server run-time behavior is:
- Lease component licenses to License Clients upon request.
- Maintain the information for each License Client node that has requested and acquired component licenses.
- If a License Client does not renew the lease of its acquired component licenses, within the Lease Duration in Seconds parameter, return the acquired license(s) back into the license pool.
System variables for license information
For notification purpose the license.XXX and license.pool.XXX System Variables are monitored by a trigger. The System Variable Get trigger action is used to retrieve specific system variable values and then, for example, forwarded to the appropriate personnel using the E-mail action.
Related Topics