| <?xml version="1.0" encoding="utf-8" standalone="yes"?> |
| <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> |
| <channel> |
| <title>User Guide on Eclipse Hono&trade; Vers.: 1.3</title> |
| <link>https://www.eclipse.org/hono/docs/1.3/user-guide/</link> |
| <description>Recent content in User Guide on Eclipse Hono&trade; Vers.: 1.3</description> |
| <generator>Hugo -- gohugo.io</generator> |
| <language>en-us</language><atom:link href="https://www.eclipse.org/hono/docs/1.3/user-guide/index.xml" rel="self" type="application/rss+xml" /> |
| <item> |
| <title>MongoDB Based Device Registry</title> |
| <link>https://www.eclipse.org/hono/docs/1.3/user-guide/mongodb-based-device-registry/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://www.eclipse.org/hono/docs/1.3/user-guide/mongodb-based-device-registry/</guid> |
| <description>The MongoDB based Device Registry component provides implementations of Hono&rsquo;s Tenant API, Device Registration API and Credentials API. As such it exposes AMQP 1.0 based endpoints for retrieving the relevant information. Protocol adapters use these APIs to determine a device&rsquo;s registration status, e.g. if it is enabled and if it is registered with a particular tenant, and to authenticate a device before accepting any data for processing from it. |
| In addition to the above APIs, this Device Registry also exposes HTTP endpoints for managing the contents of the Device Registry according to the Device Registry Management API.</description> |
| </item> |
| |
| <item> |
| <title>File Based Device Registry</title> |
| <link>https://www.eclipse.org/hono/docs/1.3/user-guide/file-based-device-registry/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://www.eclipse.org/hono/docs/1.3/user-guide/file-based-device-registry/</guid> |
| <description><p>The Device Registry component provides exemplary implementations of Hono&rsquo;s <a href="https://www.eclipse.org/hono/docs/hono/docs/1.3/api/tenant/">Tenant API</a>, <a href="https://www.eclipse.org/hono/docs/hono/docs/1.3/api/device-registration/">Device Registration API</a> and <a href="https://www.eclipse.org/hono/docs/hono/docs/1.3/api/credentials/">Credentials API</a>.</p></description> |
| </item> |
| |
| <item> |
| <title>HTTP Adapter</title> |
| <link>https://www.eclipse.org/hono/docs/1.3/user-guide/http-adapter/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://www.eclipse.org/hono/docs/1.3/user-guide/http-adapter/</guid> |
| <description><p>The HTTP protocol adapter exposes HTTP based endpoints for Eclipse Hono™&rsquo;s south bound Telemetry, Event and Command &amp; Control APIs.</p></description> |
| </item> |
| |
| <item> |
| <title>MQTT Adapter</title> |
| <link>https://www.eclipse.org/hono/docs/1.3/user-guide/mqtt-adapter/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://www.eclipse.org/hono/docs/1.3/user-guide/mqtt-adapter/</guid> |
| <description><p>The MQTT protocol adapter exposes an MQTT topic hierarchy for publishing telemetry data and events to downstream consumers and for receiving commands from applications and sending back responses.</p></description> |
| </item> |
| |
| <item> |
| <title>AMQP Adapter</title> |
| <link>https://www.eclipse.org/hono/docs/1.3/user-guide/amqp-adapter/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://www.eclipse.org/hono/docs/1.3/user-guide/amqp-adapter/</guid> |
| <description><p>The AMQP protocol adapter allows clients (devices or gateway components) supporting the AMQP 1.0 protocol to publish messages to Eclipse Hono™&rsquo;s Telemetry, Event and Command &amp; Control endpoints.</p></description> |
| </item> |
| |
| <item> |
| <title>CoAP Adapter</title> |
| <link>https://www.eclipse.org/hono/docs/1.3/user-guide/coap-adapter/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://www.eclipse.org/hono/docs/1.3/user-guide/coap-adapter/</guid> |
| <description><p>The CoAP protocol adapter exposes <a href="https://tools.ietf.org/html/rfc7252">CoAP</a> based endpoints for Eclipse Hono™&rsquo;s south bound Telemetry, Event and Command &amp; Control APIs.</p></description> |
| </item> |
| |
| <item> |
| <title>Kura Adapter</title> |
| <link>https://www.eclipse.org/hono/docs/1.3/user-guide/kura-adapter/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://www.eclipse.org/hono/docs/1.3/user-guide/kura-adapter/</guid> |
| <description><p>The Kura protocol adapter exposes an MQTT topic hierarchy allowing Eclipse Kura™ based gateways to publish <em>control</em> and <em>data</em> messages to Eclipse Hono™&rsquo;s Telemetry and Event endpoints.</p></description> |
| </item> |
| |
| <item> |
| <title>Sigfox Adapter</title> |
| <link>https://www.eclipse.org/hono/docs/1.3/user-guide/sigfox-adapter/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://www.eclipse.org/hono/docs/1.3/user-guide/sigfox-adapter/</guid> |
| <description><p>The Sigfox protocol adapter exposes an HTTP endpoint for connecting up with |
| the Sigfox backend for publishing telemetry, events and use command &amp; control.</p></description> |
| </item> |
| |
| <item> |
| <title>Load Tests with JMeter</title> |
| <link>https://www.eclipse.org/hono/docs/1.3/user-guide/jmeter_load_tests/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://www.eclipse.org/hono/docs/1.3/user-guide/jmeter_load_tests/</guid> |
| <description><p>Eclipse Hono™ comes with an <a href="https://jmeter.apache.org">Apache JMeter</a> plugin which provides <em>samplers</em> that can be used in JMeter test plans to send and receive telemetry/event data.</p></description> |
| </item> |
| |
| <item> |
| <title>Device Registries</title> |
| <link>https://www.eclipse.org/hono/docs/1.3/user-guide/device-registry/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://www.eclipse.org/hono/docs/1.3/user-guide/device-registry/</guid> |
| <description>Eclipse Hono™ provides these device registry implementations: |
| File Based Device Registry |
| MongoDB Based Device Registry.</description> |
| </item> |
| |
| </channel> |
| </rss> |