Pages in Admin-guide
Auth Server Configuration
The Auth Server component exposes a service endpoint implementing Eclipse Hono™’s Authentication API. Other services use this component for authenticating clients and retrieving a token asserting the client’s identity and corresponding authorities.
Hono Messaging Configuration
The Hono Messaging component exposes service endpoints implementing the south bound part of Eclipse Hono™’s Telemetry and Event APIs. The south bound API is used by protocol adapters to upload telemetry data and events to be forwarded to downstream consumers.
Device Registry Configuration
The Device Registry component provides an exemplary implementation of Eclipse Hono™’s Device Registration and Credentials APIs. Since Hono version 0.6 it also provides an exemplary implementation of the Tenant API.
Protocol adapters use these APIs to assert a device’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.
HTTP Adapter Configuration
The HTTP protocol adapter exposes a HTTP based API for Eclipse Hono™’s Telemetry and Event endpoints.
AMQP Adapter Configuration
The AMQP protocol adapter allows clients (devices and gateway components) that speaks AMQP 1.0 to publish telemetry messages and events to Eclipse Hono™’s Telemetry and Event endpoints.
MQTT Adapter Configuration
The MQTT protocol adapter exposes an MQTT topic hierarchy for publishing messages and events to Eclipse Hono™’s Telemetry and Event endpoints.
Kura Adapter Configuration
The Kura protocol adapter exposes an MQTT topic hierarchy allowing Eclipse Kura™ based gateways to publish control and data messages to Eclipse Hono™’s Telemetry and Event endpoints.
Hono Client Configuration
org.eclipse.hono.client.HonoClientfactory can be used to create specific clients for accessing services implementing one or more of Hono’s APIs.
AMQP 1.0 Messaging Network Configuration
The Dispatch Router, together with the Apache Artemis message broker, serves as the default AMQP 1.0 Messaging Network that is used in Hono’s example deployment as described in the Getting Started Guide.
The individual components of an Eclipse Hono™ installation, e.g. the protocol adapters, Hono Messaging, Hono Auth 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 Transport Layer Security (TLS) and how to configure it.
Monitoring & Tracing
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.