Data Hub On Edge
Data Hub is available on HiveMQ Edge and offers the same functionality as for the HiveMQ Enterprise broker. For detailed information, see our Data Hub Quick Start Guide.
Data Hub is a commercial feature and requires a license. Please reach out to our sales team to obtain one. |
Data Hub Configuration on HiveMQ Edge
When a valid license is present, Data Hub is fully enabled by default and requires no further configuration.
Individual components of Data Hub can be selectively disabled by explicitly setting the enabled
attribute to
false
in the following way:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<hivemq>
<modules>
<data-hub>
<data-validation>
<enabled>true</enabled>
</data-validation>
<behavior-validation>
<enabled>false</enabled>
</behavior-validation>
<scripting>
<enabled>true</enabled>
</scripting>
</data-hub>
</modules>
</hivemq>
The example configuration disables behavior validation while keeps data validation and scripting enabled.
The config also enables persistence to allow Data Hub to store data in case of a restart.
For more information on persistence, see Configuring Persistence.
Data Hub persistence
By default, Data Hub uses in-memory persistence, which means that all stored data is lost when HiveMQ Edge restarts. To preserve data across restarts, you must configure file-native persistence.
<?xml version="1.0"?>
<hivemq xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<persistence>
<mode>file-native</mode>
</persistence>
</hivemq>
Data Hub in the HiveMQ Edge REST API
The Data Hub portions of the HiveMQ REST API and the HiveMQ Edge REST API are identical. All available API interactions work the same way.
However, access to the HiveMQ Edge REST API requires JWT authorization. For more information on JWTs in HiveMQ Edge, see HiveMQ Edge API . An example to obtain a token is shown using cURL.