Key Capabilities
- Bidirectional IoT message queuing with multiple QoS levels
- TLS encryption and client certificate authentication with configurable keep-alive intervals
- Topic-based filtering with wildcard support and Last Will message handling
Overview
Sending data through an MQTT connector publishes the data to the configured topic, and messages that are received on any of the topics that the connector is subscribed to are placed in the Transactions tab.Connector Configuration
This section contains all of the configurable connector properties.Settings Tab
Host Configuration
Settings related to the remote MQTT server connection.Client Authentication
Settings related to authenticating against the remote MQTT server.TLS Settings
Settings related to establishing a secure connection via TLS.Publish
Settings related to publishing MQTT messages.Subscribe
Settings related to subscribing to MQTT messages.Advanced Tab
TLS Client Authentication
Advanced Settings
Settings not included in the previous categories.Message
Logging
Miscellaneous
Automation Tab
Automation Settings
Settings related to the automatic processing of files by the connector.Performance
Alerts Tab
SLAs Tab
ログタブ
Establishing a Connection
At a minimum, set Remote Host on the Settings tab to the domain name or IP address of the MQTT server. If you are using a non-standard port, set Remote Port. If authentication is required, set Username and Password. If you require a secure connection, check Use TLS, and optionally set the TLS Server Certificate to the server’s public certificate, or choose Any Certificate to accept any certificate presented by the server. If this field is used improperly, it creates a security risk. Use extreme caution when setting this field.Publishing
To publish data, set Topic in the Publish section to the topic where the connector should publish messages. QoS values range from 0 to 2 and have the following meanings:- 0 — At most once. The published message is sent once, and if it does not arrive it is lost.
- 1 — At least once. Guarantees that the published message arrives, but there might be duplicates.
- 2 — Exactly once. Guarantees that the published message arrives and that there are no duplicates.
Subscribing
In the Subscribe section of the settings page, you can check Enable MQTT Receiver to indicate that the connector should also receive data. When checked, the connector subscribes to the topics you specify in Topic Filters, and incoming messages are automatically placed on the Transactions tab, named based on the value specified in Local File Scheme in the Advanced Settings portion of the Advanced tab. By default, the connector names files with the topic and packet Id of the message, using%topic%_%packetid%.data as the Local File Scheme value.
You can supply a comma-separated list of topic filters that the connector should subscribe to in Topic Filters. The following characters have special meanings in a topic filter:
- / — The topic level separator
- # — The multi-level wildcard (zero or more levels)
- + — The single-level wildcard (exactly one level)
- Leading $ — Denotes a “system topic”