Getting Started

Introduction

This guide is intended to give a quick overview over the most prominent workflows of Bosch IoT Rollouts. Each workflow is documented using screencasts and code snippets to allow an easy reproduction. The following workflows are covered:

The workflows build up on one another, so it is possible to go through successive. However, it can also be used for later reference by heading directly to the section of interest. Let’s Start

API Replacement Token

The given code snippets use replacement tokens, to indicate which information has to be provided by the user. The following table describes where to find the respective token.

Token Description
HOST see Bosch IoT Rollouts endpoints.
TENANT_ID see Binding Credentials1
USERNAME see Binding Credentials1
PASSWORD see Binding Credentials1
TARGET_TOKEN see security token authentication to enable the feature. A device’s security token is found in the Target Details table in the Deployment View:

Target Details

GATEWAY_TOKEN see gateway token authentication to enable the feature.

1Binding Credentials: With your subscription you have received Binding Credentials (e.g. in bosch-iot-suite.com > my account > subscriptions). This JSON style document contains your Tenant ID among others.

Device Management Federation API

The guide does not contain examples for the Device Management Federation API (DMF). Its protocol flow is described in the respective section of the API guide. Moreover, the hawkBit Device Simulator implements a DMF client, which can be used as a reference implementation.