PublishJMS 2.0.0

Bundle
org.apache.nifi | nifi-jms-processors-nar
Description
Creates a JMS Message from the contents of a FlowFile and sends it to a JMS Destination (queue or topic) as JMS BytesMessage or TextMessage. FlowFile attributes will be added as JMS headers and/or properties to the outgoing JMS message.
Tags
jms, message, publish, put, send
Input Requirement
REQUIRED
Supports Sensitive Dynamic Properties
false
Properties
Dynamic Properties
System Resource Considerations
Resource Description
MEMORY An instance of this component can cause high usage of this system resource. Multiple instances or high concurrency settings may result a degradation of performance.
Restrictions
Required Permission Explanation
reference remote resources Client Library Location can reference resources over HTTP
Relationships
Name Description
success All FlowFiles that are sent to the JMS destination are routed to this relationship
failure All FlowFiles that cannot be sent to JMS destination are routed to this relationship
Reads Attributes
Name Description
jms_deliveryMode This attribute becomes the JMSDeliveryMode message header. Must be an integer.
jms_expiration This attribute becomes the JMSExpiration message header. Must be a long.
jms_priority This attribute becomes the JMSPriority message header. Must be an integer.
jms_redelivered This attribute becomes the JMSRedelivered message header.
jms_timestamp This attribute becomes the JMSTimestamp message header. Must be a long.
jms_correlationId This attribute becomes the JMSCorrelationID message header.
jms_type This attribute becomes the JMSType message header. Must be an integer.
jms_replyTo This attribute becomes the JMSReplyTo message header. Must be an integer.
jms_destination This attribute becomes the JMSDestination message header. Must be an integer.
other attributes All other attributes that do not start with jms_ are added as message properties.
other attributes .type When an attribute will be added as a message property, a second attribute of the same name but with an extra `.type` at the end will cause the message property to be sent using that strong type. For example, attribute `delay` with value `12000` and another attribute `delay.type` with value `integer` will cause a JMS message property `delay` to be sent as an Integer rather than a String. Supported types are boolean, byte, short, integer, long, float, double, and string (which is the default).
See Also