MQTT - IBM Watson over SSL

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