Table of Contents

Search

  1. Preface
  2. Informatica Intelligent Cloud Services REST API
  3. Platform REST API version 2 resources
  4. Platform REST API version 3 resources
  5. Data Integration REST API
  6. File Ingestion and Replication REST API
  7. Streaming Ingestion and Replication REST API
  8. Model Serve REST API
  9. RunAJob utility
  10. ParamSetCli utility
  11. REST API codes
  12. REST API resource quick references

REST API Reference

REST API Reference

Connection configuration for tasks with JMS as a source

Connection configuration for tasks with JMS as a source

When the source connection of the task source is JMS, you can include the following fields and key-value pairs in the config array of the source connection:
Key
Type
Required
Description
destinationType
String
Yes
Type of destination that the source service sends JMS messages to. Enter one of the following values:
  • QUEUE
    . The JMS provider delivers messages to a single consumer who is registered for the queue.
  • TOPIC
    . The JMS provider delivers messages to all active consumers that subscribe to the topic.
clientId
String
Yes
Unique ID of the JMS connection. You can enter a string of up to 255 characters.
sharedSubscription
String
Yes
Enables multiple consumers to access a single subscription. Applies to the TOPIC destination type. Enter one of the following values:
  • True
  • False
durableSubscription
String
Yes
When set to True, the JMS source service enables inactive subscribers to retain messages and then deliver them when the subscriber reconnects. Applies to the TOPIC destination type. Enter one of the following values:
  • True
  • False
subscriptionName
String
Yes
Name of the subscription. Applies to the TOPIC destination type, when the topic subscription type is shared, durable, or both.
JMS Destination
String
Yes
Name of the queue or topic that the JMS provider delivers messages to.

POST request example

To update a
streaming ingestion and replication
task with an JMS source and a flat file target, you might send a request similar to the following example:
{ "name": "crud", "description": "JMS to FileToFile", "runtimeId": "01000025000000000003", "locationId": "5sJ0JDyJyWLlrosS5qJjsQ", "currentVersion": "2", "messageFormat": "binary", "nodes": [ { "name": "crud_source", "type": "source", "connectionId": "012MGS0B000000000003", "transformationType": "", "config": [ { "key": "destinationType", "value": "QUEUE" }, { "key": "clientId", "value": "" }, { "key": "JMS Destination", "value": "test" } ] }, { "name": "crud_target", "type": "target", "connectionId": "012MGS0B00000000000H", "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": "crud_source", "to": "crud_target" } ] }

0 COMMENTS

We’d like to hear from you!