Use a JMS source to read data from a JMS provider. To create a JMS source connection, use the JMS connection type.
JMS providers are message-oriented middleware systems that send JMS messages. The JMS source reads JMS messages either from a JMS provider message queue or from a JMS provider based on the message topic.
The JMS source can read the following JMS message types:
Message. Contains only header and properties fields
TextMessage. Contains a string object. TextMessages can contain XML or JSON message data.
BytesMessage. A stream of uninterpreted bytes. Use a BytesMessage for encoding a message body to match an existing message format. BytesMessages generally do not include property fields.
MapMessage. Contains a set of name or value pairs. The names are in string format. The values are of Java primitive datatypes.
JMS message delivery destination types
You can choose one of the following JMS message delivery destination types:
Queue
. The JMS message producer delivers messages to a single consumer. The consumer must be registered to consume messages from the queue. If no consumers are registered to the queue, the queue retains the messages until a consumer registers to it.
Topic
. The JMS message producer delivers messages to all active consumers who subscribe to the topic. Several producers can send messages to the topic destination, and each message can be delivered to several subscribers. If no consumers are registered to the topic, the topic doesn't retain the message. You can make the subscription sharable, durable or both. A sharable subscription enables one or more consumers to access a single subscription. A durable subscription retains the message for inactive subscribers until subscribers consume the message or until the message expires.
ASK INFAPreview
