What am I doing wrong with hooking up my activemq jms get template? I put
stuff into the activeMQ and NIFI wont get it. Using 0.4.1.
--
Sincerely,
Chris Hamm
(E) [email protected]
(Twitter) http://twitter.com/webhamm
(Linkedin) http://www.linkedin.com/in/chrishamm
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><template><description></description><name>jms template</name><snippet><connections><id>56f8e76e-e731-41c1-8f29-277cfbbc09c0</id><parentGroupId>51cb06fa-c473-4fc3-befa-0ec229c5ff87</parentGroupId><backPressureDataSizeThreshold>0 MB</backPressureDataSizeThreshold><backPressureObjectThreshold>0</backPressureObjectThreshold><bends><x>622.2763671875</x><y>194.97129821777344</y></bends><bends><x>622.2763671875</x><y>244.97129821777344</y></bends><destination><groupId>51cb06fa-c473-4fc3-befa-0ec229c5ff87</groupId><id>071c2d7c-875e-4a1f-ad49-f874b5ff5605</id><type>PROCESSOR</type></destination><flowFileExpiration>0 sec</flowFileExpiration><labelIndex>1</labelIndex><name></name><selectedRelationships>activity.restored</selectedRelationships><selectedRelationships>inactive</selectedRelationships><selectedRelationships>success</selectedRelationships><source><groupId>51cb06fa-c473-4fc3-befa-0ec229c5ff87</groupId><id>071c2d7c-875e-4a1f-ad49-f874b5ff5605</id><type>PROCESSOR</type></source><zIndex>0</zIndex></connections><connections><id>b8564aac-b081-4349-a94d-4cfbff435380</id><parentGroupId>51cb06fa-c473-4fc3-befa-0ec229c5ff87</parentGroupId><backPressureDataSizeThreshold>0 MB</backPressureDataSizeThreshold><backPressureObjectThreshold>5</backPressureObjectThreshold><destination><groupId>51cb06fa-c473-4fc3-befa-0ec229c5ff87</groupId><id>820558a7-95d9-47ec-a2aa-b637cabf3c97</id><type>PROCESSOR</type></destination><flowFileExpiration>5 sec</flowFileExpiration><labelIndex>1</labelIndex><name></name><selectedRelationships>success</selectedRelationships><source><groupId>51cb06fa-c473-4fc3-befa-0ec229c5ff87</groupId><id>f7dd9023-171a-483f-861f-eb4db68e03d4</id><type>PROCESSOR</type></source><zIndex>0</zIndex></connections><connections><id>b922b9da-f1f3-423d-86f3-03f4977f5163</id><parentGroupId>51cb06fa-c473-4fc3-befa-0ec229c5ff87</parentGroupId><backPressureDataSizeThreshold>0 MB</backPressureDataSizeThreshold><backPressureObjectThreshold>100</backPressureObjectThreshold><destination><groupId>51cb06fa-c473-4fc3-befa-0ec229c5ff87</groupId><id>071c2d7c-875e-4a1f-ad49-f874b5ff5605</id><type>PROCESSOR</type></destination><flowFileExpiration>5 sec</flowFileExpiration><labelIndex>1</labelIndex><name></name><selectedRelationships>success</selectedRelationships><source><groupId>51cb06fa-c473-4fc3-befa-0ec229c5ff87</groupId><id>820558a7-95d9-47ec-a2aa-b637cabf3c97</id><type>PROCESSOR</type></source><zIndex>0</zIndex></connections><processors><id>f7dd9023-171a-483f-861f-eb4db68e03d4</id><parentGroupId>51cb06fa-c473-4fc3-befa-0ec229c5ff87</parentGroupId><position><x>279.19517517089844</x><y>-153.80633544921875</y></position><config><bulletinLevel>WARN</bulletinLevel><comments></comments><concurrentlySchedulableTaskCount>1</concurrentlySchedulableTaskCount><defaultConcurrentTasks><entry><key>TIMER_DRIVEN</key><value>1</value></entry><entry><key>EVENT_DRIVEN</key><value>0</value></entry><entry><key>CRON_DRIVEN</key><value>1</value></entry></defaultConcurrentTasks><defaultSchedulingPeriod><entry><key>TIMER_DRIVEN</key><value>0 sec</value></entry><entry><key>CRON_DRIVEN</key><value>* * * * * ?</value></entry></defaultSchedulingPeriod><descriptors><entry><key>JMS Provider</key><value><allowableValues><displayName>ActiveMQ</displayName><value>ActiveMQ</value></allowableValues><defaultValue>ActiveMQ</defaultValue><description>The Provider used for the JMS Server</description><displayName>JMS Provider</displayName><dynamic>false</dynamic><name>JMS Provider</name><required>true</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry><entry><key>URL</key><value><description>The URL of the JMS Server</description><displayName>URL</displayName><dynamic>false</dynamic><name>URL</name><required>true</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry><entry><key>Destination Name</key><value><description>The name of the JMS Topic or queue to use</description><displayName>Destination Name</displayName><dynamic>false</dynamic><name>Destination Name</name><required>true</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry><entry><key>Communications Timeout</key><value><defaultValue>30 sec</defaultValue><description>The amount of time to wait when attempting to receive a message before giving up and assuming failure</description><displayName>Communications Timeout</displayName><dynamic>false</dynamic><name>Communications Timeout</name><required>true</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry><entry><key>Message Batch Size</key><value><defaultValue>10</defaultValue><description>The number of messages to pull/push in a single iteration of the processor</description><displayName>Message Batch Size</displayName><dynamic>false</dynamic><name>Message Batch Size</name><required>true</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry><entry><key>Username</key><value><description>Username used for authentication and authorization</description><displayName>Username</displayName><dynamic>false</dynamic><name>Username</name><required>false</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry><entry><key>Password</key><value><description>Password used for authentication and authorization</description><displayName>Password</displayName><dynamic>false</dynamic><name>Password</name><required>false</required><sensitive>true</sensitive><supportsEl>false</supportsEl></value></entry><entry><key>SSL Context Service</key><value><description>The Controller Service to use in order to obtain an SSL Context.</description><displayName>SSL Context Service</displayName><dynamic>false</dynamic><identifiesControllerService>org.apache.nifi.ssl.SSLContextService</identifiesControllerService><name>SSL Context Service</name><required>false</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry><entry><key>Acknowledgement Mode</key><value><allowableValues><displayName>Client Acknowledge</displayName><value>Client Acknowledge</value></allowableValues><allowableValues><displayName>Auto Acknowledge</displayName><value>Auto Acknowledge</value></allowableValues><defaultValue>Client Acknowledge</defaultValue><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><displayName>Acknowledgement Mode</displayName><dynamic>false</dynamic><name>Acknowledgement Mode</name><required>true</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry><entry><key>Message Selector</key><value><description>The JMS Message Selector to use in order to narrow the messages that are pulled</description><displayName>Message Selector</displayName><dynamic>false</dynamic><name>Message Selector</name><required>false</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry><entry><key>Copy JMS Properties to Attributes</key><value><allowableValues><displayName>true</displayName><value>true</value></allowableValues><allowableValues><displayName>false</displayName><value>false</value></allowableValues><defaultValue>true</defaultValue><description>Whether or not the JMS Message Properties should be copied to the FlowFile Attributes; if so, the attribute name will be jms.XXX, where XXX is the JMS Property name</description><displayName>Copy JMS Properties to Attributes</displayName><dynamic>false</dynamic><name>Copy JMS Properties to Attributes</name><required>true</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry><entry><key>Client ID Prefix</key><value><description>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</description><displayName>Client ID Prefix</displayName><dynamic>false</dynamic><name>Client ID Prefix</name><required>false</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry></descriptors><lossTolerant>false</lossTolerant><penaltyDuration>30 sec</penaltyDuration><properties><entry><key>JMS Provider</key></entry><entry><key>URL</key><value>localhost</value></entry><entry><key>Destination Name</key><value>faa</value></entry><entry><key>Communications Timeout</key></entry><entry><key>Message Batch Size</key></entry><entry><key>Username</key></entry><entry><key>Password</key></entry><entry><key>SSL Context Service</key></entry><entry><key>Acknowledgement Mode</key></entry><entry><key>Message Selector</key></entry><entry><key>Copy JMS Properties to Attributes</key></entry><entry><key>Client ID Prefix</key></entry></properties><runDurationMillis>0</runDurationMillis><schedulingPeriod>0 sec</schedulingPeriod><schedulingStrategy>TIMER_DRIVEN</schedulingStrategy><yieldDuration>1 sec</yieldDuration></config><name>GetJMSQueue</name><relationships><autoTerminate>false</autoTerminate><description>All FlowFiles are routed to success</description><name>success</name></relationships><state>STOPPED</state><style/><supportsEventDriven>false</supportsEventDriven><supportsParallelProcessing>true</supportsParallelProcessing><type>org.apache.nifi.processors.standard.GetJMSQueue</type></processors><processors><id>820558a7-95d9-47ec-a2aa-b637cabf3c97</id><parentGroupId>51cb06fa-c473-4fc3-befa-0ec229c5ff87</parentGroupId><position><x>789.7225952148438</x><y>-5.361641883850098</y></position><config><bulletinLevel>WARN</bulletinLevel><comments></comments><concurrentlySchedulableTaskCount>1</concurrentlySchedulableTaskCount><defaultConcurrentTasks><entry><key>TIMER_DRIVEN</key><value>1</value></entry><entry><key>EVENT_DRIVEN</key><value>0</value></entry><entry><key>CRON_DRIVEN</key><value>1</value></entry></defaultConcurrentTasks><defaultSchedulingPeriod><entry><key>TIMER_DRIVEN</key><value>0 sec</value></entry><entry><key>CRON_DRIVEN</key><value>* * * * * ?</value></entry></defaultSchedulingPeriod><descriptors><entry><key>Attributes List</key><value><description>Comma separated list of attributes to be included in the resulting JSON. If this value is left empty then all existing Attributes will be included. This list of attributes is case sensitive. If an attribute specified in the list is not found it will be be emitted to the resulting JSON with an empty string or NULL value.</description><displayName>Attributes List</displayName><dynamic>false</dynamic><name>Attributes List</name><required>false</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry><entry><key>Destination</key><value><allowableValues><displayName>flowfile-attribute</displayName><value>flowfile-attribute</value></allowableValues><allowableValues><displayName>flowfile-content</displayName><value>flowfile-content</value></allowableValues><defaultValue>flowfile-attribute</defaultValue><description>Control if JSON value is written as a new flowfile attribute 'JSONAttributes' or written in the flowfile content. Writing to flowfile content will overwrite any existing flowfile content.</description><displayName>Destination</displayName><dynamic>false</dynamic><name>Destination</name><required>true</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry><entry><key>Include Core Attributes</key><value><allowableValues><displayName>true</displayName><value>true</value></allowableValues><allowableValues><displayName>false</displayName><value>false</value></allowableValues><defaultValue>true</defaultValue><description>Determines if the FlowFile org.apache.nifi.flowfile.attributes.CoreAttributes which are contained in every FlowFile should be included in the final JSON value generated.</description><displayName>Include Core Attributes</displayName><dynamic>false</dynamic><name>Include Core Attributes</name><required>true</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry><entry><key>Null Value</key><value><allowableValues><displayName>true</displayName><value>true</value></allowableValues><allowableValues><displayName>false</displayName><value>false</value></allowableValues><defaultValue>false</defaultValue><description>If true a non existing or empty attribute will be NULL in the resulting JSON. If false an empty string will be placed in the JSON</description><displayName>Null Value</displayName><dynamic>false</dynamic><name>Null Value</name><required>true</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry></descriptors><lossTolerant>false</lossTolerant><penaltyDuration>30 sec</penaltyDuration><properties><entry><key>Attributes List</key></entry><entry><key>Destination</key></entry><entry><key>Include Core Attributes</key></entry><entry><key>Null Value</key></entry></properties><runDurationMillis>0</runDurationMillis><schedulingPeriod>0 sec</schedulingPeriod><schedulingStrategy>TIMER_DRIVEN</schedulingStrategy><yieldDuration>1 sec</yieldDuration></config><name>AttributesToJSON</name><relationships><autoTerminate>true</autoTerminate><description>Failed to convert attributes to JSON</description><name>failure</name></relationships><relationships><autoTerminate>false</autoTerminate><description>Successfully converted attributes to JSON</description><name>success</name></relationships><state>STOPPED</state><style/><supportsEventDriven>true</supportsEventDriven><supportsParallelProcessing>true</supportsParallelProcessing><type>org.apache.nifi.processors.standard.AttributesToJSON</type></processors><processors><id>5b40423e-1cb5-451a-b6d0-966fcf1e3ed7</id><parentGroupId>51cb06fa-c473-4fc3-befa-0ec229c5ff87</parentGroupId><position><x>227.2763671875</x><y>-42.80633544921875</y></position><config><bulletinLevel>WARN</bulletinLevel><comments></comments><concurrentlySchedulableTaskCount>1</concurrentlySchedulableTaskCount><defaultConcurrentTasks><entry><key>TIMER_DRIVEN</key><value>1</value></entry><entry><key>EVENT_DRIVEN</key><value>0</value></entry><entry><key>CRON_DRIVEN</key><value>1</value></entry></defaultConcurrentTasks><defaultSchedulingPeriod><entry><key>TIMER_DRIVEN</key><value>0 sec</value></entry><entry><key>CRON_DRIVEN</key><value>* * * * * ?</value></entry></defaultSchedulingPeriod><descriptors><entry><key>JMS Provider</key><value><allowableValues><displayName>ActiveMQ</displayName><value>ActiveMQ</value></allowableValues><defaultValue>ActiveMQ</defaultValue><description>The Provider used for the JMS Server</description><displayName>JMS Provider</displayName><dynamic>false</dynamic><name>JMS Provider</name><required>true</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry><entry><key>URL</key><value><description>The URL of the JMS Server</description><displayName>URL</displayName><dynamic>false</dynamic><name>URL</name><required>true</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry><entry><key>Destination Name</key><value><description>The name of the JMS Topic or queue to use</description><displayName>Destination Name</displayName><dynamic>false</dynamic><name>Destination Name</name><required>true</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry><entry><key>Destination Type</key><value><allowableValues><displayName>Queue</displayName><value>Queue</value></allowableValues><allowableValues><displayName>Topic</displayName><value>Topic</value></allowableValues><defaultValue>Queue</defaultValue><description>The type of the JMS Destination to use</description><displayName>Destination Type</displayName><dynamic>false</dynamic><name>Destination Type</name><required>true</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry><entry><key>Communications Timeout</key><value><defaultValue>30 sec</defaultValue><description>The amount of time to wait when attempting to receive a message before giving up and assuming failure</description><displayName>Communications Timeout</displayName><dynamic>false</dynamic><name>Communications Timeout</name><required>true</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry><entry><key>Message Batch Size</key><value><defaultValue>10</defaultValue><description>The number of messages to pull/push in a single iteration of the processor</description><displayName>Message Batch Size</displayName><dynamic>false</dynamic><name>Message Batch Size</name><required>true</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry><entry><key>Username</key><value><description>Username used for authentication and authorization</description><displayName>Username</displayName><dynamic>false</dynamic><name>Username</name><required>false</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry><entry><key>Password</key><value><description>Password used for authentication and authorization</description><displayName>Password</displayName><dynamic>false</dynamic><name>Password</name><required>false</required><sensitive>true</sensitive><supportsEl>false</supportsEl></value></entry><entry><key>SSL Context Service</key><value><description>The Controller Service to use in order to obtain an SSL Context.</description><displayName>SSL Context Service</displayName><dynamic>false</dynamic><identifiesControllerService>org.apache.nifi.ssl.SSLContextService</identifiesControllerService><name>SSL Context Service</name><required>false</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry><entry><key>Message Type</key><value><allowableValues><displayName>byte</displayName><value>byte</value></allowableValues><allowableValues><displayName>stream</displayName><value>stream</value></allowableValues><allowableValues><displayName>text</displayName><value>text</value></allowableValues><allowableValues><displayName>map</displayName><value>map</value></allowableValues><allowableValues><displayName>empty</displayName><value>empty</value></allowableValues><defaultValue>byte</defaultValue><description>The Type of JMS Message to Construct</description><displayName>Message Type</displayName><dynamic>false</dynamic><name>Message Type</name><required>true</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry><entry><key>Message Priority</key><value><description>The Priority of the Message</description><displayName>Message Priority</displayName><dynamic>false</dynamic><name>Message Priority</name><required>false</required><sensitive>false</sensitive><supportsEl>true</supportsEl></value></entry><entry><key>Reply-To Queue</key><value><description>The name of the queue to which a reply to should be added</description><displayName>Reply-To Queue</displayName><dynamic>false</dynamic><name>Reply-To Queue</name><required>false</required><sensitive>false</sensitive><supportsEl>true</supportsEl></value></entry><entry><key>Max Buffer Size</key><value><defaultValue>1 MB</defaultValue><description>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.</description><displayName>Max Buffer Size</displayName><dynamic>false</dynamic><name>Max Buffer Size</name><required>true</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry><entry><key>Message Time to Live</key><value><description>The amount of time that the message should live on the destination before being removed; if not specified, the message will never expire.</description><displayName>Message Time to Live</displayName><dynamic>false</dynamic><name>Message Time to Live</name><required>false</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry><entry><key>Copy Attributes to JMS Properties</key><value><allowableValues><displayName>true</displayName><value>true</value></allowableValues><allowableValues><displayName>false</displayName><value>false</value></allowableValues><defaultValue>true</defaultValue><description>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.</description><displayName>Copy Attributes to JMS Properties</displayName><dynamic>false</dynamic><name>Copy Attributes to JMS Properties</name><required>true</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry><entry><key>Client ID Prefix</key><value><description>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</description><displayName>Client ID Prefix</displayName><dynamic>false</dynamic><name>Client ID Prefix</name><required>false</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry></descriptors><lossTolerant>false</lossTolerant><penaltyDuration>30 sec</penaltyDuration><properties><entry><key>JMS Provider</key></entry><entry><key>URL</key></entry><entry><key>Destination Name</key></entry><entry><key>Destination Type</key></entry><entry><key>Communications Timeout</key></entry><entry><key>Message Batch Size</key></entry><entry><key>Username</key></entry><entry><key>Password</key></entry><entry><key>SSL Context Service</key></entry><entry><key>Message Type</key></entry><entry><key>Message Priority</key></entry><entry><key>Reply-To Queue</key></entry><entry><key>Max Buffer Size</key></entry><entry><key>Message Time to Live</key></entry><entry><key>Copy Attributes to JMS Properties</key></entry><entry><key>Client ID Prefix</key></entry></properties><runDurationMillis>0</runDurationMillis><schedulingPeriod>0 sec</schedulingPeriod><schedulingStrategy>TIMER_DRIVEN</schedulingStrategy><yieldDuration>1 sec</yieldDuration></config><name>PutJMS</name><relationships><autoTerminate>false</autoTerminate><description>All FlowFiles that cannot be routed to the JMS destination are routed to this relationship</description><name>failure</name></relationships><relationships><autoTerminate>false</autoTerminate><description>All FlowFiles that are sent to the JMS destination are routed to this relationship</description><name>success</name></relationships><state>STOPPED</state><style/><supportsEventDriven>false</supportsEventDriven><supportsParallelProcessing>true</supportsParallelProcessing><type>org.apache.nifi.processors.standard.PutJMS</type></processors><processors><id>071c2d7c-875e-4a1f-ad49-f874b5ff5605</id><parentGroupId>51cb06fa-c473-4fc3-befa-0ec229c5ff87</parentGroupId><position><x>213.2763671875</x><y>169.97129821777344</y></position><config><bulletinLevel>WARN</bulletinLevel><comments></comments><concurrentlySchedulableTaskCount>1</concurrentlySchedulableTaskCount><defaultConcurrentTasks><entry><key>TIMER_DRIVEN</key><value>1</value></entry><entry><key>EVENT_DRIVEN</key><value>0</value></entry><entry><key>CRON_DRIVEN</key><value>1</value></entry></defaultConcurrentTasks><defaultSchedulingPeriod><entry><key>TIMER_DRIVEN</key><value>0 sec</value></entry><entry><key>CRON_DRIVEN</key><value>* * * * * ?</value></entry></defaultSchedulingPeriod><descriptors><entry><key>Threshold Duration</key><value><defaultValue>5 min</defaultValue><description>Determines how much time must elapse before considering the flow to be inactive</description><displayName>Threshold Duration</displayName><dynamic>false</dynamic><name>Threshold Duration</name><required>true</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry><entry><key>Continually Send Messages</key><value><allowableValues><displayName>true</displayName><value>true</value></allowableValues><allowableValues><displayName>false</displayName><value>false</value></allowableValues><defaultValue>false</defaultValue><description>If true, will send inactivity indicator continually every Threshold Duration amount of time until activity is restored; if false, will send an indicator only when the flow first becomes inactive</description><displayName>Continually Send Messages</displayName><dynamic>false</dynamic><name>Continually Send Messages</name><required>true</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry><entry><key>Inactivity Message</key><value><defaultValue>Lacking activity as of time: ${now():format('yyyy/MM/dd HH:mm:ss')}; flow has been inactive for ${inactivityDurationMillis:toNumber():divide(60000)} minutes</defaultValue><description>The message that will be the content of FlowFiles that are sent to the 'inactive' relationship</description><displayName>Inactivity Message</displayName><dynamic>false</dynamic><name>Inactivity Message</name><required>true</required><sensitive>false</sensitive><supportsEl>true</supportsEl></value></entry><entry><key>Activity Restored Message</key><value><defaultValue>Activity restored at time: ${now():format('yyyy/MM/dd HH:mm:ss')} after being inactive for ${inactivityDurationMillis:toNumber():divide(60000)} minutes</defaultValue><description>The message that will be the content of FlowFiles that are sent to 'activity.restored' relationship</description><displayName>Activity Restored Message</displayName><dynamic>false</dynamic><name>Activity Restored Message</name><required>true</required><sensitive>false</sensitive><supportsEl>true</supportsEl></value></entry><entry><key>Copy Attributes</key><value><allowableValues><displayName>true</displayName><value>true</value></allowableValues><allowableValues><displayName>false</displayName><value>false</value></allowableValues><defaultValue>false</defaultValue><description>If true, will copy all flow file attributes from the flow file that resumed activity to the newly created indicator flow file</description><displayName>Copy Attributes</displayName><dynamic>false</dynamic><name>Copy Attributes</name><required>false</required><sensitive>false</sensitive><supportsEl>false</supportsEl></value></entry></descriptors><lossTolerant>false</lossTolerant><penaltyDuration>30 sec</penaltyDuration><properties><entry><key>Threshold Duration</key></entry><entry><key>Continually Send Messages</key></entry><entry><key>Inactivity Message</key></entry><entry><key>Activity Restored Message</key></entry><entry><key>Copy Attributes</key></entry></properties><runDurationMillis>0</runDurationMillis><schedulingPeriod>0 sec</schedulingPeriod><schedulingStrategy>TIMER_DRIVEN</schedulingStrategy><yieldDuration>1 sec</yieldDuration></config><name>MonitorActivity</name><relationships><autoTerminate>false</autoTerminate><description>This relationship is used to transfer an Activity Restored indicator when FlowFiles are routing to 'success' following a period of inactivity</description><name>activity.restored</name></relationships><relationships><autoTerminate>false</autoTerminate><description>This relationship is used to transfer an Inactivity indicator when no FlowFiles are routed to 'success' for Threshold Duration amount of time</description><name>inactive</name></relationships><relationships><autoTerminate>false</autoTerminate><description>All incoming FlowFiles are routed to success</description><name>success</name></relationships><state>STOPPED</state><style/><supportsEventDriven>false</supportsEventDriven><supportsParallelProcessing>false</supportsParallelProcessing><type>org.apache.nifi.processors.standard.MonitorActivity</type></processors></snippet><timestamp>01/06/2016 17:17:42 EST</timestamp></template>
