Bosch IoT Rollouts

Getting started

Welcome to Bosch IoT Rollouts.

This guide is intended to give a quick overview of the most prominent scenarios which can be fulfilled with Bosch IoT Rollouts.

This documentation is dedicated to Bosch IoT Rollouts as a standalone service.

If you are using the Bosch IoT Rollouts functionalities as part of your Bosch IoT Device Management subscription, please read the relevant documentation here.

This is important, as some functionalities and workflows may differ.

The following sections will guide you step by step:


Each scenario builds upon the previous one, so it is possible to fulfill them successively. However, you can also use them for reference later on by heading directly to the section of interest.

Let’s start with Subscribe a Bosch IoT Rollouts instance.

API Replacement Token

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

Token

Description

HOST

see Service plans and regions

TENANT_ID

see Binding Credentials - open Subscriptions > select the respective Subscription > open Binding credentials

USERNAME

see Binding Credentials, same as above

PASSWORD

see Binding Credentials, same as above

TARGET_TOKEN

see Target security token authentication to enable the feature
see Targets > Target to find a device’s security token

images/confluence/download/attachments/1680489057/roUi-getStarted-targetToken-version-1-modificationdate-1697618796000-api-v2.png

GATEWAY_TOKEN

see Gateway security token authentication to enable the feature

Device Management Federation API

The guide does not provide examples for the Device Management Federation API (DMF API). 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.