MQTT Consumer
Snap type: | Read | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Description: | This Snap is used for subscribing to one or more MQTT message brokers and subscribing to and consuming messages from one or more topics. | |||||||||||||||||
Prerequisites: | [None] | |||||||||||||||||
Support and limitations: | Works in Ultra Task Pipelines. | |||||||||||||||||
Account: | This Snap uses account references created on the Accounts page of SnapLogic Manager to handle access to this endpoint. See MQTT Account for information on setting up this type of account. | |||||||||||||||||
Views: |
| |||||||||||||||||
Settings | ||||||||||||||||||
Label | Required. The name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your pipeline. | |||||||||||||||||
Topic Filter | Required. One or more topic filters. The "topic filter" string used when subscribing may contain special characters, which allow you to subscribe to multiple topics at once. The topic level separator is used to introduce structure into the topic, and can therefore be specified within the topic for that purpose. The multi-level wildcard and single-level wildcard can be used for subscriptions, but they cannot be used within a topic by the publisher of a message. Topic level separator Multi-level wildcard  finance/stock/ibm The multi-level wildcard can represent zero or more levels. Therefore, finance/# can also match the singular finance, where # represents zero levels. The topic level separator is meaningless in this context, because there are no levels to separate. The multi-level wildcard can be specified only on its own or next to the topic level separator character. Therefore, # and finance/# are both valid, but finance# is not valid. The multi-level wildcard must be the last character used within the topic tree. For example, finance/# is valid but finance/#/closingprice is not valid. Single-level wildcard Default value: [None] | |||||||||||||||||
Max QoS | Required. The maximum quality of service to subscribe each topic at. Messages published at a lower quality of service will be received at the published QoS. Messages published at a higher quality of service will be received using the QoS specified on the subscribe. | |||||||||||||||||
Suggest seconds | Required. Number of seconds to listen for messages during preview mode at design time. Please note that the platform imposes a time limit of 180? seconds during pipeline validation which will take precedence if you enter a number of seconds greater than that limit. | |||||||||||||||||
Execute seconds | Required. Number of seconds to listen for messages when your pipeline is executed. Enter 0 to listen until the pipeline is stopped. | |||||||||||||||||
Page lookup error: page "Anaplan Read" not found. If you're experiencing issues please see our Troubleshooting Guide. | Page lookup error: page "Anaplan Read" not found. If you're experiencing issues please see our Troubleshooting Guide. |
 Snap Pack History
Have feedback? Email documentation@snaplogic.com | Ask a question in the SnapLogic Community
© 2017-2024 SnapLogic, Inc.