MQTT - IBM Watson over SSL (Gen 1)
Note: The IBM Watson IoT platform is deprecated, affecting the functionality of the MQTT - IBM Watson over SSL connector.
Overview
IBM Watson MQTT SSL integration enables an Edge System to connect with IBM Watson using SSL authentication.
Supported Versions
Compatible with MQTT Protocol version 3.1.0 and MQTT Protocol version 3.1.1
Supported Communication
- Outbound (Publish data from Edge to MQTT Broker) - Yes
- Inbound (Subscribe data from MQTT Broker to Edge ) - Yes
Configurations
Variable | Detail | Required |
|---|---|---|
Name | Enter a name for the connector | Yes |
Hostname | IP Address or Server FQDN of MQTT broker (Must be reachable from the Edge system) | Yes |
Port | MQTT broker port | Yes |
CA certificate | It is a digital certificate issued by a trusted Certificate Authority and is used to authenticate the identity of servers or entities in an SSL/TLS connection. | No |
Organization id | The IBM unique six-character organization ID | Yes |
Device type | Device types are groups of devices that share common characteristics. | Yes |
Device id | A user-defined string identifier for the device. This ID must be unique within the registry. | Yes |
Token | Token that was generated when the device was registered with Watson IoT Platform | Yes |
QoS | The Quality of Service (QoS) level represents an understanding between the message sender and receiver, outlining the assurance of message delivery for a particular message. Simultaneously publishing multiple messages can enhance throughput, but opting for higher values may increase the risk of message loss, even when QoS is set to 1. Please note that the actual QoS options available may vary based on the server configuration. | Yes |
Parallel publish count | It refers to the number of messages that can be simultaneously published or sent in parallel. It is a measure of how many messages can be transmitted at the same time. As an example, in Mosquitto, you have the following settings: * max_queued_messages (default 100) * max_queued_bytes (default 0) As per the Mosquitto documentation, when this limit is reached, any additional messages are silently discarded. You have the option to either adjust the server configuration or specify this value based on the server settings. | Yes |
Integration topic | Default topic for publishing or subscribing | Yes |
LWT topic | It refers to the specific topic where the last will message will be published. | No |
LWT payload | It is the information or message that will be sent to the specified topic when the client disconnects unexpectedly or goes offline without sending a proper "goodbye" message. | No |
LWT payload type | A payload type (raw string or base64 encoded bytes) for Last Will and Testament feature of MQTT | No |
LWT QoS | A QoS value for Last Will and Testament feature of MQTT | No |
LWT retained | If enabled, the broker will store the LWT message, and any new subscribers to the LWT topic will immediately receive this retained LWT message. | No |
Throttling limit | Set a limit on the number of outbound messages per second. If sending data to a server that has restrictions on the rate of incoming messages, this ensures that no messages are lost. | No |
Persistent storage | If enabled, messages in the outbound queue are stored on disk. If there are interruptions in connection or power loss, messages will be retained and eventually sent when the connection is restored. | No |
Queue mode | Select the sequence of data transfer: FIFO or LIFO. Selecting FIFO (First In First Out) will send the earliest message first. Selecting LIFO (Last In First Out) will send the latest message first. | No |