Creates a JMS Message from the contents of a FlowFile and sends the message to a JMS Server
Tags: jms, send, put
Properties:
In the list below, the names of required properties appear in bold. Anyother properties (not in bold) are considered optional. The table also indicates any default values, whether a property supports the NiFi Expression Language (or simply EL), and whether a property is considered "sensitive", meaning that its value will be encrypted. Before entering a value in a sensitive property, ensure that the nifi.properties file has an entry for the property nifi.sensitive.props.key.
| Name | Description | Default Value | Valid Values | EL | Sensitive |
|---|---|---|---|---|---|
| JMS Provider | The Provider used for the JMS Server | ActiveMQ |
| No | No |
| URL | The URL of the JMS Server | No | No | ||
| Destination Name | The name of the JMS Topic or queue to use | No | No | ||
| Destination Type | The type of the JMS Destination to use | Queue |
| No | No |
| Communications Timeout | The amount of time to wait when attempting to receive a message before giving up and assuming failure | 30 sec | No | No | |
| Message Batch Size | The number of messages to pull/push in a single iteration of the processor | 10 | No | No | |
| Username | Username used for authentication and authorization | No | No | ||
| Password | Password used for authentication and authorization | No | Yes | ||
| Message Type | The Type of JMS Message to Construct | byte |
| No | No |
| Message Priority | The Priority of the Message | Yes | No | ||
| Reply-To Queue | The name of the queue to which a reply to should be added | Yes | No | ||
| Max Buffer Size | The maximum amount of data that can be buffered for a JMS Message. If a FlowFile's size exceeds this value, the FlowFile will be routed to failure. | 1 MB | No | No | |
| Message Time to Live | The amount of time that the message should live on the destination before being removed; if not specified, the message will never expire. | No | No | ||
| Copy Attributes to JMS Properties | Whether or not FlowFile Attributes should be translated into JMS Message Properties. If true, all attributes starting with 'jms.' will be set as Properties on the JMS Message (without the 'jms.' prefix). If an attribute exists that starts with the same value but ends in '.type', that attribute will be used to determine the JMS Message Property type. | true |
| No | No |
| Client ID Prefix | A human-readable ID that can be used to associate connections with yourself so that the maintainers of the JMS Server know who to contact if problems arise | No | No |
Relationships:
| Name | Description |
|---|---|
| failure | All FlowFiles that cannot be routed to the JMS destination are routed to this relationship |
| success | All FlowFiles that are sent to the JMS destination are routed to this relationship |