Bosch IoT Device Management - will be discontinued by mid 2024

General fields for a connection

This section holds general parameters to manage your connection.

  • Connection ID: Each connection is stored with a technical unique identifier.
    You can use it for API level access on the connection configuration (see HTTP API description).

  • Connection name: This is the name which will be displayed at the left side in the list of connections.
    The list orders the connections alphabetically.

  • Connection type: The type defines which underlying transport protocol is used.
    At the time we support:

    • Bosch IoT Hub - the device connectivity layer uses Apache Kafka, this connection is created automatically with your subscription.

    • AMQP 0.9.1 - if you use a AMQP 0.91 message broker, e.g. RabbitMQ.

    • AMQP 1.0 - if you use generic AMQP 1.0 message broker like Apache ActiveMQ Artemis.

    • HTTP 1.1 - to publish messages to an existing HTTP server/endpoint via POST, PUT or PATCH verbs.
      Please note, that we support HTTP topics only one-way as targets, i.e. you will not be able to configure a HTTP connection as a source.

    • Kafka 2.x - to publish messages to and from an Apache Kafka cluster infrastructure.

    • MQTT 3.1.1 - if you use an MQTT 3 server or service.

    • MQTT 5 - if you use an MQTT 5 server or service.

    • AWS IoT - if you use an MQTT endpoint Amazon’s web services.

      WebSocket connections are not displayed here because such connections are opened and closed ad hoc, and do not need explicit configuration.

  • Enable debug mode for target-issued acknowledgements

    • Disabled by default. You can enable it e.g. for debugging.

  • Reflect device connectivity status in thing

  • Edge or virtual device via gateway

  • Gateway or stand-alone device

  • Enable automatic re-connect (always enabled for Kafka):

    • Enabled by default.

    • Via this parameter, you can enable or disable the failover behavior.
      By enabling, the automatic re-connect, in case a connection closes unexpectedly or fails to establish, the digital twin layer will automatically try to re-connect.

  • Validate certificates (always enabled for Kafka)

    • Enabled by default.

    • Via this parameter, you can enable or disable the SSL certificate validation.

  • Enable SSH tunnel

    • Disabled by default. You can enable it if you need to establish an SSH tunnel.

  • Client count: Number of clients to be instantiated for this connection

    • Free plan subscribers can use 1 client

    • Starter and Standard plan subscribers are allowed to increase to max. 2 clients.
      When you configure more than one client, a load balancing for you connection will be used.