Device Administrator is used to manage licenses on automation servers.
The following features of an automation server need licenses.
To be able to use SmartDrivers on an automation server one license is needed for every SmartDriver that runs on the automation server.
To be able to use SNMP Notification on an automation server, a license is required.
For a stand-alone automation server, the license is local for the automation server and administered by Device Administrator.
In a multi-server system, you can use inherited licenses.
For more information, see Inherited Licenses .
To be able to create personal dashboards on an automation server, you need a license. Personal dashboards are used in WebStation.
For a stand-alone automation server, the license can be local for the automation server and administered by Device Administrator.
In a a multi-server system, you can use inherited licenses.
For more information, see Inherited Licenses .
To be able to use TimescaleDB on an automation server, a license is required.
For more information, see Inherited Licenses .
To be able to read and write to an MQTT broker from an MQTT client on an automation server, you need a license. For a stand-alone automation server, the license is local for the automation server and administered by Device Administrator.
In a multi-server system, you can use inherited licenses.
For more information, see Inherited Licenses .
Licenses are bought as products and delivered in Entitlements. An Entitlement is a container that can contain several products. The products contain the licenses and they can differ in quantity and contents.
Use this workflow to add licenses to automation servers using Device Administrator.
For more information, see Automation Server Licensing on Automation Servers Connected to Internet Workflow .
It is recommended to use HTTPS for the communication between Device Administrator and automation servers when you manage licenses.
For more information, see Certificates in Device Administrator .