Summary
This processor publishes the contents of the incoming FlowFile to a JMS compliant messaging system.
This processor does two things. It constructs JMS Message by extracting FlowFile contents (both body and attributes).
Once message is constructed it is sent to a pre-configured JMS Destination.
Standard JMS Headers
will be extracted from the FlowFile and set on javax.jms.Message as JMS headers while other
FlowFile attributes will be set as properties of javax.jms.Message. Upon success the incoming FlowFile is transfered
to the success Relationship and upon failure FlowFile is
penalized and transfered to the failure Relationship.
Configuration Details
At the time of writing this document it only defines the essential configuration properties which are suitable for most cases.
Other properties will be defined later as this component progresses.
Configuring PublishJMS:
- User Name - [OPTIONAL] User Name used for authentication and authorization when this processor obtains javax.jms.Connection
from the pre-configured javax.jms.ConnectionFactory (see below).
- Password - [OPTIONAL] Password used in conjunction with User Name.
- Destination Name - [REQUIRED] the name of the javax.jms.Destination.
Usually provided by administrator (e.g., 'topic://myTopic').
- Destination Type - [OPTIONAL] the type of the javax.jms.Destination. Could be one of 'QUEUE' or 'TOPIC'
Usually provided by the administrator. Defaults to 'TOPIC'.
- Session Cache size - [OPTIONAL] Specify the desired size for the JMS Session cache (per JMS Session type). This cache
size is the maximum limit for the number of cached Sessions.
Usually provided by the administrator (e.g., '2453'). Defaults to '1'.
- Connection Factory Service - [REQUIRED] link to a pre-configured instance of org.apache.nifi.jms.cf.JMSConnectionFactoryProvider.