| <?xml version="1.0" encoding="utf-8" standalone="yes"?> |
| <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> |
| <channel> |
| <title>Admin Guide on Eclipse Hono&trade; Vers.: dev</title> |
| <link>https://www.eclipse.org/hono/docs/dev/admin-guide/</link> |
| <description>Recent content in Admin Guide on Eclipse Hono&trade; Vers.: dev</description> |
| <generator>Hugo -- gohugo.io</generator> |
| <language>en-us</language><atom:link href="https://www.eclipse.org/hono/docs/dev/admin-guide/index.xml" rel="self" type="application/rss+xml" /> |
| <item> |
| <title>Common Configuration</title> |
| <link>https://www.eclipse.org/hono/docs/dev/admin-guide/common-config/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://www.eclipse.org/hono/docs/dev/admin-guide/common-config/</guid> |
| <description><p>Many Hono components support a common set of configuration options. This section |
| describes those options.</p></description> |
| </item> |
| |
| <item> |
| <title>Auth Server Configuration</title> |
| <link>https://www.eclipse.org/hono/docs/dev/admin-guide/auth-server-config/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://www.eclipse.org/hono/docs/dev/admin-guide/auth-server-config/</guid> |
| <description><p>The Auth Server component exposes a service endpoint implementing Eclipse Hono™&rsquo;s <a href="https://www.eclipse.org/hono/docs/hono/docs/dev/api/authentication/">Authentication</a> API. Other services use this component for authenticating clients and retrieving a token asserting the client&rsquo;s identity and corresponding authorities.</p></description> |
| </item> |
| |
| <item> |
| <title>MongoDB Based Device Registry Configuration</title> |
| <link>https://www.eclipse.org/hono/docs/dev/admin-guide/mongodb-device-registry-config/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://www.eclipse.org/hono/docs/dev/admin-guide/mongodb-device-registry-config/</guid> |
| <description>The MongoDB based Device Registry component provides an implementation of Eclipse Hono™&rsquo;s Device Registration, Credentials and Tenant APIs. 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, this Device Registry also provides an implementation of Device Registry Management APIs for managing tenants, registration information and credentials of devices.</description> |
| </item> |
| |
| <item> |
| <title>JDBC Based Device Registry Configuration</title> |
| <link>https://www.eclipse.org/hono/docs/dev/admin-guide/jdbc-device-registry-config/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://www.eclipse.org/hono/docs/dev/admin-guide/jdbc-device-registry-config/</guid> |
| <description>The JDBC based Device Registry components provides an implementation of Eclipse Hono™'s Device Registration, Credentials and Tenant APIs. 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, this Device Registry also provides an implementation of Device Registry Management APIs for managing tenants, registration information and credentials of devices.</description> |
| </item> |
| |
| <item> |
| <title>File Based Device Registry Configuration</title> |
| <link>https://www.eclipse.org/hono/docs/dev/admin-guide/file-based-device-registry-config/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://www.eclipse.org/hono/docs/dev/admin-guide/file-based-device-registry-config/</guid> |
| <description><p>The File based Device Registry component provides an exemplary implementation of Eclipse Hono™&rsquo;s <a href="https://www.eclipse.org/hono/docs/hono/docs/dev/api/device-registration/">Device Registration</a>, <a href="https://www.eclipse.org/hono/docs/hono/docs/dev/api/credentials/">Credentials</a>, <a href="https://www.eclipse.org/hono/docs/hono/docs/dev/api/tenant/">Tenant</a> and <a href="https://www.eclipse.org/hono/docs/hono/docs/dev/api/device-connection/">Device Connection</a> APIs.</p> |
| <p>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.</p></description> |
| </item> |
| |
| <item> |
| <title>Configuring the Command Router Service</title> |
| <link>https://www.eclipse.org/hono/docs/dev/admin-guide/command-router-config/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://www.eclipse.org/hono/docs/dev/admin-guide/command-router-config/</guid> |
| <description><p>The Command Router service provides an implementation of Eclipse Hono™&rsquo;s <a href="https://www.eclipse.org/hono/docs/hono/docs/dev/api/command-router/">Command Router API</a>.</p> |
| <p><em>Protocol Adapters</em> use the <em>Command Router API</em> to supply information with which a Command Router service component can route command &amp; control messages to the protocol adapters that the target devices are connected to.</p></description> |
| </item> |
| |
| <item> |
| <title>Configuring the Device Connection Service</title> |
| <link>https://www.eclipse.org/hono/docs/dev/admin-guide/device-connection-config/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://www.eclipse.org/hono/docs/dev/admin-guide/device-connection-config/</guid> |
| <description><p>The Device Connection service provides an implementation of Eclipse Hono™&rsquo;s <a href="https://www.eclipse.org/hono/docs/hono/docs/dev/api/device-connection/">Device Connection API</a>.</p> |
| <p>Protocol adapters use this API to store and retrieve information about the gateway that a device is using to connect to Hono&rsquo;s protocol adapters. This information is necessary for routing commands to the particular protocol adapter instance that the gateway used by the device is connected to.</p></description> |
| </item> |
| |
| <item> |
| <title>HTTP Adapter Configuration</title> |
| <link>https://www.eclipse.org/hono/docs/dev/admin-guide/http-adapter-config/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://www.eclipse.org/hono/docs/dev/admin-guide/http-adapter-config/</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 Configuration</title> |
| <link>https://www.eclipse.org/hono/docs/dev/admin-guide/mqtt-adapter-config/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://www.eclipse.org/hono/docs/dev/admin-guide/mqtt-adapter-config/</guid> |
| <description><p>The MQTT protocol adapter exposes an MQTT topic hierarchy for Eclipse Hono™&rsquo;s south bound Telemetry, Event and Command &amp; Control APIs.</p></description> |
| </item> |
| |
| <item> |
| <title>AMQP Adapter Configuration</title> |
| <link>https://www.eclipse.org/hono/docs/dev/admin-guide/amqp-adapter-config/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://www.eclipse.org/hono/docs/dev/admin-guide/amqp-adapter-config/</guid> |
| <description><p>The AMQP protocol adapter exposes AMQP based endpoints for Eclipse Hono™&rsquo;s south bound Telemetry, Event and Command &amp; Control APIs.</p></description> |
| </item> |
| |
| <item> |
| <title>CoAP Adapter Configuration</title> |
| <link>https://www.eclipse.org/hono/docs/dev/admin-guide/coap-adapter-config/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://www.eclipse.org/hono/docs/dev/admin-guide/coap-adapter-config/</guid> |
| <description><p>The CoAP protocol adapter exposes CoAP based endpoints for Eclipse Hono™&rsquo;s south bound Telemetry, Event and Command &amp; Control APIs.</p></description> |
| </item> |
| |
| <item> |
| <title>Kura Adapter Configuration</title> |
| <link>https://www.eclipse.org/hono/docs/dev/admin-guide/kura-adapter-config/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://www.eclipse.org/hono/docs/dev/admin-guide/kura-adapter-config/</guid> |
| <description><p>The Kura protocol adapter exposes an MQTT topic hierarchy allowing Eclipse Kura™ based gateways to access Eclipse Hono™&rsquo;s |
| south bound Telemetry, Event and Command &amp; Control APIs.</p></description> |
| </item> |
| |
| <item> |
| <title>Hono Client Configuration</title> |
| <link>https://www.eclipse.org/hono/docs/dev/admin-guide/hono-client-configuration/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://www.eclipse.org/hono/docs/dev/admin-guide/hono-client-configuration/</guid> |
| <description><p>The <code>org.eclipse.hono.client.HonoConnection</code> factory can be used to create AMQP 1.0 connections to Hono&rsquo;s service components.</p></description> |
| </item> |
| |
| <item> |
| <title>Hono Kafka Client Configuration</title> |
| <link>https://www.eclipse.org/hono/docs/dev/admin-guide/hono-kafka-client-configuration/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://www.eclipse.org/hono/docs/dev/admin-guide/hono-kafka-client-configuration/</guid> |
| <description>Protocol adapters can be configured to use Kafka for the messaging. The Kafka client used there can be configured with environment variables and/or command line options. |
| Tech preview The support of Kafka as a messaging system is currently a preview and not yet ready for production. The implementation as well as its APIs may change with the next version. Configure for Kafka based Messaging The selection of whether to use AMQP or Kafka for the messaging can be configured on the tenant.</description> |
| </item> |
| |
| <item> |
| <title>AMQP 1.0 Messaging Network Configuration</title> |
| <link>https://www.eclipse.org/hono/docs/dev/admin-guide/amqp-network-config/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://www.eclipse.org/hono/docs/dev/admin-guide/amqp-network-config/</guid> |
| <description><p>The <em>Qpid Dispatch Router</em>, together with the <em>Apache Artemis</em> message broker, serves as the default <em>AMQP 1.0 Messaging Network</em> that is used in Hono&rsquo;s example deployment as described in the <a href="https://www.eclipse.org/hono/docs/hono/docs/dev/deployment/">Deployment Guides</a>.</p></description> |
| </item> |
| |
| <item> |
| <title>Secure Communication</title> |
| <link>https://www.eclipse.org/hono/docs/dev/admin-guide/secure_communication/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://www.eclipse.org/hono/docs/dev/admin-guide/secure_communication/</guid> |
| <description><p>The individual components of an Eclipse Hono™ installation, e.g. the protocol adapters, <em>AMQP Messaging Network</em>, <em>Hono Auth</em> etc., and the clients attaching to Hono in order to send and receive data all communicate with each other using AMQP 1.0 over TCP. The Hono components and the clients will usually not be located on the same local network but will probably communicate over public networking infrastructure. For most use cases it is therefore desirable, if not necessary, to provide for confidentiality of the data being transferred between these components. This section describes how Hono supports confidentiality by means of <em>Transport Layer Security</em> (TLS) and how to configure it.</p></description> |
| </item> |
| |
| <item> |
| <title>Monitoring & Tracing</title> |
| <link>https://www.eclipse.org/hono/docs/dev/admin-guide/monitoring-tracing-config/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://www.eclipse.org/hono/docs/dev/admin-guide/monitoring-tracing-config/</guid> |
| <description><p>The individual components of an Eclipse Hono™ installation need to work together in order to provide their |
| functionality to devices and applications. Under normal circumstances these interactions work flawlessly. |
| However, due to the nature of distributed systems, any one (or more) of the components may crash or become otherwise |
| unavailable due to arbitrary reasons. This page describes how Hono supports operations teams by providing insights |
| into the individual service components and their interactions with each other by means of reporting metrics and |
| tracing the processing of individual messages through the system.</p></description> |
| </item> |
| |
| <item> |
| <title>Device Registry Configurations</title> |
| <link>https://www.eclipse.org/hono/docs/dev/admin-guide/device-registry-config/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://www.eclipse.org/hono/docs/dev/admin-guide/device-registry-config/</guid> |
| <description>The configuration of Eclipse Hono™s Device Registry implementations for the File Based Device Registry and for the MongoDB Based Device Registry.</description> |
| </item> |
| |
| </channel> |
| </rss> |
