<extensionManifest><groupId>org.apache.nifi</groupId><artifactId>nifi-jms-processors-nar</artifactId><version>1.28.0.101-eep-941</version><parentNar><groupId>org.apache.nifi</groupId><artifactId>nifi-jms-cf-service-nar</artifactId><version>1.28.0.101-eep-941</version></parentNar><systemApiVersion>1.28.0.101-eep-941</systemApiVersion><buildInfo><tag>nifi-1.28.0-RC1</tag><branch>UNKNOWN</branch><revision>ce631aa</revision></buildInfo><extensions><extension><name>org.apache.nifi.jms.processors.ConsumeJMS</name><type>PROCESSOR</type><description>Consumes JMS Message of type BytesMessage, TextMessage, ObjectMessage, MapMessage or StreamMessage transforming its content to a FlowFile and transitioning it to 'success' relationship. JMS attributes such as headers and properties will be copied as FlowFile attributes. MapMessages will be transformed into JSONs and then into byte arrays. The other types will have their raw contents as byte array transferred into the flowfile.</description><tags><tag>jms</tag><tag>get</tag><tag>message</tag><tag>receive</tag><tag>consume</tag></tags><properties><property><name>Connection Factory Service</name><displayName>Connection Factory Service</displayName><description>The Controller Service that is used to obtain Connection Factory. Alternatively, the 'JNDI *' or the 'JMS *' properties can also be be used to configure the Connection Factory.</description><controllerServiceDefinition><className>org.apache.nifi.jms.cf.JMSConnectionFactoryProviderDefinition</className><groupId>org.apache.nifi</groupId><artifactId>nifi-jms-cf-service-nar</artifactId><version>1.28.0.101-eep-941</version></controllerServiceDefinition><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>NONE</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>Destination Name</name><displayName>Destination Name</displayName><description>The name of the JMS Destination. Usually provided by the administrator (e.g., 'topic://myTopic' or 'myTopic').</description><required>true</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>FLOWFILE_ATTRIBUTES</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>Destination Type</name><displayName>Destination Type</displayName><description>The type of the JMS Destination. Could be one of 'QUEUE' or 'TOPIC'. Usually provided by the administrator. Defaults to 'QUEUE'</description><defaultValue>QUEUE</defaultValue><allowableValues><allowableValue><displayName>QUEUE</displayName><value>QUEUE</value><description></description></allowableValue><allowableValue><displayName>TOPIC</displayName><value>TOPIC</value><description></description></allowableValue></allowableValues><required>true</required><sensitive>false</sensitive><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>NONE</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>Message Selector</name><displayName>Message Selector</displayName><description>The JMS Message Selector to filter the messages that the processor will receive</description><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>User Name</name><displayName>User Name</displayName><description>User Name used for authentication and authorization.</description><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>Password</name><displayName>Password</displayName><description>Password used for authentication and authorization.</description><required>false</required><sensitive>true</sensitive><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>NONE</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>Connection Client ID</name><displayName>Connection Client ID</displayName><description>The client id to be set on the connection, if set. For durable non shared consumer this is mandatory, for all others it is optional, typically with shared consumers it is undesirable to be set. Please see JMS spec for further details</description><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>Session Cache size</name><displayName>Session Cache Size</displayName><description>This property is deprecated and no longer has any effect on the Processor. It will be removed in a later version.</description><defaultValue>1</defaultValue><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>NONE</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>character-set</name><displayName>Character Set</displayName><description>The name of the character set to use to construct or interpret TextMessages</description><defaultValue>US-ASCII</defaultValue><required>true</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>FLOWFILE_ATTRIBUTES</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>Acknowledgement Mode</name><displayName>Acknowledgement Mode</displayName><description>The JMS Acknowledgement Mode. Using Auto Acknowledge can cause messages to be lost on restart of NiFi but may provide better performance than Client Acknowledge.</description><defaultValue>2</defaultValue><allowableValues><allowableValue><displayName>AUTO_ACKNOWLEDGE (1)</displayName><value>1</value><description>Automatically acknowledges a client's receipt of a message, regardless if NiFi session has been commited. Can result in data loss in the event where NiFi abruptly stopped before session was commited.</description></allowableValue><allowableValue><displayName>CLIENT_ACKNOWLEDGE (2)</displayName><value>2</value><description>(DEFAULT) Manually acknowledges a client's receipt of a message after NiFi Session was commited, thus ensuring no data loss</description></allowableValue><allowableValue><displayName>DUPS_OK_ACKNOWLEDGE (3)</displayName><value>3</value><description>This acknowledgment mode instructs the session to lazily acknowledge the delivery of messages. May result in both data duplication and data loss while achieving the best throughput.</description></allowableValue></allowableValues><required>true</required><sensitive>false</sensitive><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>NONE</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>Durable subscription</name><displayName>Durable Subscription</displayName><description>If destination is Topic if present then make it the consumer durable. @see https://docs.oracle.com/javaee/7/api/javax/jms/Session.html#createDurableConsumer-javax.jms.Topic-java.lang.String-</description><defaultValue>false</defaultValue><allowableValues><allowableValue><displayName>true</displayName><value>true</value><description></description></allowableValue><allowableValue><displayName>false</displayName><value>false</value><description></description></allowableValue></allowableValues><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>Shared subscription</name><displayName>Shared Subscription</displayName><description>If destination is Topic if present then make it the consumer shared. @see https://docs.oracle.com/javaee/7/api/javax/jms/Session.html#createSharedConsumer-javax.jms.Topic-java.lang.String-</description><defaultValue>false</defaultValue><allowableValues><allowableValue><displayName>true</displayName><value>true</value><description></description></allowableValue><allowableValue><displayName>false</displayName><value>false</value><description></description></allowableValue></allowableValues><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>Subscription Name</name><displayName>Subscription Name</displayName><description>The name of the subscription to use if destination is Topic and is shared or durable.</description><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>Timeout</name><displayName>Timeout</displayName><description>How long to wait to consume a message from the remote broker before giving up.</description><defaultValue>1 sec</defaultValue><required>true</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>Error Queue Name</name><displayName>Error Queue Name</displayName><description>The name of a JMS Queue where - if set - unprocessed messages will be routed. Usually provided by the administrator (e.g., 'queue://myErrorQueue' or 'myErrorQueue').Only applicable if 'Destination Type' is set to 'QUEUE'</description><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>FLOWFILE_ATTRIBUTES</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>record-reader</name><displayName>Record Reader</displayName><description>The Record Reader to use for parsing received JMS Messages into Records.</description><controllerServiceDefinition><className>org.apache.nifi.serialization.RecordReaderFactory</className><groupId>org.apache.nifi</groupId><artifactId>nifi-standard-services-api-nar</artifactId><version>1.28.0.101-eep-941</version></controllerServiceDefinition><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>NONE</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>record-writer</name><displayName>Record Writer</displayName><description>The Record Writer to use for serializing Records before writing them to a FlowFile.</description><controllerServiceDefinition><className>org.apache.nifi.serialization.RecordSetWriterFactory</className><groupId>org.apache.nifi</groupId><artifactId>nifi-standard-services-api-nar</artifactId><version>1.28.0.101-eep-941</version></controllerServiceDefinition><required>true</required><sensitive>false</sensitive><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>NONE</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic><dependencies><dependency><propertyName>record-reader</propertyName><propertyDisplayName>Record Reader</propertyDisplayName></dependency></dependencies></property><property><name>output-strategy</name><displayName>Output Strategy</displayName><description>The format used to output the JMS message into a FlowFile record.</description><defaultValue>USE_VALUE</defaultValue><allowableValues><allowableValue><displayName>Use Content as Value</displayName><value>USE_VALUE</value><description>Write only the message to the FlowFile record.</description></allowableValue><allowableValue><displayName>Use Wrapper</displayName><value>USE_WRAPPER</value><description>Write the additional attributes into the FlowFile record on a separate leaf. (See processor usage for more information.)</description></allowableValue><allowableValue><displayName>Use Appender</displayName><value>USE_APPENDER</value><description>Write the additional attributes into the FlowFile record prefixed with "_". (See processor usage for more information.)</description></allowableValue></allowableValues><required>true</required><sensitive>false</sensitive><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>NONE</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic><dependencies><dependency><propertyName>record-reader</propertyName><propertyDisplayName>Record Reader</propertyDisplayName></dependency></dependencies></property><property><name>java.naming.factory.initial</name><displayName>JNDI Initial Context Factory Class</displayName><description>The fully qualified class name of the JNDI Initial Context Factory Class (java.naming.factory.initial).</description><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>java.naming.provider.url</name><displayName>JNDI Provider URL</displayName><description>The URL of the JNDI Provider to use as the value for java.naming.provider.url. See additional details documentation for allowed URL schemes.</description><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>connection.factory.name</name><displayName>JNDI Name of the Connection Factory</displayName><description>The name of the JNDI Object to lookup for the Connection Factory.</description><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>naming.factory.libraries</name><displayName>JNDI / JMS Client Libraries</displayName><description>Specifies jar files and/or directories to add to the ClassPath in order to load the JNDI / JMS client libraries. This should be a comma-separated list of files, directories, and/or URLs. If a directory is given, any files in that directory will be included, but subdirectories will not be included (i.e., it is not recursive).</description><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>true</dynamicallyModifiesClasspath><dynamic>false</dynamic><resourceDefinition><cardinality>MULTIPLE</cardinality><resourceTypes><resourceType>FILE</resourceType><resourceType>URL</resourceType><resourceType>DIRECTORY</resourceType></resourceTypes></resourceDefinition></property><property><name>java.naming.security.principal</name><displayName>JNDI Principal</displayName><description>The Principal to use when authenticating with JNDI (java.naming.security.principal).</description><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>java.naming.security.credentials</name><displayName>JNDI Credentials</displayName><description>The Credentials to use when authenticating with JNDI (java.naming.security.credentials).</description><required>false</required><sensitive>true</sensitive><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>NONE</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>cf</name><displayName>JMS Connection Factory Implementation Class</displayName><description>The fully qualified name of the JMS ConnectionFactory implementation class (eg. org.apache.activemq.ActiveMQConnectionFactory).</description><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>cflib</name><displayName>JMS Client Libraries</displayName><description>Path to the directory with additional resources (eg. JARs, configuration files etc.) to be added to the classpath (defined as a comma separated list of values). Such resources typically represent target JMS client libraries for the ConnectionFactory implementation.</description><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>true</dynamicallyModifiesClasspath><dynamic>false</dynamic><resourceDefinition><cardinality>MULTIPLE</cardinality><resourceTypes><resourceType>FILE</resourceType><resourceType>URL</resourceType><resourceType>DIRECTORY</resourceType></resourceTypes></resourceDefinition></property><property><name>broker</name><displayName>JMS Broker URI</displayName><description>URI pointing to the network location of the JMS Message broker. Example for ActiveMQ: 'tcp://myhost:61616'. Examples for IBM MQ: 'myhost(1414)' and 'myhost01(1414),myhost02(1414)'.</description><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>SSL Context Service</name><displayName>JMS SSL Context Service</displayName><description>The SSL Context Service used to provide client certificate information for TLS/SSL connections.</description><controllerServiceDefinition><className>org.apache.nifi.ssl.SSLContextService</className><groupId>org.apache.nifi</groupId><artifactId>nifi-standard-services-api-nar</artifactId><version>1.28.0.101-eep-941</version></controllerServiceDefinition><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>NONE</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property></properties><dynamicProperties><dynamicProperty><name>The name of a Connection Factory configuration property.</name><value>The value of a given Connection Factory configuration property.</value><description>Additional configuration property for the Connection Factory. It can be used when the Connection Factory is being configured via the 'JNDI *' or the 'JMS *'properties of the processor. For more information, see the Additional Details page.</description><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope></dynamicProperty></dynamicProperties><relationships><relationship><name>success</name><description>All FlowFiles that are received from the JMS Destination are routed to this relationship</description><autoTerminated>false</autoTerminated></relationship><relationship><name>parse.failure</name><description>If a message cannot be parsed using the configured Record Reader, the contents of the message will be routed to this Relationship as its own individual FlowFile.</description><autoTerminated>true</autoTerminated></relationship></relationships><writesAttributes><writesAttribute><name>jms_deliveryMode</name><description>The JMSDeliveryMode from the message header.</description></writesAttribute><writesAttribute><name>jms_expiration</name><description>The JMSExpiration from the message header.</description></writesAttribute><writesAttribute><name>jms_priority</name><description>The JMSPriority from the message header.</description></writesAttribute><writesAttribute><name>jms_redelivered</name><description>The JMSRedelivered from the message header.</description></writesAttribute><writesAttribute><name>jms_timestamp</name><description>The JMSTimestamp from the message header.</description></writesAttribute><writesAttribute><name>jms_correlationId</name><description>The JMSCorrelationID from the message header.</description></writesAttribute><writesAttribute><name>jms_messageId</name><description>The JMSMessageID from the message header.</description></writesAttribute><writesAttribute><name>jms_type</name><description>The JMSType from the message header.</description></writesAttribute><writesAttribute><name>jms_replyTo</name><description>The JMSReplyTo from the message header.</description></writesAttribute><writesAttribute><name>jms_destination</name><description>The JMSDestination from the message header.</description></writesAttribute><writesAttribute><name>jms.messagetype</name><description>The JMS message type, can be TextMessage, BytesMessage, ObjectMessage, MapMessage or StreamMessage).</description></writesAttribute><writesAttribute><name>other attributes</name><description>Each message property is written to an attribute.</description></writesAttribute></writesAttributes><restricted><restrictions><restriction><requiredPermission>reference remote resources</requiredPermission><explanation>Client Library Location can reference resources over HTTP</explanation></restriction></restrictions></restricted><inputRequirement>INPUT_FORBIDDEN</inputRequirement><seeAlso><see>org.apache.nifi.jms.processors.PublishJMS</see><see>org.apache.nifi.jms.cf.JMSConnectionFactoryProvider</see></seeAlso></extension><extension><name>org.apache.nifi.jms.processors.PublishJMS</name><type>PROCESSOR</type><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.</description><tags><tag>jms</tag><tag>put</tag><tag>message</tag><tag>send</tag><tag>publish</tag></tags><properties><property><name>Connection Factory Service</name><displayName>Connection Factory Service</displayName><description>The Controller Service that is used to obtain Connection Factory. Alternatively, the 'JNDI *' or the 'JMS *' properties can also be be used to configure the Connection Factory.</description><controllerServiceDefinition><className>org.apache.nifi.jms.cf.JMSConnectionFactoryProviderDefinition</className><groupId>org.apache.nifi</groupId><artifactId>nifi-jms-cf-service-nar</artifactId><version>1.28.0.101-eep-941</version></controllerServiceDefinition><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>NONE</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>Destination Name</name><displayName>Destination Name</displayName><description>The name of the JMS Destination. Usually provided by the administrator (e.g., 'topic://myTopic' or 'myTopic').</description><required>true</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>FLOWFILE_ATTRIBUTES</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>Destination Type</name><displayName>Destination Type</displayName><description>The type of the JMS Destination. Could be one of 'QUEUE' or 'TOPIC'. Usually provided by the administrator. Defaults to 'QUEUE'</description><defaultValue>QUEUE</defaultValue><allowableValues><allowableValue><displayName>QUEUE</displayName><value>QUEUE</value><description></description></allowableValue><allowableValue><displayName>TOPIC</displayName><value>TOPIC</value><description></description></allowableValue></allowableValues><required>true</required><sensitive>false</sensitive><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>NONE</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>User Name</name><displayName>User Name</displayName><description>User Name used for authentication and authorization.</description><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>Password</name><displayName>Password</displayName><description>Password used for authentication and authorization.</description><required>false</required><sensitive>true</sensitive><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>NONE</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>Connection Client ID</name><displayName>Connection Client ID</displayName><description>The client id to be set on the connection, if set. For durable non shared consumer this is mandatory, for all others it is optional, typically with shared consumers it is undesirable to be set. Please see JMS spec for further details</description><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>Session Cache size</name><displayName>Session Cache Size</displayName><description>This property is deprecated and no longer has any effect on the Processor. It will be removed in a later version.</description><defaultValue>1</defaultValue><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>NONE</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>message-body-type</name><displayName>Message Body Type</displayName><description>The type of JMS message body to construct.</description><defaultValue>bytes</defaultValue><allowableValues><allowableValue><displayName>bytes</displayName><value>bytes</value><description></description></allowableValue><allowableValue><displayName>text</displayName><value>text</value><description></description></allowableValue></allowableValues><required>true</required><sensitive>false</sensitive><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>NONE</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>character-set</name><displayName>Character Set</displayName><description>The name of the character set to use to construct or interpret TextMessages</description><defaultValue>US-ASCII</defaultValue><required>true</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>FLOWFILE_ATTRIBUTES</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>allow-illegal-chars-in-jms-header-names</name><displayName>Allow Illegal Characters in Header Names</displayName><description>Specifies whether illegal characters in header names should be sent to the JMS broker. Usually hyphens and full-stops.</description><defaultValue>false</defaultValue><allowableValues><allowableValue><displayName>true</displayName><value>true</value><description></description></allowableValue><allowableValue><displayName>false</displayName><value>false</value><description></description></allowableValue></allowableValues><required>true</required><sensitive>false</sensitive><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>NONE</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>attributes-to-send-as-jms-headers-regex</name><displayName>Attributes to Send as JMS Headers (Regex)</displayName><description>Specifies the Regular Expression that determines the names of FlowFile attributes that should be sent as JMS Headers</description><defaultValue>.*</defaultValue><required>true</required><sensitive>false</sensitive><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>NONE</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>record-reader</name><displayName>Record Reader</displayName><description>The Record Reader to use for parsing the incoming FlowFile into Records.</description><controllerServiceDefinition><className>org.apache.nifi.serialization.RecordReaderFactory</className><groupId>org.apache.nifi</groupId><artifactId>nifi-standard-services-api-nar</artifactId><version>1.28.0.101-eep-941</version></controllerServiceDefinition><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>NONE</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>record-writer</name><displayName>Record Writer</displayName><description>The Record Writer to use for serializing Records before publishing them as an JMS Message.</description><controllerServiceDefinition><className>org.apache.nifi.serialization.RecordSetWriterFactory</className><groupId>org.apache.nifi</groupId><artifactId>nifi-standard-services-api-nar</artifactId><version>1.28.0.101-eep-941</version></controllerServiceDefinition><required>true</required><sensitive>false</sensitive><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>NONE</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic><dependencies><dependency><propertyName>record-reader</propertyName><propertyDisplayName>Record Reader</propertyDisplayName></dependency></dependencies></property><property><name>java.naming.factory.initial</name><displayName>JNDI Initial Context Factory Class</displayName><description>The fully qualified class name of the JNDI Initial Context Factory Class (java.naming.factory.initial).</description><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>java.naming.provider.url</name><displayName>JNDI Provider URL</displayName><description>The URL of the JNDI Provider to use as the value for java.naming.provider.url. See additional details documentation for allowed URL schemes.</description><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>connection.factory.name</name><displayName>JNDI Name of the Connection Factory</displayName><description>The name of the JNDI Object to lookup for the Connection Factory.</description><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>naming.factory.libraries</name><displayName>JNDI / JMS Client Libraries</displayName><description>Specifies jar files and/or directories to add to the ClassPath in order to load the JNDI / JMS client libraries. This should be a comma-separated list of files, directories, and/or URLs. If a directory is given, any files in that directory will be included, but subdirectories will not be included (i.e., it is not recursive).</description><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>true</dynamicallyModifiesClasspath><dynamic>false</dynamic><resourceDefinition><cardinality>MULTIPLE</cardinality><resourceTypes><resourceType>FILE</resourceType><resourceType>URL</resourceType><resourceType>DIRECTORY</resourceType></resourceTypes></resourceDefinition></property><property><name>java.naming.security.principal</name><displayName>JNDI Principal</displayName><description>The Principal to use when authenticating with JNDI (java.naming.security.principal).</description><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>java.naming.security.credentials</name><displayName>JNDI Credentials</displayName><description>The Credentials to use when authenticating with JNDI (java.naming.security.credentials).</description><required>false</required><sensitive>true</sensitive><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>NONE</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>cf</name><displayName>JMS Connection Factory Implementation Class</displayName><description>The fully qualified name of the JMS ConnectionFactory implementation class (eg. org.apache.activemq.ActiveMQConnectionFactory).</description><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>cflib</name><displayName>JMS Client Libraries</displayName><description>Path to the directory with additional resources (eg. JARs, configuration files etc.) to be added to the classpath (defined as a comma separated list of values). Such resources typically represent target JMS client libraries for the ConnectionFactory implementation.</description><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>true</dynamicallyModifiesClasspath><dynamic>false</dynamic><resourceDefinition><cardinality>MULTIPLE</cardinality><resourceTypes><resourceType>FILE</resourceType><resourceType>URL</resourceType><resourceType>DIRECTORY</resourceType></resourceTypes></resourceDefinition></property><property><name>broker</name><displayName>JMS Broker URI</displayName><description>URI pointing to the network location of the JMS Message broker. Example for ActiveMQ: 'tcp://myhost:61616'. Examples for IBM MQ: 'myhost(1414)' and 'myhost01(1414),myhost02(1414)'.</description><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>SSL Context Service</name><displayName>JMS SSL Context Service</displayName><description>The SSL Context Service used to provide client certificate information for TLS/SSL connections.</description><controllerServiceDefinition><className>org.apache.nifi.ssl.SSLContextService</className><groupId>org.apache.nifi</groupId><artifactId>nifi-standard-services-api-nar</artifactId><version>1.28.0.101-eep-941</version></controllerServiceDefinition><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>NONE</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property></properties><dynamicProperties><dynamicProperty><name>The name of a Connection Factory configuration property.</name><value>The value of a given Connection Factory configuration property.</value><description>Additional configuration property for the Connection Factory. It can be used when the Connection Factory is being configured via the 'JNDI *' or the 'JMS *'properties of the processor. For more information, see the Additional Details page.</description><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope></dynamicProperty></dynamicProperties><relationships><relationship><name>success</name><description>All FlowFiles that are sent to the JMS destination are routed to this relationship</description><autoTerminated>false</autoTerminated></relationship><relationship><name>failure</name><description>All FlowFiles that cannot be sent to JMS destination are routed to this relationship</description><autoTerminated>false</autoTerminated></relationship></relationships><readsAttributes><readsAttribute><name>jms_deliveryMode</name><description>This attribute becomes the JMSDeliveryMode message header. Must be an integer.</description></readsAttribute><readsAttribute><name>jms_expiration</name><description>This attribute becomes the JMSExpiration message header. Must be an integer.</description></readsAttribute><readsAttribute><name>jms_priority</name><description>This attribute becomes the JMSPriority message header. Must be an integer.</description></readsAttribute><readsAttribute><name>jms_redelivered</name><description>This attribute becomes the JMSRedelivered message header.</description></readsAttribute><readsAttribute><name>jms_timestamp</name><description>This attribute becomes the JMSTimestamp message header. Must be a long.</description></readsAttribute><readsAttribute><name>jms_correlationId</name><description>This attribute becomes the JMSCorrelationID message header.</description></readsAttribute><readsAttribute><name>jms_type</name><description>This attribute becomes the JMSType message header. Must be an integer.</description></readsAttribute><readsAttribute><name>jms_replyTo</name><description>This attribute becomes the JMSReplyTo message header. Must be an integer.</description></readsAttribute><readsAttribute><name>jms_destination</name><description>This attribute becomes the JMSDestination message header. Must be an integer.</description></readsAttribute><readsAttribute><name>other attributes</name><description>All other attributes that do not start with jms_ are added as message properties.</description></readsAttribute><readsAttribute><name>other attributes .type</name><description>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).</description></readsAttribute></readsAttributes><writesAttributes></writesAttributes><restricted><restrictions><restriction><requiredPermission>reference remote resources</requiredPermission><explanation>Client Library Location can reference resources over HTTP</explanation></restriction></restrictions></restricted><inputRequirement>INPUT_REQUIRED</inputRequirement><systemResourceConsiderations><systemResourceConsideration><resource>MEMORY</resource><description>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.</description></systemResourceConsideration></systemResourceConsiderations><seeAlso><see>org.apache.nifi.jms.processors.ConsumeJMS</see><see>org.apache.nifi.jms.cf.JMSConnectionFactoryProvider</see></seeAlso></extension><extension><name>org.apache.nifi.jms.cf.JMSConnectionFactoryProvider</name><type>CONTROLLER_SERVICE</type><description>Provides a generic service to create vendor specific javax.jms.ConnectionFactory implementations. The Connection Factory can be served once this service is configured successfully.</description><tags><tag>jms</tag><tag>messaging</tag><tag>integration</tag><tag>queue</tag><tag>topic</tag><tag>publish</tag><tag>subscribe</tag></tags><properties><property><name>cf</name><displayName>JMS Connection Factory Implementation Class</displayName><description>The fully qualified name of the JMS ConnectionFactory implementation class (eg. org.apache.activemq.ActiveMQConnectionFactory).</description><required>true</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>cflib</name><displayName>JMS Client Libraries</displayName><description>Path to the directory with additional resources (eg. JARs, configuration files etc.) to be added to the classpath (defined as a comma separated list of values). Such resources typically represent target JMS client libraries for the ConnectionFactory implementation.</description><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>true</dynamicallyModifiesClasspath><dynamic>false</dynamic><resourceDefinition><cardinality>MULTIPLE</cardinality><resourceTypes><resourceType>FILE</resourceType><resourceType>URL</resourceType><resourceType>DIRECTORY</resourceType></resourceTypes></resourceDefinition></property><property><name>broker</name><displayName>JMS Broker URI</displayName><description>URI pointing to the network location of the JMS Message broker. Example for ActiveMQ: 'tcp://myhost:61616'. Examples for IBM MQ: 'myhost(1414)' and 'myhost01(1414),myhost02(1414)'.</description><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>SSL Context Service</name><displayName>JMS SSL Context Service</displayName><description>The SSL Context Service used to provide client certificate information for TLS/SSL connections.</description><controllerServiceDefinition><className>org.apache.nifi.ssl.SSLContextService</className><groupId>org.apache.nifi</groupId><artifactId>nifi-standard-services-api-nar</artifactId><version>1.28.0.101-eep-941</version></controllerServiceDefinition><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>NONE</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property></properties><dynamicProperties><dynamicProperty><name>The name of a Connection Factory configuration property.</name><value>The value of a given Connection Factory configuration property.</value><description>The properties that are set following Java Beans convention where a property name is derived from the 'set*' method of the vendor specific ConnectionFactory's implementation. For example, 'com.ibm.mq.jms.MQConnectionFactory.setChannel(String)' would imply 'channel' property and 'com.ibm.mq.jms.MQConnectionFactory.setTransportType(int)' would imply 'transportType' property.</description><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope></dynamicProperty></dynamicProperties><restricted><restrictions><restriction><requiredPermission>reference remote resources</requiredPermission><explanation>Client Library Location can reference resources over HTTP</explanation></restriction></restrictions></restricted><seeAlso><see>org.apache.nifi.jms.processors.ConsumeJMS</see><see>org.apache.nifi.jms.processors.PublishJMS</see></seeAlso><providedServiceAPIs><providedServiceAPI><className>org.apache.nifi.jms.cf.JMSConnectionFactoryProviderDefinition</className><groupId>org.apache.nifi</groupId><artifactId>nifi-jms-cf-service-nar</artifactId><version>1.28.0.101-eep-941</version></providedServiceAPI></providedServiceAPIs></extension><extension><name>org.apache.nifi.jms.cf.JndiJmsConnectionFactoryProvider</name><type>CONTROLLER_SERVICE</type><description>Provides a service to lookup an existing JMS ConnectionFactory using the Java Naming and Directory Interface (JNDI).</description><tags><tag>jms</tag><tag>jndi</tag><tag>messaging</tag><tag>integration</tag><tag>queue</tag><tag>topic</tag><tag>publish</tag><tag>subscribe</tag></tags><properties><property><name>java.naming.factory.initial</name><displayName>JNDI Initial Context Factory Class</displayName><description>The fully qualified class name of the JNDI Initial Context Factory Class (java.naming.factory.initial).</description><required>true</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>java.naming.provider.url</name><displayName>JNDI Provider URL</displayName><description>The URL of the JNDI Provider to use as the value for java.naming.provider.url. See additional details documentation for allowed URL schemes.</description><required>true</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>connection.factory.name</name><displayName>JNDI Name of the Connection Factory</displayName><description>The name of the JNDI Object to lookup for the Connection Factory.</description><required>true</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>naming.factory.libraries</name><displayName>JNDI / JMS Client Libraries</displayName><description>Specifies jar files and/or directories to add to the ClassPath in order to load the JNDI / JMS client libraries. This should be a comma-separated list of files, directories, and/or URLs. If a directory is given, any files in that directory will be included, but subdirectories will not be included (i.e., it is not recursive).</description><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>true</dynamicallyModifiesClasspath><dynamic>false</dynamic><resourceDefinition><cardinality>MULTIPLE</cardinality><resourceTypes><resourceType>FILE</resourceType><resourceType>URL</resourceType><resourceType>DIRECTORY</resourceType></resourceTypes></resourceDefinition></property><property><name>java.naming.security.principal</name><displayName>JNDI Principal</displayName><description>The Principal to use when authenticating with JNDI (java.naming.security.principal).</description><required>false</required><sensitive>false</sensitive><expressionLanguageSupported>true</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property><property><name>java.naming.security.credentials</name><displayName>JNDI Credentials</displayName><description>The Credentials to use when authenticating with JNDI (java.naming.security.credentials).</description><required>false</required><sensitive>true</sensitive><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>NONE</expressionLanguageScope><dynamicallyModifiesClasspath>false</dynamicallyModifiesClasspath><dynamic>false</dynamic></property></properties><dynamicProperties><dynamicProperty><name>The name of a JNDI Initial Context environment variable.</name><value>The value of the JNDI Initial Context environment variable.</value><description>In order to perform a JNDI Lookup, an Initial Context must be established. When this is done, an Environment can be established for the context. Any dynamic/user-defined property that is added to this Controller Service will be added as an Environment configuration/variable to this Context.</description><expressionLanguageSupported>false</expressionLanguageSupported><expressionLanguageScope>VARIABLE_REGISTRY</expressionLanguageScope></dynamicProperty></dynamicProperties><seeAlso><see>org.apache.nifi.jms.processors.ConsumeJMS</see><see>org.apache.nifi.jms.processors.PublishJMS</see><see>org.apache.nifi.jms.cf.JMSConnectionFactoryProvider</see></seeAlso><providedServiceAPIs><providedServiceAPI><className>org.apache.nifi.jms.cf.JMSConnectionFactoryProviderDefinition</className><groupId>org.apache.nifi</groupId><artifactId>nifi-jms-cf-service-nar</artifactId><version>1.28.0.101-eep-941</version></providedServiceAPI></providedServiceAPIs></extension></extensions></extensionManifest>