Eclipse hawkBit™ - Update Server

Eclipse hawkBit is an domain independent back end solution for rolling out software updates to constrained edge devices as well as more powerful controllers and gateways connected to IP based networking infrastructure.

Build:

Docker:

Documentation

see hawkBit Documentation

Contact us

• Having questions about hawkBit? Check Stack Overflow
• Want to chat with the team behind hawkBit?
• Having issues with hawkBit? Open a GitHub issue.
• You can also check out our Project Homepage for further contact options.

Examples and Extensions

Next to the hawkBit core hosted here the project maintains as well examples and extension repositories.

hawkBit sandbox

We offer a sandbox installation that is free for everyone to try out hawkBit. However, keep in mind that the sandbox database will be reset from time to time. It is also not possible to upload any artifacts into the sandbox. But you can use it to try out the Management UI, Management API and DDI API. Keep in mind as well that you are not permitted to store any kind of personal data in the sandbox.

https://hawkbit.eclipseprojects.io/UI/login

In addition the following vendors offer free trial accounts for their hawkBit compatible products:

• Bosch IoT Rollouts
• Kynetics Update Factory

Device Integration

hawkBit exposes HTTP/JSon based Direct Device Integration (API) API that allow any update client to integrate quite easily.

The Eclipse Hara subproject aims to provide a reference agent software implementation of the Eclipse hawkBit device API. At the moment the project provides the hara-ddiclient Kotlin library that facilitates and speeds up the development of DDI API clients running on the JVM. The library is expected to soon see its first release under the Eclipse umbrella, and has been successfully used in production for years under its previous guise.

Additionally, the hawkBit project has the long term goal to provide Eclipse Hono integration which will provide connectivity through various IoT protocols and as a result will allow a wide range of clients to connect to hawkBit.

There are clients outside of the Eclipse IoT eco system as well, e.g.:

• SWupdate which is a Linux Update agent with focus on a efficient and safe way to update embedded systems.
• rauc-hawkbit-updater which is a hawkBit client for the RAUC update framework written in C/glib.
• rauc-hawkbit which is a python-based hawkBit client demo application and library for the RAUC update framework.
• hawkbit-rs provides a couple of Rust crates to help implement and test hawkBit clients.

Runtime dependencies and support

Java Runtime Environment: 1.8,11

SQL database

(Optional) RabbitMQ: 3.6,3.7,3.8

Getting Started

We are providing a Spring Boot based reference Update Server including embedded H2 DB for test and evaluation purposes. Run with docker:

docker run -d -p 8080:8080 hawkbit/hawkbit-update-server

Open the update server in your browser:

localhost:8080

See below for how to build and run the update server on your own. In addition we have a guide for setting up a complete landscape.

hawkBit (Spring boot) starters

Next to the Update Server we are also providing a set of Spring Boot Starters to quick start your own Spring Boot based application.

Clone, build and run hawkBit

Build and start hawkBit Update Server

git clone https://github.com/eclipse/hawkbit.git
cd hawkbit
mvn clean install
java -jar ./hawkbit-runtime/hawkbit-update-server/target/hawkbit-update-server-#version#.jar

Start hawkBit Device Simulator (optional)

git clone https://github.com/eclipse/hawkbit-examples.git
cd hawkbit-examples
mvn clean install

java -jar ./hawkbit-device-simulator/target/hawkbit-device-simulator-#version#.jar

Generate getting started data with the Management API example (optional)

java -jar ./hawkbit-example-mgmt-simulator/target/hawkbit-example-mgmt-simulator-#version#-exec.jar

Status and API stability

hawkBit is currently in ‘0.X’ semantic version. That is due to the need that there is still content in hawkBit that is in need for refactoring. That includes the maven module structure, Spring Boot Properties, Spring Boot auto configuration as well as internal Java APIs (e.g. the repository API ).

However, the device facing DDI API is on major version ‘v1’ and will be kept stable.

Server facing and DMF API are Management API are on v1 as well. However, we cannot fully guarantee the same stability during hawkBit’s 0.X development but we will try as best we can.