camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jens Reimann <>
Subject Contributing a set of IoT related components
Date Thu, 06 Apr 2017 09:33:44 GMT
Hi everyone,

As just mentioned on IRC, I would like to contribute a bunch of IoT related
Camel components I made to Apache Camel. Those are independent of each
other, so please consider them separately.


## Milo

Eclipse Milo is an OPC UA protocol implementation. This component provides
a client and server integration of Milo for Camel. [1]

OPC UA is a protocol for industrial IoT [2]

## IEC 60870

This component wraps the Eclipse NeoSCADA IEC 60870-5-104 protocol
implementation into a Camel component. It provides client and server [3].
IEC 60870 is an industrial IoT protocol mainly used in the energy sector.

## OpenTSDB Collector

A Camel component for collecting telemetry data in OpenTSDB [5]. OpenTSDB
is a time series database used to store large amount of telemetry data [6].

## Why at Apache Camel?

NeoSCADA and Milo are both Eclipse projects under the IoT top level
project. That would mean splitting up those Camel components under two
different projects. When Camel updates both projects would need to be

On the other hand Apache Camel seems to me like the integration point,
Camel would consume Milo and NeoSCADA protocol implementations and provide
the Camel components for them. But at a single location.


So what do you think?





Jens Reimann
Senior Software Engineer / EMEA ENG Middleware
Werner-von-Siemens-Ring 14
85630 Grasbrunn
phone: +49 89 2050 71286

Red Hat GmbH,,
Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB
Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham,
Michael O'Neill

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message