OAuth2 client | An OAuth2 client is created and managed in Rollouts Management UI. It grants access to resources within the tenant's scope. The client consists of a client ID, a secret, and a scope. This information is provided as configured into a client application. The client application uses the client to get a token from the Rollouts IdP authorization token endpoint. |
Authorization token endpoint | The endpoint (URL) to request authorization tokens. The tokens can be requested according to the OAuth 2 spec RFC 6749. See https://oauth.net/2/. |
Authorization token | The Bearer token is issued by the Rollouts IdP - authorization token endpoint. The token authorizes access to service APIs. |
Action | Requested operations for the targets. Usually, a software update. Other supported actions include canceling a running update action or refreshing target attributes. |
Action Status | Status information of an action that can be provided by the target. This can be the start of the action lifecycle, the end, or update notifications in between. |
Artifact | An Artifact is a file of any type that has been uploaded to Rollouts. It may contain firmware, an application, or a link to external artifact references. |
Auto Assignment | Targets that match a Target Filter get a Distribution Set automatically assigned. |
Controller | Term used in DDI API for a Target. |
Device Management Federation API (DMF API) | AMQP-based API for indirect device integration via an external device management |
Direct Device Integration API (DDI API) | Polling-based HTTP API for integrating devices |
Distribution Set (DS) | A Distribution Set defines a meta package that combines a set of software modules that must be provisioned in their entirety (e.g., OS X Ver X, JVM Y ver. Y, AH Z ver. Z). |
Distribution Set Type | A Distribution Set Type is an abstract definition for DS that defines which types of Software Modules can be added (optionally or mandatorily). A DS is considered complete if all mandatory Software Modules are present. Only a complete DS can be assigned to a Target. |
Gateway | A device that indirectly connects other devices with Rollouts. |
Gateway Security Token | Security Token of a Gateway to authenticate multiple targets (which are behind that Gateway) with Rollouts. |
Management UI | The management UI of Bosch IoT Rollouts includes the following UI features: Actions, Targets, Rollouts, Software modules, and Distribution sets. |
Metadata | Metadata is key-value pairs that can be freely modified to describe and identify DSs and SMs. |
Rollout | Software update on (a large set of) devices in a managed and defined way. |
Security Token | A 32-character alphanumeric security token. Can either be a Gateway Security Token or a Target Token. |
Software Module (SM) | A Software Module is a logical grouping of Artifacts based on a defined Software Module Type. |
Software Module Type | A Software Module Type is an abstract definition for an SM that defines whether it is Firmware or Software. A DS can only be assigned to one SM of type Firmware, but multiple of type Software. |
Tag | Tags are strings used to describe and identify Targets and DSs. |
Target | A target is a device to which software can be assigned. (a.k.a. Controller) |
Target Attributes | Attributes are key-value metadata sent by a target and stored on the Rollouts server. On the server side, they can be used to identify and classify targets based on their properties, e.g., hardware revision and serial number. |
Target Filter | Filter targets by a defined query. Target Filters are used for Auto Assignments or to select targets for a Rollout. |
Target Token | Security Token of a Target to authenticate with Rollouts. |
Target Type | A Target Type is an abstract definition for Targets. It contains a list of Distribution Set Types that define if a Distribution Set is compatible with a Target. |