Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "BaSyx / Documentation / Components / DataBridge / Features / Protocol Integration / Hono"
< BaSyx | Documentation | Components | DataBridge | Features
(Created page with "= Hono = The Hono source can be integrated with DataBridge. == Configuration == To configure Hono consumer in DataBridge you need to provide the '''unique id''', and the Hono...") |
m (→Working Example) |
||
Line 26: | Line 26: | ||
== Working Example == | == Working Example == | ||
− | The integration example with Hono as a data source, JsonAta as a transformer, and AAS as a data sink is on [https://github.com/eclipse-basyx/basyx-databridge/tree/main/ | + | The integration example with Hono as a data source, JsonAta as a transformer, and AAS as a data sink is on [https://github.com/eclipse-basyx/basyx-databridge/tree/main/databridge.examples/databridge.examples.hono-jsonata-aas GitHub DataBridge Example]. |
Latest revision as of 03:09, 10 May 2023
Contents
Hono
The Hono source can be integrated with DataBridge.
Configuration
To configure Hono consumer in DataBridge you need to provide the unique id, and the Hono server details like host, port, along with user credentials, tenant id and device id.
Sample Configuration
[ { "uniqueId": "property1", "serverUrl": "http://hono.eclipseprojects.io", "serverPort": 15672, "userName": "consumer@HONO", "password": "verysecret", "tenantId": "mytenantid", "deviceId": "mytenantdevice" } ]
Similarly, you can configure multiple Hono consumers inside the configuration file.
Naming Convention
The name of the Hono consumer configuration file should be honoconsumer.json.
Working Example
The integration example with Hono as a data source, JsonAta as a transformer, and AAS as a data sink is on GitHub DataBridge Example.