Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Table of Contents

Search

  1. Preface
  2. IDMC REST API
  3. REST API resource quick references
  4. Platform REST API version 2 resources
  5. Platform REST API version 3 resources
  6. Data Integration REST API
  7. Cloud Data Integration for PowerCenter (CDI-PC) REST API
  8. Data Ingestion and Replication REST API
  9. Customer Managed REST API
  10. RunAJob utility
  11. ParamSetCli utility
  12. REST API codes

REST API Reference

REST API Reference

MQTT sources

MQTT sources

When the source connection of the task source is MQTT, you can include the following fields and key-value pairs in the config array of the source connection:
Key
Type
Required
Description
ClientID
String
-
Unique identifier of the connection between the MQTT source and the MQTT broker. The client ID is the file-based persistence store that the MQTT source uses to store messages while they are processed.
You can enter a string of up to 255 characters.
MaxQueueSize
Integer
-
The maximum number of messages that the processor can store in memory.
You can enter a value between 1 and 2147483647.
Topic
String
Yes
Name of the MQTT topic.

POST request example

To update a
streaming ingestion and replication
task with an MQTT source and a flat file target, you might send a request similar to the following example:
POST <serverUrl>/sisvc/restapi/v1/UpdateEntity/Documents('<document ID>') Content-Type: application/json Accept: application/json IDS-SESSION-ID: <SessionId> { "name": "mqtt to flatfile", "description": "mqtt to flatfile", "runtimeId": "01000025000000000003", "locationId": "5sJ0JDyJyWLlrosS5qJjsQ", "currentVersion": "2", "messageFormat": "binary", "nodes": [ { "name": "mqtt to flatfile_source", "type": "source", "connectionId": "012MGS0B00000000001O", "transformationType": "", "config": [ { "key": "ClientID", "value": "test" }, { "key": "MaxQueueSize", "value": 1024 }, { "key": "Topic", "value": "test" } ] }, { "name": "mqtt to flatfile_target", "type": "target", "connectionId": "012MGS0B00000000002N", "transformationType": "", "config": [ { "key": "interimDirectory", "value": "/home/agent/test" }, { "key": "rolloverSize", "value": 1024 }, { "key": "rolloverEvents", "value": 100 }, { "key": "rolloverTime", "value": 300000 }, { "key": "File Name", "value": "test" } ] } ], "edges": [ { "from": "mqtt to flatfile_source", "to": "mqtt to flatfile_target" } ] }
The response returns only the fields that you entered in the request. If the request is unsuccessful, the response includes a reason for the failure.

POST response example

If the request is successful, you might receive a response similar to the following example in a
Success
node:
{ "Success": { "name": "mqtt to flatfile", "description": "mqtt to flatfile", "runtimeId": "01000025000000000003", "locationId": "5sJ0JDyJyWLlrosS5qJjsQ", "currentVersion": "2", "messageFormat": "binary", "nodes": [ { "name": "mqtt to flatfile_source", "type": "source", "connectionId": "012MGS0B00000000001O", "transformationType": "", "config": [ { "key": "ClientID", "value": "test" }, { "key": "MaxQueueSize", "value": 1024 }, { "key": "Topic", "value": "test" } ] }, { "name": "mqtt to flatfile_target", "type": "target", "connectionId": "012MGS0B00000000002N", "transformationType": "", "config": [ { "key": "interimDirectory", "value": "/home/agent/test" }, { "key": "rolloverSize", "value": 1024 }, { "key": "rolloverEvents", "value": 100 }, { "key": "rolloverTime", "value": 300000 }, { "key": "File Name", "value": "test" } ] } ], "edges": [ { "from": "mqtt to flatfile_source", "to": "mqtt to flatfile_target" } ] } }

0 COMMENTS

We’d like to hear from you!