Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutDatabaseRecord/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutDatabaseRecord/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutDatabaseRecord/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutDatabaseRecord/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>PutDatabaseRecord</title><link rel="stylesheet" 
href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">PutDatabaseRecord</h1><h2>Description: </h2><p>The PutDatabaseRecord 
processor uses a specified RecordReader to input (possibly multiple) records 
from an incoming flow file. These records are translated to SQL statements and 
executed as a single batch. If any errors occur, the flow file is routed to 
failure or retry, and if the records are transmitted successfully, the incoming 
flow file is routed to success.  The type of statement executed by the 
processor is specified via the Statement Type property, which accepts some 
hard-coded values such as INSERT, UPDATE, and DELETE, as well as 'Use sta
 tement.type Attribute', which causes the processor to get the statement type 
from a flow file attribute.  IMPORTANT: If the Statement Type is UPDATE, then 
the incoming records must not alter the value(s) of the primary keys (or 
user-specified Update Keys). If such records are encountered, the UPDATE 
statement issued to the database may do nothing (if no existing records with 
the new primary key values are found), or could inadvertently corrupt the 
existing data (by changing records for which the new values of the primary keys 
exist).</p><h3>Tags: </h3><p>sql, record, jdbc, put, database, update, insert, 
delete</p><h3>Properties: </h3><p>In the list below, the names of required 
properties appear in <strong>bold</strong>. Any other properties (not in bold) 
are considered optional. The table also indicates any default values, and 
whether a property supports the <a 
href="../../../../../html/expression-language-guide.html">NiFi Expression 
Language</a>.</p><table id="properties"><tr><th>N
 ame</th><th>Default Value</th><th>Allowable 
Values</th><th>Description</th></tr><tr><td id="name"><strong>Record 
Reader</strong></td><td id="default-value"></td><td 
id="allowable-values"><strong>Controller Service API: 
</strong><br/>RecordReaderFactory<br/><strong>Implementations: </strong><a 
href="../../../nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.avro.AvroReader/index.html">AvroReader</a><br/><a
 
href="../../../nifi-scripting-nar/1.6.0/org.apache.nifi.record.script.ScriptedReader/index.html">ScriptedReader</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.json.JsonPathReader/index.html">JsonPathReader</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.grok.GrokReader/index.html">GrokReader</a><br/><a
 
href="../../../nifi-record-serialization-services-nar/1.6.0/org.apache.nifi.csv.CSVReader/index.html">CSVReader</a><br/><a
 href="../../../nifi-record-serialization-services-nar/1.6.0/org.apache.
 nifi.json.JsonTreeReader/index.html">JsonTreeReader</a></td><td 
id="description">Specifies the Controller Service to use for parsing incoming 
data and determining the data's schema.</td></tr><tr><td 
id="name"><strong>Statement Type</strong></td><td id="default-value"></td><td 
id="allowable-values"><ul><li>UPDATE</li><li>INSERT</li><li>DELETE</li><li>Use 
statement.type Attribute</li></ul></td><td id="description">Specifies the type 
of SQL Statement to generate. If 'Use statement.type Attribute' is chosen, then 
the value is taken from the statement.type attribute in the FlowFile. The 'Use 
statement.type Attribute' option is the only one that allows the 'SQL' 
statement type. If 'SQL' is specified, the value of the field specified by the 
'Field Containing SQL' property is expected to be a valid SQL statement on the 
target database, and will be executed as-is.</td></tr><tr><td 
id="name"><strong>Database Connection Pooling Service</strong></td><td 
id="default-value"></td><td id="allowable
 -values"><strong>Controller Service API: 
</strong><br/>DBCPService<br/><strong>Implementations: </strong><a 
href="../../../nifi-dbcp-service-nar/1.6.0/org.apache.nifi.dbcp.DBCPConnectionPool/index.html">DBCPConnectionPool</a><br/><a
 
href="../../../nifi-hive-nar/1.6.0/org.apache.nifi.dbcp.hive.HiveConnectionPool/index.html">HiveConnectionPool</a></td><td
 id="description">The Controller Service that is used to obtain a connection to 
the database for sending records.</td></tr><tr><td id="name">Catalog 
Name</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The name of the catalog that the statement should update. This 
may not apply for the database that you are updating. In this case, leave the 
field empty<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Schema Name</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
name of the schema that the table belongs to. This may not apply for
  the database that you are updating. In this case, leave the field 
empty<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name"><strong>Table Name</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The name of the table that the 
statement should affect.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Translate Field Names</td><td 
id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">If true, the Processor will attempt to translate field names 
into the appropriate column names for the table specified. If false, the field 
names must match the column names exactly, or the column will not be 
updated</td></tr><tr><td id="name">Unmatched Field Behavior</td><td 
id="default-value">Ignore Unmatched Fields</td><td 
id="allowable-values"><ul><li>Ignore Unmatched Fields <img 
src="../../../../../html/images/iconInfo.png" alt="Any fi
 eld in the document that cannot be mapped to a column in the database is 
ignored" title="Any field in the document that cannot be mapped to a column in 
the database is ignored"></img></li><li>Fail on Unmatched Fields <img 
src="../../../../../html/images/iconInfo.png" alt="If the document has any 
field that cannot be mapped to a column in the database, the FlowFile will be 
routed to the failure relationship" title="If the document has any field that 
cannot be mapped to a column in the database, the FlowFile will be routed to 
the failure relationship"></img></li></ul></td><td id="description">If an 
incoming record has a field that does not map to any of the database table's 
columns, this property specifies how to handle the situation</td></tr><tr><td 
id="name">Unmatched Column Behavior</td><td id="default-value">Fail on 
Unmatched Columns</td><td id="allowable-values"><ul><li>Ignore Unmatched 
Columns <img src="../../../../../html/images/iconInfo.png" alt="Any column in 
the database tha
 t does not have a field in the document will be assumed to not be required.  
No notification will be logged" title="Any column in the database that does not 
have a field in the document will be assumed to not be required.  No 
notification will be logged"></img></li><li>Warn on Unmatched Columns <img 
src="../../../../../html/images/iconInfo.png" alt="Any column in the database 
that does not have a field in the document will be assumed to not be required.  
A warning will be logged" title="Any column in the database that does not have 
a field in the document will be assumed to not be required.  A warning will be 
logged"></img></li><li>Fail on Unmatched Columns <img 
src="../../../../../html/images/iconInfo.png" alt="A flow will fail if any 
column in the database that does not have a field in the document.  An error 
will be logged" title="A flow will fail if any column in the database that does 
not have a field in the document.  An error will be 
logged"></img></li></ul></td><td id="descr
 iption">If an incoming record does not have a field mapping for all of the 
database table's columns, this property specifies how to handle the 
situation</td></tr><tr><td id="name">Update Keys</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">A 
comma-separated list of column names that uniquely identifies a row in the 
database for UPDATE statements. If the Statement Type is UPDATE and this 
property is not set, the table's Primary Keys are used. In this case, if no 
Primary Key exists, the conversion to SQL will fail if Unmatched Column 
Behaviour is set to FAIL. This property is ignored if the Statement Type is 
INSERT<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name">Field Containing SQL</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">If the Statement Type is 'SQL' 
(as set in the statement.type attribute), this field indicates which field in 
the record(s) contains the SQL statement to
  execute. The value of the field must be a single SQL statement. If the 
Statement Type is not 'SQL', this field is ignored.<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name">Quote Column 
Identifiers</td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Enabling this option will cause all column names to be quoted, 
allowing you to use reserved words as column names in your 
tables.</td></tr><tr><td id="name">Quote Table Identifiers</td><td 
id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Enabling this option will cause the table name to be quoted to 
support the use of special characters in the table name.</td></tr><tr><td 
id="name"><strong>Max Wait Time</strong></td><td id="default-value">0 
seconds</td><td id="allowable-values"></td><td id="description">The maximum 
amount of time allowed for a running SQL statement 
 , zero means there is no limit. Max time less than 1 second will be equal to 
zero.<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name"><strong>Rollback On Failure</strong></td><td 
id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Specify how to handle error. By default (false), if an error 
occurs while processing a FlowFile, the FlowFile will be routed to 'failure' or 
'retry' relationship based on error type, and processor can continue with next 
FlowFile. Instead, you may want to rollback currently processed FlowFiles and 
stop further processing immediately. In that case, you can do so by enabling 
this 'Rollback On Failure' property.  If enabled, failed FlowFiles will stay in 
the input relationship without penalizing it and being processed repeatedly 
until it gets processed successfully or removed by other means. It is important 
to set adequate 'Yield Duration' to avoid retrying too fre
 quently.</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>retry</td><td>A
 FlowFile is routed to this relationship if the database cannot be updated but 
attempting the operation again may 
succeed</td></tr><tr><td>success</td><td>Successfully created FlowFile from SQL 
query result set.</td></tr><tr><td>failure</td><td>A FlowFile is routed to this 
relationship if the database cannot be updated and retrying the operation will 
also fail, such as an invalid query or an integrity constraint 
violation</td></tr></table><h3>Reads Attributes: </h3><table 
id="reads-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>statement.type</td><td>If
 'Use statement.type Attribute' is selected for the Statement Type property, 
the value of this attribute will be used to determine the type of statement 
(INSERT, UPDATE, DELETE, SQL, etc.) to generate and 
execute.</td></tr></table><h3>Writes Attributes: </h3><table id="writes-attri
 
butes"><tr><th>Name</th><th>Description</th></tr><tr><td>putdatabaserecord.error</td><td>If
 an error occurs during processing, the flow file will be routed to failure or 
retry, and this attribute will be populated with the cause of the 
error.</td></tr></table><h3>State management: </h3>This component does not 
store state.<h3>Restricted: </h3>This component is not restricted.<h3>Input 
requirement: </h3>This component requires an incoming relationship.<h3>System 
Resource Considerations:</h3>None specified.</body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutDistributedMapCache/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutDistributedMapCache/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutDistributedMapCache/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutDistributedMapCache/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>PutDistributedMapCache</title><link 
rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">PutDistributedMapCache</h1><h2>Description: </h2><p>Gets the content of 
a FlowFile and puts it to a distributed map cache, using a cache key computed 
from FlowFile attributes. If the cache already contains the entry and the cache 
update strategy is 'keep original' the entry is not replaced.'</p><h3>Tags: 
</h3><p>map, cache, put, distributed</p><h3>Properties: </h3><p>In the list 
below, the names of required properties appear in <strong>bold</strong>. Any 
other properties (not in bold) are considered optional. The table also 
indicates any default values, and whether a property supports the
  <a href="../../../../../html/expression-language-guide.html">NiFi Expression 
Language</a>.</p><table id="properties"><tr><th>Name</th><th>Default 
Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td 
id="name"><strong>Cache Entry Identifier</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">A 
FlowFile attribute, or the results of an Attribute Expression Language 
statement, which will be evaluated against a FlowFile in order to determine the 
cache key<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Distributed Cache 
Service</strong></td><td id="default-value"></td><td 
id="allowable-values"><strong>Controller Service API: 
</strong><br/>DistributedMapCacheClient<br/><strong>Implementations: 
</strong><a 
href="../../../nifi-redis-nar/1.6.0/org.apache.nifi.redis.service.RedisDistributedMapCacheClientService/index.html">RedisDistributedMapCacheClientService</a><br/><a
 href="../../../nifi-dis
 
tributed-cache-services-nar/1.6.0/org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService/index.html">DistributedMapCacheClientService</a><br/><a
 
href="../../../nifi-hbase_1_1_2-client-service-nar/1.6.0/org.apache.nifi.hbase.HBase_1_1_2_ClientMapCacheService/index.html">HBase_1_1_2_ClientMapCacheService</a></td><td
 id="description">The Controller Service that is used to cache flow 
files</td></tr><tr><td id="name"><strong>Cache update strategy</strong></td><td 
id="default-value">replace</td><td id="allowable-values"><ul><li>Replace if 
present <img src="../../../../../html/images/iconInfo.png" alt="Adds the 
specified entry to the cache, replacing any value that is currently set." 
title="Adds the specified entry to the cache, replacing any value that is 
currently set."></img></li><li>Keep original <img 
src="../../../../../html/images/iconInfo.png" alt="Adds the specified entry to 
the cache, if the key does not exist." title="Adds the specified entry to the 
cache, if t
 he key does not exist."></img></li></ul></td><td id="description">Determines 
how the cache is updated if the cache already contains the 
entry</td></tr><tr><td id="name">Max cache entry size</td><td 
id="default-value">1 MB</td><td id="allowable-values"></td><td 
id="description">The maximum amount of data to put into 
cache</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>Any
 FlowFile that is successfully inserted into cache will be routed to this 
relationship</td></tr><tr><td>failure</td><td>Any FlowFile that cannot be 
inserted into the cache will be routed to this 
relationship</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>Writes Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>cached</td><td>All
 FlowFiles will have an attribute 'cached'. The value of this attribute is 
true, is the FlowFile is cached, otherwise false.</td></tr></table><h3
 >State management: </h3>This component does not store state.<h3>Restricted: 
 ></h3>This component is not restricted.<h3>Input requirement: </h3>This 
 >component requires an incoming relationship.<h3>System Resource 
 >Considerations:</h3>None specified.<h3>See Also:</h3><p><a 
 >href="../../../nifi-distributed-cache-services-nar/1.6.0/org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService/index.html">DistributedMapCacheClientService</a>,
 > <a 
 >href="../../../nifi-distributed-cache-services-nar/1.6.0/org.apache.nifi.distributed.cache.server.map.DistributedMapCacheServer/index.html">DistributedMapCacheServer</a>,
 > <a 
 >href="../org.apache.nifi.processors.standard.FetchDistributedMapCache/index.html">FetchDistributedMapCache</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutEmail/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutEmail/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutEmail/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutEmail/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>PutEmail</title><link rel="stylesheet" 
href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">PutEmail</h1><h2>Description: </h2><p>Sends an e-mail to configured 
recipients for each incoming FlowFile</p><h3>Tags: </h3><p>email, put, notify, 
smtp</p><h3>Properties: </h3><p>In the list below, the names of required 
properties appear in <strong>bold</strong>. Any other properties (not in bold) 
are considered optional. The table also indicates any default values, whether a 
property supports the <a 
href="../../../../../html/expression-language-guide.html">NiFi Expression 
Language</a>, and whether a property is considered "sensitive", meaning that 
its value will be encrypted. Before entering a value i
 n a sensitive property, ensure that the <strong>nifi.properties</strong> file 
has an entry for the property 
<strong>nifi.sensitive.props.key</strong>.</p><table 
id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><th>Description</th></tr><tr><td id="name"><strong>SMTP 
Hostname</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The hostname of the SMTP 
host<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name"><strong>SMTP Port</strong></td><td id="default-value">25</td><td 
id="allowable-values"></td><td id="description">The Port used for SMTP 
communications<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">SMTP Username</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Username for the SMTP account<br/><strong>Supports Expression 
Language: true</strong></td></tr><tr><td id="name">SMTP Password</td><td 
id="default-value"
 ></td><td id="allowable-values"></td><td id="description">Password for the 
 >SMTP account<br/><strong>Sensitive Property: 
 >true</strong><br/><strong>Supports Expression Language: 
 >true</strong></td></tr><tr><td id="name"><strong>SMTP Auth</strong></td><td 
 >id="default-value">true</td><td id="allowable-values"></td><td 
 >id="description">Flag indicating whether authentication should be 
 >used<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
 >id="name"><strong>SMTP TLS</strong></td><td id="default-value">false</td><td 
 >id="allowable-values"></td><td id="description">Flag indicating whether TLS 
 >should be enabled<br/><strong>Supports Expression Language: 
 >true</strong></td></tr><tr><td id="name"><strong>SMTP Socket 
 >Factory</strong></td><td 
 >id="default-value">javax.net.ssl.SSLSocketFactory</td><td 
 >id="allowable-values"></td><td id="description">Socket Factory to use for 
 >SMTP Connection<br/><strong>Supports Expression Language: 
 >true</strong></td></tr><tr><td id="name"><strong>
 SMTP X-Mailer Header</strong></td><td id="default-value">NiFi</td><td 
id="allowable-values"></td><td id="description">X-Mailer used in the header of 
the outgoing email<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Content Type</strong></td><td 
id="default-value">text/plain</td><td id="allowable-values"></td><td 
id="description">Mime Type used to interpret the contents of the email, such as 
text/plain or text/html<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>From</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Specifies the Email address to use as the 
sender<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name">To</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The recipients to include in the To-Line of the 
email<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
 id="name">CC</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The recipients to include in 
the CC-Line of the email<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">BCC</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
recipients to include in the BCC-Line of the email<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td 
id="name"><strong>Subject</strong></td><td id="default-value">Message from 
NiFi</td><td id="allowable-values"></td><td id="description">The email 
subject<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Message</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
body of the email message<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Flow file content as 
message</strong></td><td id="default-value">false</td><td id="allowable-valu
 es"></td><td id="description">Specifies whether or not the FlowFile content 
should be the message of the email. If true, the 'Message' property is 
ignored.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Attach File</strong></td><td 
id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Specifies whether or not the FlowFile content should be 
attached to the email</td></tr><tr><td id="name"><strong>Include All Attributes 
In Message</strong></td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Specifies whether or not all FlowFile attributes should be 
recorded in the body of the email message</td></tr></table><h3>Relationships: 
</h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>FlowFiles
 that are successfully sent will be routed to this relationship</td></tr><tr><td
 >failure</td><td>FlowFiles that fail to send will be routed to this 
 >relationship</td></tr></table><h3>Reads Attributes: </h3>None 
 >specified.<h3>Writes Attributes: </h3>None specified.<h3>State management: 
 ></h3>This component does not store state.<h3>Restricted: </h3>This component 
 >is not restricted.<h3>Input requirement: </h3>This component requires an 
 >incoming relationship.<h3>System Resource Considerations:</h3><table 
 >id="system-resource-considerations"><tr><th>Resource</th><th>Description</th></tr><tr><td>MEMORY</td><td>The
 > entirety of the FlowFile's content (as a String object) will be read into 
 >memory in case the property to use the flow file content as the email body is 
 >set to true.</td></tr></table></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutFTP/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutFTP/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutFTP/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutFTP/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>PutFTP</title><link rel="stylesheet" 
href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">PutFTP</h1><h2>Description: </h2><p>Sends FlowFiles to an FTP 
Server</p><h3>Tags: </h3><p>remote, copy, egress, put, ftp, archive, 
files</p><h3>Properties: </h3><p>In the list below, the names of required 
properties appear in <strong>bold</strong>. Any other properties (not in bold) 
are considered optional. The table also indicates any default values, whether a 
property supports the <a 
href="../../../../../html/expression-language-guide.html">NiFi Expression 
Language</a>, and whether a property is considered "sensitive", meaning that 
its value will be encrypted. Before entering a value in a sensitive pro
 perty, ensure that the <strong>nifi.properties</strong> file has an entry for 
the property <strong>nifi.sensitive.props.key</strong>.</p><table 
id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><th>Description</th></tr><tr><td 
id="name"><strong>Hostname</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The fully qualified hostname or 
IP address of the remote system<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Port</strong></td><td 
id="default-value">21</td><td id="allowable-values"></td><td 
id="description">The port that the remote system is listening on for file 
transfers<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Username</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Username<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Password</td>
 <td id="default-value"></td><td id="allowable-values"></td><td 
id="description">Password for the user account<br/><strong>Sensitive Property: 
true</strong><br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Remote Path</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
path on the remote system from which to pull or push files<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name"><strong>Create 
Directory</strong></td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Specifies whether or not the remote directory should be 
created if it does not exist.</td></tr><tr><td id="name"><strong>Batch 
Size</strong></td><td id="default-value">500</td><td 
id="allowable-values"></td><td id="description">The maximum number of FlowFiles 
to send in a single connection</td></tr><tr><td id="name"><strong>Connection 
Timeout</strong></td
 ><td id="default-value">30 sec</td><td id="allowable-values"></td><td 
 >id="description">Amount of time to wait before timing out while creating a 
 >connection</td></tr><tr><td id="name"><strong>Data Timeout</strong></td><td 
 >id="default-value">30 sec</td><td id="allowable-values"></td><td 
 >id="description">When transferring a file between the local and remote 
 >system, this value specifies how long is allowed to elapse without any data 
 >being transferred between systems</td></tr><tr><td id="name"><strong>Conflict 
 >Resolution</strong></td><td id="default-value">NONE</td><td 
 >id="allowable-values"><ul><li>REPLACE</li><li>IGNORE</li><li>RENAME</li><li>REJECT</li><li>FAIL</li><li>NONE</li></ul></td><td
 > id="description">Determines how to handle the problem of filename 
 >collisions</td></tr><tr><td id="name">Dot Rename</td><td 
 >id="default-value">true</td><td 
 >id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
 >id="description">If true, then the filename of the sent file is prepended wit
 h a "." and then renamed back to the original once the file is completely 
sent. Otherwise, there is no rename. This property is ignored if the Temporary 
Filename property is set.</td></tr><tr><td id="name">Temporary Filename</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">If 
set, the filename of the sent file will be equal to the value specified during 
the transfer and after successful completion will be renamed to the original 
filename. If this value is set, the Dot Rename property is 
ignored.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Transfer Mode</td><td 
id="default-value">Binary</td><td 
id="allowable-values"><ul><li>Binary</li><li>ASCII</li></ul></td><td 
id="description">The FTP Transfer Mode</td></tr><tr><td id="name">Connection 
Mode</td><td id="default-value">Passive</td><td 
id="allowable-values"><ul><li>Active</li><li>Passive</li></ul></td><td 
id="description">The FTP Connection Mode</td></tr><tr><td
  id="name">Reject Zero-Byte Files</td><td id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Determines whether or not Zero-byte files should be rejected 
without attempting to transfer</td></tr><tr><td id="name">Last Modified 
Time</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The lastModifiedTime to assign to the file after transferring 
it. If not set, the lastModifiedTime will not be changed. Format must be 
yyyy-MM-dd'T'HH:mm:ssZ. You may also use expression language such as 
${file.lastModifiedTime}. If the value is invalid, the processor will not be 
invalid but will fail to change lastModifiedTime of the 
file.<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name">Permissions</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The permissions to assign to 
the file after transferring it. Format must be either UNIX rwxrwxr
 wx with a - in place of denied permissions (e.g. rw-r--r--) or an octal number 
(e.g. 644). If not set, the permissions will not be changed. You may also use 
expression language such as ${file.permissions}. If the value is invalid, the 
processor will not be invalid but will fail to change permissions of the 
file.<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name"><strong>Use Compression</strong></td><td 
id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Indicates whether or not ZLIB compression should be used when 
transferring files</td></tr><tr><td id="name">Proxy Type</td><td 
id="default-value">DIRECT</td><td 
id="allowable-values"><ul><li>DIRECT</li><li>HTTP</li><li>SOCKS</li></ul></td><td
 id="description">Proxy type used for file transfers</td></tr><tr><td 
id="name">Proxy Host</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The fully qualified hostn
 ame or IP address of the proxy server</td></tr><tr><td id="name">Proxy 
Port</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The port of the proxy server</td></tr><tr><td id="name">Http 
Proxy Username</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Http Proxy 
Username</td></tr><tr><td id="name">Http Proxy Password</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Http Proxy Password<br/><strong>Sensitive Property: 
true</strong></td></tr><tr><td id="name">Internal Buffer Size</td><td 
id="default-value">16KB</td><td id="allowable-values"></td><td 
id="description">Set the internal buffer size for buffered data 
streams</td></tr><tr><td id="name"><strong>Use UTF-8 Encoding</strong></td><td 
id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Tells the client to use UTF-8 encoding when processing files 
and filenames. If se
 t to true, the server must also support UTF-8 
encoding.</td></tr></table><h3>Dynamic Properties: </h3><p>Dynamic Properties 
allow the user to specify both the name and value of a property.<table 
id="dynamic-properties"><tr><th>Name</th><th>Value</th><th>Description</th></tr><tr><td
 id="name">pre.cmd._____</td><td id="value">Not used</td><td>The command 
specified in the key will be executed before doing a put.  You may add these 
optional properties  to send any commands to the FTP server before the file is 
actually transferred (before the put command). This option is only available 
for the PutFTP processor, as only FTP has this functionality. This is 
essentially the same as sending quote commands to an FTP server from the 
command line.  While this is the same as sending a quote command, it is very 
important that you leave off the .</td></tr><tr><td 
id="name">post.cmd._____</td><td id="value">Not used</td><td>The command 
specified in the key will be executed after doing a put.  You ma
 y add these optional properties  to send any commands to the FTP server before 
the file is actually transferred (before the put command). This option is only 
available for the PutFTP processor, as only FTP has this functionality. This is 
essentially the same as sending quote commands to an FTP server from the 
command line.  While this is the same as sending a quote command, it is very 
important that you leave off the .</td></tr></table></p><h3>Relationships: 
</h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>FlowFiles
 that are successfully sent will be routed to 
success</td></tr><tr><td>reject</td><td>FlowFiles that were rejected by the 
destination system</td></tr><tr><td>failure</td><td>FlowFiles that failed to 
send to the remote system; failure is usually looped back to this 
processor</td></tr></table><h3>Reads Attributes: </h3>None specified.<h3>Writes 
Attributes: </h3>None specified.<h3>State management: </h3>This component does 
not 
 store state.<h3>Restricted: </h3>This component is not restricted.<h3>Input 
requirement: </h3>This component requires an incoming relationship.<h3>System 
Resource Considerations:</h3>None specified.<h3>See Also:</h3><p><a 
href="../org.apache.nifi.processors.standard.GetFTP/index.html">GetFTP</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutFile/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutFile/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutFile/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutFile/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>PutFile</title><link rel="stylesheet" 
href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">PutFile</h1><h2>Description: </h2><p>Writes the contents of a FlowFile 
to the local file system</p><h3>Tags: </h3><p>put, local, copy, archive, files, 
filesystem</p><h3>Properties: </h3><p>In the list below, the names of required 
properties appear in <strong>bold</strong>. Any other properties (not in bold) 
are considered optional. The table also indicates any default values, and 
whether a property supports the <a 
href="../../../../../html/expression-language-guide.html">NiFi Expression 
Language</a>.</p><table id="properties"><tr><th>Name</th><th>Default 
Value</th><th>Allowable Values</th><th>Descriptio
 n</th></tr><tr><td id="name"><strong>Directory</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
directory to which files should be written. You may use expression language 
such as /aa/bb/${path}<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Conflict Resolution 
Strategy</strong></td><td id="default-value">fail</td><td 
id="allowable-values"><ul><li>replace</li><li>ignore</li><li>fail</li></ul></td><td
 id="description">Indicates what should happen when a file with the same name 
already exists in the output directory</td></tr><tr><td 
id="name"><strong>Create Missing Directories</strong></td><td 
id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">If true, then missing destination directories will be created. 
If false, flowfiles are penalized and sent to failure.</td></tr><tr><td 
id="name">Maximum File Count</td><td id="default-value"
 ></td><td id="allowable-values"></td><td id="description">Specifies the 
 >maximum number of files that can exist in the output 
 >directory</td></tr><tr><td id="name">Last Modified Time</td><td 
 >id="default-value"></td><td id="allowable-values"></td><td 
 >id="description">Sets the lastModifiedTime on the output file to the value of 
 >this attribute.  Format must be yyyy-MM-dd'T'HH:mm:ssZ.  You may also use 
 >expression language such as ${file.lastModifiedTime}.<br/><strong>Supports 
 >Expression Language: true</strong></td></tr><tr><td 
 >id="name">Permissions</td><td id="default-value"></td><td 
 >id="allowable-values"></td><td id="description">Sets the permissions on the 
 >output file to the value of this attribute.  Format must be either UNIX 
 >rwxrwxrwx with a - in place of denied permissions (e.g. rw-r--r--) or an 
 >octal number (e.g. 644).  You may also use expression language such as 
 >${file.permissions}.<br/><strong>Supports Expression Language: 
 >true</strong></td></tr><tr><td id="name">Owner</td><td id
 ="default-value"></td><td id="allowable-values"></td><td id="description">Sets 
the owner on the output file to the value of this attribute.  You may also use 
expression language such as ${file.owner}.<br/><strong>Supports Expression 
Language: true</strong></td></tr><tr><td id="name">Group</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Sets the group on the output file to the value of this 
attribute.  You may also use expression language such as 
${file.group}.<br/><strong>Supports Expression Language: 
true</strong></td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>Files
 that have been successfully written to the output directory are transferred to 
this relationship</td></tr><tr><td>failure</td><td>Files that could not be 
written to the output directory for some reason are transferred to this 
relationship</td></tr></table><h3>Reads Attributes: </h3><table id="reads-a
 
ttributes"><tr><th>Name</th><th>Description</th></tr><tr><td>filename</td><td>The
 filename to use when writing the FlowFile to disk.</td></tr></table><h3>Writes 
Attributes: </h3>None specified.<h3>State management: </h3>This component does 
not store state.<h3>Restricted: </h3><table id="restrictions"><tr><th>Required 
Permission</th><th>Explanation</th></tr><tr><td>write 
filesystem</td><td>Provides operator the ability to write to any file that NiFi 
has access to.</td></tr></table><h3>Input requirement: </h3>This component 
requires an incoming relationship.<h3>System Resource Considerations:</h3>None 
specified.<h3>See Also:</h3><p><a 
href="../org.apache.nifi.processors.standard.FetchFile/index.html">FetchFile</a>,
 <a 
href="../org.apache.nifi.processors.standard.GetFile/index.html">GetFile</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutJMS/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutJMS/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutJMS/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutJMS/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>PutJMS</title><link rel="stylesheet" 
href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">PutJMS</h1><h2>Deprecation notice: </h2><p>This processor is deprecated 
and may be removed in future releases.</p><p>Please consider using one the 
following alternatives: <a 
href="../../../nifi-jms-processors-nar/1.6.0/org.apache.nifi.jms.processors.PublishJMS/index.html">PublishJMS</a></p><h2>Description:
 </h2><p>Creates a JMS Message from the contents of a FlowFile and sends the 
message to a ActiveMQ JMS Server.</p><h3>Tags: </h3><p>jms, send, 
put</p><h3>Properties: </h3><p>In the list below, the names of required 
properties appear in <strong>bold</strong>. Any other properties (not in bold) 
are consid
 ered optional. The table also indicates any default values, whether a property 
supports the <a href="../../../../../html/expression-language-guide.html">NiFi 
Expression Language</a>, 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 <strong>nifi.properties</strong> file has 
an entry for the property <strong>nifi.sensitive.props.key</strong>.</p><table 
id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><th>Description</th></tr><tr><td id="name"><strong>JMS 
Provider</strong></td><td id="default-value">ActiveMQ</td><td 
id="allowable-values"><ul><li>ActiveMQ</li></ul></td><td id="description">The 
Provider used for the JMS Server</td></tr><tr><td 
id="name"><strong>URL</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The URL of the JMS 
Server</td></tr><tr><td id="name"><strong>Destination Name</strong></td><td i
 d="default-value"></td><td id="allowable-values"></td><td id="description">The 
name of the JMS Topic or queue to use</td></tr><tr><td 
id="name"><strong>Destination Type</strong></td><td 
id="default-value">Queue</td><td 
id="allowable-values"><ul><li>Queue</li><li>Topic</li></ul></td><td 
id="description">The type of the JMS Destination to use</td></tr><tr><td 
id="name"><strong>Communications Timeout</strong></td><td id="default-value">30 
sec</td><td id="allowable-values"></td><td id="description">The amount of time 
to wait when attempting to receive a message before giving up and assuming 
failure</td></tr><tr><td id="name"><strong>Message Batch Size</strong></td><td 
id="default-value">10</td><td id="allowable-values"></td><td 
id="description">The number of messages to pull/push in a single iteration of 
the processor</td></tr><tr><td id="name">Username</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Username used for authentication and authorization<
 /td></tr><tr><td id="name">Password</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Password used for 
authentication and authorization<br/><strong>Sensitive Property: 
true</strong></td></tr><tr><td id="name">SSL Context Service</td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: </strong><br/>SSLContextService<br/><strong>Implementations: </strong><a 
href="../../../nifi-ssl-context-service-nar/1.6.0/org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a><br/><a
 
href="../../../nifi-ssl-context-service-nar/1.6.0/org.apache.nifi.ssl.StandardRestrictedSSLContextService/index.html">StandardRestrictedSSLContextService</a></td><td
 id="description">The Controller Service to use in order to obtain an SSL 
Context.</td></tr><tr><td id="name"><strong>Message Type</strong></td><td 
id="default-value">byte</td><td 
id="allowable-values"><ul><li>byte</li><li>stream</li><li>text</li><li>map</li><
 li>empty</li></ul></td><td id="description">The Type of JMS Message to 
Construct</td></tr><tr><td id="name">Message Priority</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
Priority of the Message<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Reply-To Queue</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
name of the queue to which a reply to should be added<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name"><strong>Max 
Buffer Size</strong></td><td id="default-value">1 MB</td><td 
id="allowable-values"></td><td id="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.</td></tr><tr><td id="name">Message Time to 
Live</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The amount of time that the message 
 should live on the destination before being removed; if not specified, the 
message will never expire.</td></tr><tr><td id="name"><strong>Copy Attributes 
to JMS Properties</strong></td><td id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="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.</td></tr><tr><td id="name">Client ID Prefix</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="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</td></tr></table><h3>Relationships: </h3><table id="relat
 
ionships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>All 
FlowFiles that are sent to the JMS destination are routed to this 
relationship</td></tr><tr><td>failure</td><td>All FlowFiles that cannot be 
routed to the JMS destination are routed to this 
relationship</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>Writes Attributes: </h3>None specified.<h3>State management: 
</h3>This component does not store state.<h3>Restricted: </h3>This component is 
not restricted.<h3>Input requirement: </h3>This component requires an incoming 
relationship.<h3>System Resource Considerations:</h3>None specified.<h3>See 
Also:</h3><p><a 
href="../org.apache.nifi.processors.standard.GetJMSQueue/index.html">GetJMSQueue</a>,
 <a 
href="../org.apache.nifi.processors.standard.GetJMSTopic/index.html">GetJMSTopic</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutSFTP/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutSFTP/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutSFTP/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutSFTP/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>PutSFTP</title><link rel="stylesheet" 
href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">PutSFTP</h1><h2>Description: </h2><p>Sends FlowFiles to an SFTP 
Server</p><h3>Tags: </h3><p>remote, copy, egress, put, sftp, archive, 
files</p><h3>Properties: </h3><p>In the list below, the names of required 
properties appear in <strong>bold</strong>. Any other properties (not in bold) 
are considered optional. The table also indicates any default values, whether a 
property supports the <a 
href="../../../../../html/expression-language-guide.html">NiFi Expression 
Language</a>, 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 <strong>nifi.properties</strong> file has an entry 
for the property <strong>nifi.sensitive.props.key</strong>.</p><table 
id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><th>Description</th></tr><tr><td 
id="name"><strong>Hostname</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The fully qualified hostname or 
IP address of the remote system<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Port</strong></td><td 
id="default-value">22</td><td id="allowable-values"></td><td 
id="description">The port that the remote system is listening on for file 
transfers<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Username</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Username<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Password<
 /td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">Password for the user account<br/><strong>Sensitive Property: 
true</strong><br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Private Key Path</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
fully qualified path to the Private Key file<br/><strong>Supports Expression 
Language: true</strong></td></tr><tr><td id="name">Private Key 
Passphrase</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">Password for the private key<br/><strong>Sensitive Property: 
true</strong><br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Remote Path</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
path on the remote system from which to pull or push files<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name"><strong>Create
  Directory</strong></td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Specifies whether or not the remote directory should be 
created if it does not exist.</td></tr><tr><td id="name">Disable Directory 
Listing</td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">If set to 'true', directory listing is not performed prior to 
create missing directories. By default, this processor executes a directory 
listing command to see target directory existence before creating missing 
directories. However, there are situations that you might need to disable the 
directory listing such as followings. Directory listing might fail with some 
permission setups (e.g. chmod 100) on a directory. Also, if any other SFTP 
client created the directory after this processor performed a listing and 
before a directory creation request by this processor is finished, then 
 an error is returned because the directory already exists.</td></tr><tr><td 
id="name"><strong>Batch Size</strong></td><td id="default-value">500</td><td 
id="allowable-values"></td><td id="description">The maximum number of FlowFiles 
to send in a single connection</td></tr><tr><td id="name"><strong>Connection 
Timeout</strong></td><td id="default-value">30 sec</td><td 
id="allowable-values"></td><td id="description">Amount of time to wait before 
timing out while creating a connection</td></tr><tr><td id="name"><strong>Data 
Timeout</strong></td><td id="default-value">30 sec</td><td 
id="allowable-values"></td><td id="description">When transferring a file 
between the local and remote system, this value specifies how long is allowed 
to elapse without any data being transferred between systems</td></tr><tr><td 
id="name"><strong>Conflict Resolution</strong></td><td 
id="default-value">NONE</td><td 
id="allowable-values"><ul><li>REPLACE</li><li>IGNORE</li><li>RENAME</li><li>REJECT</li><li>FAIL<
 /li><li>NONE</li></ul></td><td id="description">Determines how to handle the 
problem of filename collisions</td></tr><tr><td id="name">Reject Zero-Byte 
Files</td><td id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Determines whether or not Zero-byte files should be rejected 
without attempting to transfer</td></tr><tr><td id="name">Dot Rename</td><td 
id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">If true, then the filename of the sent file is prepended with 
a "." and then renamed back to the original once the file is completely sent. 
Otherwise, there is no rename. This property is ignored if the Temporary 
Filename property is set.</td></tr><tr><td id="name">Temporary Filename</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">If 
set, the filename of the sent file will be equal to the value specified during 
the transf
 er and after successful completion will be renamed to the original filename. 
If this value is set, the Dot Rename property is ignored.<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name">Host Key 
File</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">If supplied, the given file will be used as the Host Key; 
otherwise, no use host key file will be used</td></tr><tr><td id="name">Last 
Modified Time</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The lastModifiedTime to assign 
to the file after transferring it. If not set, the lastModifiedTime will not be 
changed. Format must be yyyy-MM-dd'T'HH:mm:ssZ. You may also use expression 
language such as ${file.lastModifiedTime}. If the value is invalid, the 
processor will not be invalid but will fail to change lastModifiedTime of the 
file.<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name">Permissions</td><td id
 ="default-value"></td><td id="allowable-values"></td><td id="description">The 
permissions to assign to the file after transferring it. Format must be either 
UNIX rwxrwxrwx with a - in place of denied permissions (e.g. rw-r--r--) or an 
octal number (e.g. 644). If not set, the permissions will not be changed. You 
may also use expression language such as ${file.permissions}. If the value is 
invalid, the processor will not be invalid but will fail to change permissions 
of the file.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Remote Owner</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Integer value representing the User ID to set on the file 
after transferring it. If not set, the owner will not be set. You may also use 
expression language such as ${file.owner}. If the value is invalid, the 
processor will not be invalid but will fail to change the owner of the 
file.<br/><strong>Supports Expression Language: true</
 strong></td></tr><tr><td id="name">Remote Group</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Integer value representing the Group ID to set on the file 
after transferring it. If not set, the group will not be set. You may also use 
expression language such as ${file.group}. If the value is invalid, the 
processor will not be invalid but will fail to change the group of the 
file.<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name"><strong>Strict Host Key Checking</strong></td><td 
id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Indicates whether or not strict enforcement of hosts keys 
should be applied</td></tr><tr><td id="name"><strong>Send Keep Alive On 
Timeout</strong></td><td id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Indicates whether or not to send a single Keep Alive mess
 age when SSH socket times out</td></tr><tr><td id="name"><strong>Use 
Compression</strong></td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Indicates whether or not ZLIB compression should be used when 
transferring files</td></tr></table><h3>Dynamic Properties: </h3><p>Dynamic 
Properties allow the user to specify both the name and value of a 
property.<table 
id="dynamic-properties"><tr><th>Name</th><th>Value</th><th>Description</th></tr><tr><td
 id="name">Disable Directory Listing</td><td id="value">true or 
false</td><td>Disables directory listings before operations which might fail, 
such as configurations which create directory 
structures.</td></tr></table></p><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>FlowFiles
 that are successfully sent will be routed to 
success</td></tr><tr><td>reject</td><td>FlowFiles that were rejected by the 
destina
 tion system</td></tr><tr><td>failure</td><td>FlowFiles that failed to send to 
the remote system; failure is usually looped back to this 
processor</td></tr></table><h3>Reads Attributes: </h3>None specified.<h3>Writes 
Attributes: </h3>None specified.<h3>State management: </h3>This component does 
not store state.<h3>Restricted: </h3>This component is not restricted.<h3>Input 
requirement: </h3>This component requires an incoming relationship.<h3>System 
Resource Considerations:</h3>None specified.<h3>See Also:</h3><p><a 
href="../org.apache.nifi.processors.standard.GetSFTP/index.html">GetSFTP</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutSQL/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutSQL/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutSQL/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutSQL/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>PutSQL</title><link rel="stylesheet" 
href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">PutSQL</h1><h2>Description: </h2><p>Executes a SQL UPDATE or INSERT 
command. The content of an incoming FlowFile is expected to be the SQL command 
to execute. The SQL command may use the ? to escape parameters. In this case, 
the parameters to use must exist as FlowFile attributes with the naming 
convention sql.args.N.type and sql.args.N.value, where N is a positive integer. 
The sql.args.N.type is expected to be a number indicating the JDBC Type. The 
content of the FlowFile is expected to be in UTF-8 format.</p><h3>Tags: 
</h3><p>sql, put, rdbms, database, update, insert, 
relational</p><h3>Properties: </h3
 ><p>In the list below, the names of required properties appear in 
 ><strong>bold</strong>. Any other properties (not in bold) are considered 
 >optional. The table also indicates any default values, and whether a property 
 >supports the <a 
 >href="../../../../../html/expression-language-guide.html">NiFi Expression 
 >Language</a>.</p><table id="properties"><tr><th>Name</th><th>Default 
 >Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td 
 >id="name"><strong>JDBC Connection Pool</strong></td><td 
 >id="default-value"></td><td id="allowable-values"><strong>Controller Service 
 >API: </strong><br/>DBCPService<br/><strong>Implementations: </strong><a 
 >href="../../../nifi-dbcp-service-nar/1.6.0/org.apache.nifi.dbcp.DBCPConnectionPool/index.html">DBCPConnectionPool</a><br/><a
 > 
 >href="../../../nifi-hive-nar/1.6.0/org.apache.nifi.dbcp.hive.HiveConnectionPool/index.html">HiveConnectionPool</a></td><td
 > id="description">Specifies the JDBC Connection Pool to use in order to 
 >convert the JSON message to a
  SQL statement. The Connection Pool is necessary in order to determine the 
appropriate database column types.</td></tr><tr><td id="name">SQL 
Statement</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The SQL statement to execute. The statement can be empty, a 
constant value, or built from attributes using Expression Language. If this 
property is specified, it will be used regardless of the content of incoming 
flowfiles. If this property is empty, the content of the incoming flow file is 
expected to contain a valid SQL statement, to be issued by the processor to the 
database.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Support Fragmented 
Transactions</td><td id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">If true, when a FlowFile is consumed by this Processor, the 
Processor will first check the fragment.identifier and fragment.count 
attributes 
 of that FlowFile. If the fragment.count value is greater than 1, the Processor 
will not process any FlowFile with that fragment.identifier until all are 
available; at that point, it will process all FlowFiles with that 
fragment.identifier as a single transaction, in the order specified by the 
FlowFiles' fragment.index attributes. This Provides atomicity of those SQL 
statements. If this value is false, these attributes will be ignored and the 
updates will occur independent of one another.</td></tr><tr><td 
id="name">Transaction Timeout</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">If the &lt;Support Fragmented 
Transactions&gt; property is set to true, specifies how long to wait for all 
FlowFiles for a particular fragment.identifier attribute to arrive before just 
transferring all of the FlowFiles with that identifier to the 'failure' 
relationship</td></tr><tr><td id="name"><strong>Batch Size</strong></td><td 
id="default-value">100</td><td id="allo
 wable-values"></td><td id="description">The preferred number of FlowFiles to 
put to the database in a single transaction</td></tr><tr><td id="name">Obtain 
Generated Keys</td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">If true, any key that is automatically generated by the 
database will be added to the FlowFile that generated it using the 
sql.generate.key attribute. This may result in slightly slower performance and 
is not supported by all databases.</td></tr><tr><td id="name"><strong>Rollback 
On Failure</strong></td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Specify how to handle error. By default (false), if an error 
occurs while processing a FlowFile, the FlowFile will be routed to 'failure' or 
'retry' relationship based on error type, and processor can continue with next 
FlowFile. Instead, you may want to rollback currently pr
 ocessed FlowFiles and stop further processing immediately. In that case, you 
can do so by enabling this 'Rollback On Failure' property.  If enabled, failed 
FlowFiles will stay in the input relationship without penalizing it and being 
processed repeatedly until it gets processed successfully or removed by other 
means. It is important to set adequate 'Yield Duration' to avoid retrying too 
frequently.</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>retry</td><td>A
 FlowFile is routed to this relationship if the database cannot be updated but 
attempting the operation again may succeed</td></tr><tr><td>success</td><td>A 
FlowFile is routed to this relationship after the database is successfully 
updated</td></tr><tr><td>failure</td><td>A FlowFile is routed to this 
relationship if the database cannot be updated and retrying the operation will 
also fail, such as an invalid query or an integrity constraint 
violation</td></tr>
 </table><h3>Reads Attributes: </h3><table 
id="reads-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>fragment.identifier</td><td>If
 the &lt;Support Fragment Transactions&gt; property is true, this attribute is 
used to determine whether or not two FlowFiles belong to the same 
transaction.</td></tr><tr><td>fragment.count</td><td>If the &lt;Support 
Fragment Transactions&gt; property is true, this attribute is used to determine 
how many FlowFiles are needed to complete the 
transaction.</td></tr><tr><td>fragment.index</td><td>If the &lt;Support 
Fragment Transactions&gt; property is true, this attribute is used to determine 
the order that the FlowFiles in a transaction should be 
evaluated.</td></tr><tr><td>sql.args.N.type</td><td>Incoming FlowFiles are 
expected to be parametrized SQL statements. The type of each Parameter is 
specified as an integer that represents the JDBC Type of the 
parameter.</td></tr><tr><td>sql.args.N.value</td><td>Incoming FlowFiles are 
expected to be p
 arametrized SQL statements. The value of the Parameters are specified as 
sql.args.1.value, sql.args.2.value, sql.args.3.value, and so on. The type of 
the sql.args.1.value Parameter is specified by the sql.args.1.type 
attribute.</td></tr><tr><td>sql.args.N.format</td><td>This attribute is always 
optional, but default options may not always work for your data. Incoming 
FlowFiles are expected to be parametrized SQL statements. In some cases a 
format option needs to be specified, currently this is only applicable for 
binary data types, dates, times and timestamps. Binary Data Types (defaults to 
'ascii') - ascii: each string character in your attribute value represents a 
single byte. This is the format provided by Avro Processors. base64: the string 
is a Base64 encoded string that can be decoded to bytes. hex: the string is hex 
encoded with all letters in upper case and no '0x' at the beginning. 
Dates/Times/Timestamps - Date, Time and Timestamp formats all support both 
custom formats or 
 named format ('yyyy-MM-dd','ISO_OFFSET_DATE_TIME') as specified according to 
java.time.format.DateTimeFormatter. If not specified, a long value input is 
expected to be an unix epoch (milli seconds from 1970/1/1), or a string value 
in 'yyyy-MM-dd' format for Date, 'HH:mm:ss.SSS' for Time (some database engines 
e.g. Derby or MySQL do not support milliseconds and will truncate 
milliseconds), 'yyyy-MM-dd HH:mm:ss.SSS' for Timestamp is 
used.</td></tr></table><h3>Writes Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>sql.generated.key</td><td>If
 the database generated a key for an INSERT statement and the Obtain Generated 
Keys property is set to true, this attribute will be added to indicate the 
generated key, if possible. This feature is not supported by all database 
vendors.</td></tr></table><h3>State management: </h3>This component does not 
store state.<h3>Restricted: </h3>This component is not restricted.<h3>Input 
requirement: </h3>This
  component requires an incoming relationship.<h3>System Resource 
Considerations:</h3>None specified.<h3>See Also:</h3><p><a 
href="../org.apache.nifi.processors.standard.ConvertJSONToSQL/index.html">ConvertJSONToSQL</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutSyslog/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutSyslog/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutSyslog/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutSyslog/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>PutSyslog</title><link rel="stylesheet" 
href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">PutSyslog</h1><h2>Description: </h2><p>Sends Syslog messages to a given 
host and port over TCP or UDP. Messages are constructed from the "Message ___" 
properties of the processor which can use expression language to generate 
messages from incoming FlowFiles. The properties are used to construct messages 
of the form: (&lt;PRIORITY&gt;)(VERSION )(TIMESTAMP) (HOSTNAME) (BODY) where 
version is optional.  The constructed messages are checked against regular 
expressions for RFC5424 and RFC3164 formatted messages. The timestamp can be an 
RFC5424 timestamp with a format of "yyyy-MM-dd'T'HH:mm:ss.SZ" or "yyyy-
 MM-dd'T'HH:mm:ss.S+hh:mm", or it can be an RFC3164 timestamp with a format of 
"MMM d HH:mm:ss". If a message is constructed that does not form a valid Syslog 
message according to the above description, then it is routed to the invalid 
relationship. Valid messages are sent to the Syslog server and successes are 
routed to the success relationship, failures routed to the failure 
relationship.</p><h3>Tags: </h3><p>syslog, put, udp, tcp, 
logs</p><h3>Properties: </h3><p>In the list below, the names of required 
properties appear in <strong>bold</strong>. Any other properties (not in bold) 
are considered optional. The table also indicates any default values, and 
whether a property supports the <a 
href="../../../../../html/expression-language-guide.html">NiFi Expression 
Language</a>.</p><table id="properties"><tr><th>Name</th><th>Default 
Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td 
id="name"><strong>Hostname</strong></td><td 
id="default-value">localhost</td><td id="all
 owable-values"></td><td id="description">The ip address or hostname of the 
Syslog server. Note that Expression language is not evaluated per 
FlowFile.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Protocol</strong></td><td 
id="default-value">UDP</td><td 
id="allowable-values"><ul><li>TCP</li><li>UDP</li></ul></td><td 
id="description">The protocol for Syslog communication.</td></tr><tr><td 
id="name"><strong>Port</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The port for Syslog 
communication. Note that Expression language is not evaluated per 
FlowFile.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Max Size of Socket Send 
Buffer</strong></td><td id="default-value">1 MB</td><td 
id="allowable-values"></td><td id="description">The maximum size of the socket 
send buffer that should be used. This is a suggestion to the Operating System 
to indicate how big t
 he socket buffer should be. If this value is set too low, the buffer may fill 
up before the data can be read, and incoming data will be dropped. Note that 
Expression language is not evaluated per FlowFile.<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name">SSL Context 
Service</td><td id="default-value"></td><td 
id="allowable-values"><strong>Controller Service API: 
</strong><br/>SSLContextService<br/><strong>Implementations: </strong><a 
href="../../../nifi-ssl-context-service-nar/1.6.0/org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a><br/><a
 
href="../../../nifi-ssl-context-service-nar/1.6.0/org.apache.nifi.ssl.StandardRestrictedSSLContextService/index.html">StandardRestrictedSSLContextService</a></td><td
 id="description">The Controller Service to use in order to obtain an SSL 
Context. If this property is set, syslog messages will be sent over a secure 
connection.</td></tr><tr><td id="name"><strong>Idle Connection E
 xpiration</strong></td><td id="default-value">5 seconds</td><td 
id="allowable-values"></td><td id="description">The amount of time a connection 
should be held open without being used before closing the connection. Note that 
Expression language is not evaluated per FlowFile.<br/><strong>Supports 
Expression Language: true</strong></td></tr><tr><td id="name">Timeout</td><td 
id="default-value">10 seconds</td><td id="allowable-values"></td><td 
id="description">The timeout for connecting to and communicating with the 
syslog server. Does not apply to UDP. Note that Expression language is not 
evaluated per FlowFile.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Batch Size</strong></td><td 
id="default-value">25</td><td id="allowable-values"></td><td 
id="description">The number of incoming FlowFiles to process in a single 
execution of this processor. Note that Expression language is not evaluated per 
FlowFile.<br/><strong>Supports Expression Langua
 ge: true</strong></td></tr><tr><td id="name"><strong>Character 
Set</strong></td><td id="default-value">UTF-8</td><td 
id="allowable-values"></td><td id="description">Specifies the character set of 
the Syslog messages. Note that Expression language is not evaluated per 
FlowFile.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Message 
Priority</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The priority for the Syslog 
messages, excluding &lt; &gt;.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Message Version</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
version for the Syslog messages.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Message 
Timestamp</strong></td><td id="default-value">${now():format('MMM d 
HH:mm:ss')}</td><td id="allowable-values"></td><td id="description">The 
 timestamp for the Syslog messages. The timestamp can be an RFC5424 timestamp 
with a format of "yyyy-MM-dd'T'HH:mm:ss.SZ" or "yyyy-MM-dd'T'HH:mm:ss.S+hh:mm", 
" or it can be an RFC3164 timestamp with a format of "MMM d 
HH:mm:ss".<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Message 
Hostname</strong></td><td id="default-value">${hostname(true)}</td><td 
id="allowable-values"></td><td id="description">The hostname for the Syslog 
messages.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Message Body</strong></td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
body for the Syslog messages.<br/><strong>Supports Expression Language: 
true</strong></td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>FlowFiles
 that are sent successfully to Syslog are sent out this 
relationship.</td></tr><tr><
 td>failure</td><td>FlowFiles that failed to send to Syslog are sent out this 
relationship.</td></tr><tr><td>invalid</td><td>FlowFiles that do not form a 
valid Syslog message are sent out this relationship.</td></tr></table><h3>Reads 
Attributes: </h3>None specified.<h3>Writes Attributes: </h3>None 
specified.<h3>State management: </h3>This component does not store 
state.<h3>Restricted: </h3>This component is not restricted.<h3>Input 
requirement: </h3>This component requires an incoming relationship.<h3>System 
Resource Considerations:</h3>None specified.<h3>See Also:</h3><p><a 
href="../org.apache.nifi.processors.standard.ListenSyslog/index.html">ListenSyslog</a>,
 <a 
href="../org.apache.nifi.processors.standard.ParseSyslog/index.html">ParseSyslog</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutTCP/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutTCP/index.html?rev=1828578&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutTCP/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.PutTCP/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>PutTCP</title><link rel="stylesheet" 
href="../../../../../css/component-usage.css" 
type="text/css"></link></head><script type="text/javascript">window.onload = 
function(){if(self==top) { document.getElementById('nameHeader').style.display 
= "inherit"; } }</script><body><h1 id="nameHeader" style="display: 
none;">PutTCP</h1><h2>Description: </h2><p>The PutTCP processor receives a 
FlowFile and transmits the FlowFile content over a TCP connection to the 
configured TCP server. By default, the FlowFiles are transmitted over the same 
TCP connection (or pool of TCP connections if multiple input threads are 
configured). To assist the TCP server with determining message boundaries, an 
optional "Outgoing Message Delimiter" string can be configured which is 
appended to the end of each FlowFiles content when it is transmitted over the 
TCP connection. An optional "Connection Per FlowFile" parameter can be 
specified to change
  the behaviour so that each FlowFiles content is transmitted over a single TCP 
connection which is opened when the FlowFile is received and closed after the 
FlowFile has been sent. This option should only be used for low message volume 
scenarios, otherwise the platform may run out of TCP sockets.</p><h3>Tags: 
</h3><p>remote, egress, put, tcp</p><h3>Properties: </h3><p>In the list below, 
the names of required properties appear in <strong>bold</strong>. Any other 
properties (not in bold) are considered optional. The table also indicates any 
default values, and whether a property supports the <a 
href="../../../../../html/expression-language-guide.html">NiFi Expression 
Language</a>.</p><table id="properties"><tr><th>Name</th><th>Default 
Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td 
id="name"><strong>Hostname</strong></td><td 
id="default-value">localhost</td><td id="allowable-values"></td><td 
id="description">The ip address or hostname of the destination.<br/><stron
 g>Supports Expression Language: true</strong></td></tr><tr><td 
id="name"><strong>Port</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The port on the 
destination.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Max Size of Socket Send 
Buffer</strong></td><td id="default-value">1 MB</td><td 
id="allowable-values"></td><td id="description">The maximum size of the socket 
send buffer that should be used. This is a suggestion to the Operating System 
to indicate how big the socket buffer should be. If this value is set too low, 
the buffer may fill up before the data can be read, and incoming data will be 
dropped.</td></tr><tr><td id="name"><strong>Idle Connection 
Expiration</strong></td><td id="default-value">5 seconds</td><td 
id="allowable-values"></td><td id="description">The amount of time a connection 
should be held open without being used before closing the 
connection.</td></tr><tr><td id="name"><s
 trong>Connection Per FlowFile</strong></td><td 
id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Specifies whether to send each FlowFile's content on an 
individual connection.</td></tr><tr><td id="name">Outgoing Message 
Delimiter</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">Specifies the delimiter to use when sending messages out over 
the same TCP stream. The delimiter is appended to each FlowFile message that is 
transmitted over the stream so that the receiver can determine when one message 
ends and the next message begins. Users should ensure that the FlowFile content 
does not contain the delimiter character to avoid errors. In order to use a new 
line character you can enter '\n'. For a tab character use '\t'. Finally for a 
carriage return use '\r'.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Timeout</td><td id="default-value">10 
seconds<
 /td><td id="allowable-values"></td><td id="description">The timeout for 
connecting to and communicating with the destination. Does not apply to 
UDP</td></tr><tr><td id="name">SSL Context Service</td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: </strong><br/>SSLContextService<br/><strong>Implementations: </strong><a 
href="../../../nifi-ssl-context-service-nar/1.6.0/org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</a><br/><a
 
href="../../../nifi-ssl-context-service-nar/1.6.0/org.apache.nifi.ssl.StandardRestrictedSSLContextService/index.html">StandardRestrictedSSLContextService</a></td><td
 id="description">The Controller Service to use in order to obtain an SSL 
Context. If this property is set, messages will be sent over a secure 
connection.</td></tr><tr><td id="name"><strong>Character Set</strong></td><td 
id="default-value">UTF-8</td><td id="allowable-values"></td><td 
id="description">Specifies the character se
 t of the data being sent.</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>FlowFiles
 that are sent successfully to the destination are sent out this 
relationship.</td></tr><tr><td>failure</td><td>FlowFiles that failed to send to 
the destination are sent out this relationship.</td></tr></table><h3>Reads 
Attributes: </h3>None specified.<h3>Writes Attributes: </h3>None 
specified.<h3>State management: </h3>This component does not store 
state.<h3>Restricted: </h3>This component is not restricted.<h3>Input 
requirement: </h3>This component requires an incoming relationship.<h3>System 
Resource Considerations:</h3>None specified.<h3>See Also:</h3><p><a 
href="../org.apache.nifi.processors.standard.ListenTCP/index.html">ListenTCP</a></p></body></html>
\ No newline at end of file


Reply via email to