Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.GenerateFlowFile/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.GenerateFlowFile/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.GenerateFlowFile/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.GenerateFlowFile/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>GenerateFlowFile</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;">GenerateFlowFile</h1><h2>Description: </h2><p>This processor creates 
FlowFiles with random data or custom content. GenerateFlowFile is usefulfor 
load testing, configuration, and simulation.</p><h3>Tags: </h3><p>test, random, 
generate</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="propertie
 s"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><th>Description</th></tr><tr><td id="name"><strong>File 
Size</strong></td><td id="default-value">0B</td><td 
id="allowable-values"></td><td id="description">The size of the file that will 
be used</td></tr><tr><td id="name"><strong>Batch Size</strong></td><td 
id="default-value">1</td><td id="allowable-values"></td><td 
id="description">The number of FlowFiles to be transferred in each 
invocation</td></tr><tr><td id="name"><strong>Data Format</strong></td><td 
id="default-value">Text</td><td 
id="allowable-values"><ul><li>Binary</li><li>Text</li></ul></td><td 
id="description">Specifies whether the data should be Text or 
Binary</td></tr><tr><td id="name"><strong>Unique FlowFiles</strong></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, each FlowFile that is generated will be unique. If 
false, a random value will be generated and all FlowFil
 es will get the same content but this offers much higher 
throughput</td></tr><tr><td id="name">Custom Text</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">If 
Data Format is text and if Unique FlowFiles is false, then this custom text 
will be used as content of the generated FlowFiles and the File Size will be 
ignored. Finally, if Expression Language is used, evaluation will be performed 
only once per batch of generated FlowFiles<br/><strong>Supports Expression 
Language: 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 to 
use when writing the bytes of Custom Text to a flow 
file.</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"
 >Generated FlowFile attribute name</td><td id="value">Generated FlowFile 
 >attribute value</td><td>Specifies an attribute on generated FlowFiles defined 
 >by the Dynamic Property's key and value. If Expression Language is used, 
 >evaluation will be performed only once per batch of generated 
 >FlowFiles.<br/><strong>Supports Expression Language: 
 >true</strong></td></tr></table></p><h3>Relationships: </h3><table 
 >id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td></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 does not allow 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.GenerateTableFetch/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.GenerateTableFetch/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.GenerateTableFetch/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.GenerateTableFetch/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1,6 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>GenerateTableFetch</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;">GenerateTableFetch</h1><h2>Description: </h2><p>Generates SQL select 
queries that fetch "pages" of rows from a table. The partition size property, 
along with the table's row count, determine the size and number of pages and 
generated FlowFiles. In addition, incremental fetching can be achieved by 
setting Maximum-Value Columns, which causes the processor to track the columns' 
maximum values, thus only fetching rows whose columns' values exceed the 
observed maximums. This processor is intended to be run on the Primary Node 
only.
+
+This processor can accept incoming connections; the behavior of the processor 
is different whether incoming connections are provided:
+  - If no incoming connection(s) are specified, the processor will generate 
SQL queries on the specified processor schedule. Expression Language is 
supported for many fields, but no flow file attributes are available. However 
the properties will be evaluated using the Variable Registry.
+  - If incoming connection(s) are specified and no flow file is available to a 
processor task, no work will be performed.
+  - If incoming connection(s) are specified and a flow file is available to a 
processor task, the flow file's attributes may be used in Expression Language 
for such fields as Table Name and others. However, the Max-Value Columns and 
Columns to Return fields must be empty or refer to columns that are available 
in each specified table.</p><h3>Tags: </h3><p>sql, select, jdbc, query, 
database, fetch, generate</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>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.</td></tr><tr><td id="name"><strong>Database Type</strong></td><td 
id="default-value">Generic</td><td id="allowable-values"><ul><li>Generic <img 
src="../../../../../html/images/iconInfo.png" alt="Generates ANSI SQL" 
title="Generates ANSI SQL"></img></li><li>Oracle <img 
src="../../../../../html/images/iconInfo.png" alt="Generates Oracle compliant 
SQL" title="Generates Oracle compliant SQL"></img></li><li>Oracle 12+ <img 
src="../../../../../html/images/iconInfo.png" alt="Generates Oracle compliant 
SQL for version 12 or greater" title="Generates Oracle co
 mpliant SQL for version 12 or greater"></img></li><li>MS SQL 2012+ <img 
src="../../../../../html/images/iconInfo.png" alt="Generates MS SQL Compatible 
SQL, for version 2012 or greater" title="Generates MS SQL Compatible SQL, for 
version 2012 or greater"></img></li><li>MS SQL 2008 <img 
src="../../../../../html/images/iconInfo.png" alt="Generates MS SQL Compatible 
SQL for version 2008" title="Generates MS SQL Compatible SQL for version 
2008"></img></li></ul></td><td id="description">The type/flavor of database, 
used for generating database-specific code. In many cases the Generic type 
should suffice, but some databases (such as Oracle) require custom SQL clauses. 
</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 database table to be queried.<br/><strong>Supports Expression 
Language: true</strong></td></tr><tr><td id="name">Columns to Return</td><td 
id="default-value"></td><td id="
 allowable-values"></td><td id="description">A comma-separated list of column 
names to be used in the query. If your database requires special treatment of 
the names (quoting, e.g.), each name should include such treatment. If no 
column names are supplied, all columns in the specified table will be returned. 
NOTE: It is important to use consistent column names for a given table for 
incremental fetch to work properly.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Maximum-value Columns</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">A 
comma-separated list of column names. The processor will keep track of the 
maximum value for each column that has been returned since the processor 
started running. Using multiple columns implies an order to the column list, 
and each column's values are expected to increase more slowly than the previous 
columns' values. Thus, using multiple columns implies a hierarchical structure 
of
  columns, which is usually used for partitioning tables. This processor can be 
used to retrieve only those rows that have been added/updated since the last 
retrieval. Note that some JDBC types such as bit/boolean are not conducive to 
maintaining maximum value, so columns of these types should not be listed in 
this property, and will result in error(s) during processing. If no columns are 
provided, all rows from the table will be considered, which could have a 
performance impact. NOTE: It is important to use consistent max-value column 
names for a given table for incremental fetch to work 
properly.<br/><strong>Supports Expression Language: 
true</strong></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 select 
query , zero means there is no limit. Max time less than 1 second will be equal 
to zero.<br/><strong>Supports Expression Lang
 uage: true</strong></td></tr><tr><td id="name"><strong>Partition 
Size</strong></td><td id="default-value">10000</td><td 
id="allowable-values"></td><td id="description">The number of result rows to be 
fetched by each generated SQL statement. The total number of rows in the table 
divided by the partition size gives the number of SQL statements (i.e. 
FlowFiles) generated. A value of zero indicates that a single FlowFile is to be 
generated whose SQL statement will fetch all rows in the 
table.<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name">Additional WHERE clause</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">A custom clause to be added in 
the WHERE condition when generating SQL requests.<br/><strong>Supports 
Expression Language: true</strong></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">Initial Max 
Value</td><td id="value">Attribute Expression Language</td><td>Specifies an 
initial max value for max value columns. Properties should be added in the 
format 
`initial.maxvalue.{max_value_column}`.</td></tr></table></p><h3>Relationships: 
</h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>Successfully
 created FlowFile from SQL query result 
set.</td></tr><tr><td>failure</td><td>This relationship is only used when SQL 
query execution (using an incoming FlowFile) failed. The incoming FlowFile will 
be penalized and routed to this relationship. If no incoming connection(s) are 
specified, this relationship is unused.</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>generatetablefetch.sql.error</td><td>If
 the processor has incoming connections, and processin
 g an incoming flow file causes a SQL Exception, the flow file is routed to 
failure and this attribute is set to the exception 
message.</td></tr><tr><td>generatetablefetch.tableName</td><td>The name of the 
database table to be 
queried.</td></tr><tr><td>generatetablefetch.columnNames</td><td>The 
comma-separated list of column names used in the 
query.</td></tr><tr><td>generatetablefetch.whereClause</td><td>Where clause 
used in the query to get the expected 
rows.</td></tr><tr><td>generatetablefetch.maxColumnNames</td><td>The 
comma-separated list of column names used to keep track of data that has been 
returned since the processor started 
running.</td></tr><tr><td>generatetablefetch.limit</td><td>The number of result 
rows to be fetched by the SQL 
statement.</td></tr><tr><td>generatetablefetch.offset</td><td>Offset to be used 
to retrieve the corresponding partition.</td></tr></table><h3>State management: 
</h3><table 
id="stateful"><tr><th>Scope</th><th>Description</th></tr><tr><td>CLUSTER<
 /td><td>After performing a query on the specified table, the maximum values 
for the specified column(s) will be retained for use in future executions of 
the query. This allows the Processor to fetch only those records that have max 
values greater than the retained values. This can be used for incremental 
fetching, fetching of newly added rows, etc. To clear the maximum values, clear 
the state of the processor per the State Management 
documentation</td></tr></table><h3>Restricted: </h3>This component is not 
restricted.<h3>Input requirement: </h3>This component allows an incoming 
relationship.<h3>System Resource Considerations:</h3>None specified.<h3>See 
Also:</h3><p><a 
href="../org.apache.nifi.processors.standard.QueryDatabaseTable/index.html">QueryDatabaseTable</a>,
 <a 
href="../org.apache.nifi.processors.standard.ExecuteSQL/index.html">ExecuteSQL</a>,
 <a 
href="../org.apache.nifi.processors.standard.ListDatabaseTables/index.html">ListDatabaseTables</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.GetFTP/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.GetFTP/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.GetFTP/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.GetFTP/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>GetFTP</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;">GetFTP</h1><h2>Description: </h2><p>Fetches files from an FTP Server and 
creates FlowFiles from them</p><h3>Tags: </h3><p>FTP, get, retrieve, files, 
fetch, remote, ingest, source, input</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 encr
 ypted. 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">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">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">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">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">File Filter Regex</td><td id="default-value"></td><td 
id="allowable-values"></
 td><td id="description">Provides a Java Regular Expression for filtering 
Filenames; if a filter is supplied, only files whose names match that Regular 
Expression will be fetched</td></tr><tr><td id="name">Path Filter Regex</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">When Search Recursively is true, then only subdirectories 
whose path matches the given Regular Expression will be 
scanned</td></tr><tr><td id="name"><strong>Polling Interval</strong></td><td 
id="default-value">60 sec</td><td id="allowable-values"></td><td 
id="description">Determines how long to wait between fetching the listing for 
new files</td></tr><tr><td id="name"><strong>Search 
Recursively</strong></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, will pull files from arbitrarily nested 
subdirectories; otherwise, will not traverse subdirectories</td></tr><tr><td 
id="name"><strong>Ignore Dotted 
 Files</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, files whose names begin with a dot (".") will be 
ignored</td></tr><tr><td id="name"><strong>Delete Original</strong></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 the file is deleted from the remote 
system after it has been successfully transferred</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 da
 ta being transferred between systems</td></tr><tr><td id="name"><strong>Max 
Selects</strong></td><td id="default-value">100</td><td 
id="allowable-values"></td><td id="description">The maximum number of files to 
pull in a single connection</td></tr><tr><td id="name"><strong>Remote Poll 
Batch Size</strong></td><td id="default-value">5000</td><td 
id="allowable-values"></td><td id="description">The value specifies how many 
file paths to find in a given directory on the remote system when doing a file 
listing. This value in general should not need to be modified but when polling 
against a remote system with a tremendous number of files this value can be 
critical.  Setting this value too high can result very poor performance and 
setting it too low can cause the flow to be slower than 
normal.</td></tr><tr><td id="name"><strong>Use Natural 
Ordering</strong></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, w
 ill pull files in the order in which they are naturally listed; otherwise, the 
order in which the files will be pulled is not defined</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 hostname 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 set to true, the server must also support UTF-8 
 >encoding.</td></tr></table><h3>Relationships: </h3><table 
 >id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>All
 > FlowFiles that are received are routed to success</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>filename</td><td>The
 > filename is set to the name of the file on the remote server</td></tr><
 tr><td>path</td><td>The path is set to the path of the file's directory on the 
remote server. For example, if the &lt;Remote Path&gt; property is set to /tmp, 
files picked up from /tmp will have the path attribute set to /tmp. If the 
&lt;Search Recursively&gt; property is set to true and a file is picked up from 
/tmp/abc/1/2/3, then the path attribute will be set to 
/tmp/abc/1/2/3</td></tr><tr><td>file.lastModifiedTime</td><td>The date and time 
that the source file was last 
modified</td></tr><tr><td>file.lastAccessTime</td><td>The date and time that 
the file was last accessed. May not work on all file 
systems</td></tr><tr><td>file.owner</td><td>The numeric owner id of the source 
file</td></tr><tr><td>file.group</td><td>The numeric group id of the source 
file</td></tr><tr><td>file.permissions</td><td>The read/write/execute 
permissions of the source file</td></tr><tr><td>absolute.path</td><td>The 
full/absolute path from where a file was picked up. The current 'path' 
attribute is still
  populated, but may be a relative path</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 does not allow an 
incoming relationship.<h3>System Resource Considerations:</h3>None 
specified.<h3>See Also:</h3><p><a 
href="../org.apache.nifi.processors.standard.PutFTP/index.html">PutFTP</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.GetFile/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.GetFile/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.GetFile/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.GetFile/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>GetFile</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;">GetFile</h1><h2>Description: </h2><p>Creates FlowFiles from files in a 
directory.  NiFi will ignore files it doesn't have at least read permissions 
for.</p><h3>Tags: </h3><p>local, files, filesystem, ingest, ingress, get, 
source, input</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>Input 
Directory</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The input directory from which 
to pull files<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>File Filter</strong></td><td 
id="default-value">[^\.].*</td><td id="allowable-values"></td><td 
id="description">Only files whose names match the given regular expression will 
be picked up</td></tr><tr><td id="name">Path Filter</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">When Recurse Subdirectories is true, then only subdirectories 
whose path matches the given regular expression will be 
scanned</td></tr><tr><td id="name"><strong>Batch Size</strong></td><td 
id="default-value">10</td><td id="allowable-values"></td><td 
id="description">The maximum number of files to pull in each iteration</td></tr>
 <tr><td id="name"><strong>Keep Source 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">If true, the file is not deleted after it has been copied to 
the Content Repository; this causes the file to be picked up continually and is 
useful for testing purposes.  If not keeping original NiFi will need write 
permissions on the directory it is pulling from otherwise it will ignore the 
file.</td></tr><tr><td id="name"><strong>Recurse 
Subdirectories</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 pull files from 
subdirectories</td></tr><tr><td id="name"><strong>Polling 
Interval</strong></td><td id="default-value">0 sec</td><td 
id="allowable-values"></td><td id="description">Indicates how long to wait 
before performing a directory listing</td></tr><tr><td id="name"><strong>Ignore 
Hidden Files</
 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 hidden files should be 
ignored</td></tr><tr><td id="name"><strong>Minimum File Age</strong></td><td 
id="default-value">0 sec</td><td id="allowable-values"></td><td 
id="description">The minimum age that a file must be in order to be pulled; any 
file younger than this amount of time (according to last modification date) 
will be ignored</td></tr><tr><td id="name">Maximum File Age</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
maximum age that a file must be in order to be pulled; any file older than this 
amount of time (according to last modification date) will be 
ignored</td></tr><tr><td id="name"><strong>Minimum File Size</strong></td><td 
id="default-value">0 B</td><td id="allowable-values"></td><td 
id="description">The minimum size that a file must be in order to be 
pulled</td></tr><tr><t
 d id="name">Maximum File Size</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The maximum size that a file 
can be in order to be pulled</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>All
 files are routed to success</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>filename</td><td>The
 filename is set to the name of the file on 
disk</td></tr><tr><td>path</td><td>The path is set to the relative path of the 
file's directory on disk. For example, if the &lt;Input Directory&gt; property 
is set to /tmp, files picked up from /tmp will have the path attribute set to 
./. If the &lt;Recurse Subdirectories&gt; property is set to true and a file is 
picked up from /tmp/abc/1/2/3, then the path attribute will be set to 
abc/1/2/3</td></tr><tr><td>file.creationTim
 e</td><td>The date and time that the file was created. May not work on all 
file systems</td></tr><tr><td>file.lastModifiedTime</td><td>The date and time 
that the file was last modified. May not work on all file 
systems</td></tr><tr><td>file.lastAccessTime</td><td>The date and time that the 
file was last accessed. May not work on all file 
systems</td></tr><tr><td>file.owner</td><td>The owner of the file. May not work 
on all file systems</td></tr><tr><td>file.group</td><td>The group owner of the 
file. May not work on all file 
systems</td></tr><tr><td>file.permissions</td><td>The read/write/execute 
permissions of the file. May not work on all file 
systems</td></tr><tr><td>absolute.path</td><td>The full/absolute path from 
where a file was picked up. The current 'path' attribute is still populated, 
but may be a relative path</td></tr></table><h3>State management: </h3>This 
component does not store state.<h3>Restricted: </h3><table 
id="restrictions"><tr><th>Required Permission</th><th>Exp
 lanation</th></tr><tr><td>read filesystem</td><td>Provides operator the 
ability to read from any file that NiFi has access to.</td></tr><tr><td>write 
filesystem</td><td>Provides operator the ability to delete any file that NiFi 
has access to.</td></tr></table><h3>Input requirement: </h3>This component does 
not allow an incoming relationship.<h3>System Resource Considerations:</h3>None 
specified.<h3>See Also:</h3><p><a 
href="../org.apache.nifi.processors.standard.PutFile/index.html">PutFile</a>, 
<a 
href="../org.apache.nifi.processors.standard.FetchFile/index.html">FetchFile</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.GetHTTP/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.GetHTTP/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.GetHTTP/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.GetHTTP/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1,2 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>GetHTTP</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;">GetHTTP</h1><h2>Description: </h2><p>Fetches data from an HTTP or HTTPS 
URL and writes the data to the content of a FlowFile. Once the content has been 
fetched, the ETag and Last Modified dates are remembered (if the web server 
supports these concepts). This allows the Processor to fetch new data only if 
the remote data has changed or until the state is cleared. That is, once the 
content has been fetched from the given URL, it will not be fetched again until 
the content on the remote server changes. Note that due to limitations on state 
management, stored "last modified" and etag fields never expire. If
  the URL in GetHttp uses Expression Language that is unbounded, there is the 
potential for Out of Memory Errors to occur.</p><h3>Tags: </h3><p>get, fetch, 
poll, http, https, ingest, source, input</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>URL</strong></td><td id="default-value"></td><td id=
 "allowable-values"></td><td id="description">The URL to pull 
from<br/><strong>Supports Expression Language: true</strong></td></tr><tr><td 
id="name"><strong>Filename</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The filename to assign to the 
file when pulled<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</td></tr><tr><td id="name">Userna
 me</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">Username required to access the URL</td></tr><tr><td 
id="name">Password</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Password required to access the 
URL<br/><strong>Sensitive Property: true</strong></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">How long to wait 
when attempting to connect to the remote server before giving 
up</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">How long to wait between receiving segments of data from the 
remote server before giving up and discarding the partial file</td></tr><tr><td 
id="name">User Agent</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">What to report as the User 
Agent when we con
 nect to the remote server</td></tr><tr><td id="name">Accept 
Content-Type</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">If specified, requests will only accept the provided 
Content-Type</td></tr><tr><td id="name">Follow Redirects</td><td 
id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">If we receive a 3xx HTTP Status Code from the server, 
indicates whether or not we should follow the redirect that the server 
specifies</td></tr><tr><td id="name">Redirect Cookie Policy</td><td 
id="default-value">default</td><td id="allowable-values"><ul><li>default <img 
src="../../../../../html/images/iconInfo.png" alt="Default cookie policy that 
provides a higher degree of compatibility with common cookie management of 
popular HTTP agents for non-standard (Netscape style) cookies." title="Default 
cookie policy that provides a higher degree of compatibility with common cookie 
management of popular 
 HTTP agents for non-standard (Netscape style) 
cookies."></img></li><li>standard <img 
src="../../../../../html/images/iconInfo.png" alt="RFC 6265 compliant cookie 
policy (interoperability profile)." title="RFC 6265 compliant cookie policy 
(interoperability profile)."></img></li><li>strict <img 
src="../../../../../html/images/iconInfo.png" alt="RFC 6265 compliant cookie 
policy (strict profile)." title="RFC 6265 compliant cookie policy (strict 
profile)."></img></li><li>netscape <img 
src="../../../../../html/images/iconInfo.png" alt="Netscape draft compliant 
cookie policy." title="Netscape draft compliant cookie 
policy."></img></li><li>ignore <img 
src="../../../../../html/images/iconInfo.png" alt="A cookie policy that ignores 
cookies." title="A cookie policy that ignores 
cookies."></img></li></ul></td><td id="description">When a HTTP server responds 
to a request with a redirect, this is the cookie policy used to copy cookies to 
the following request.</td></tr><tr><td id="name">Proxy Hos
 t</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">The fully qualified hostname 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></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">Header Name</td><td id="value">The Expression Language to be used to 
populate the header value</td><td>The additional headers to be sent by the 
processor whenever making a new HTTP request. 
+ Setting a dynamic property name to XYZ and value to ${attribute} will result 
in the header 'XYZ: attribute_value' being sent to the HTTP 
endpoint</td></tr></table></p><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>All
 files are transferred to the success 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>filename</td><td>The
 filename is set to the name of the file on the remote 
server</td></tr><tr><td>mime.type</td><td>The MIME Type of the FlowFile, as 
reported by the HTTP Content-Type header</td></tr></table><h3>State management: 
</h3><table 
id="stateful"><tr><th>Scope</th><th>Description</th></tr><tr><td>LOCAL</td><td>Stores
 Last Modified Time and ETag headers returned by server so that the same data 
will not be fetched multiple times.</td></tr></table><h3>Restricted: </h3>This 
compone
 nt is not restricted.<h3>Input requirement: </h3>This component does not allow 
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.GetJMSQueue/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.GetJMSQueue/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.GetJMSQueue/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.GetJMSQueue/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>GetJMSQueue</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;">GetJMSQueue</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.ConsumeJMS/index.html">ConsumeJMS</a></p><h2>Description:
 </h2><p>Pulls messages from a ActiveMQ JMS Queue, creating a FlowFile for each 
JMS Message or bundle of messages, as configured</p><h3>Tags: </h3><p>jms, 
queue, listen, get, pull, source, consume, consumer</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 
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 
id="default-value"></td><td id="allowable-values"></t
 d><td id="description">The name of the JMS Topic or queue 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="de
 fault-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>Acknowledgement 
Mode</strong></td><td id="default-value">Client Acknowledge</td><td 
id="allowable-values"><ul><li>Client Acknowledge</li><li>Auto 
Acknowledge</li></ul></td><td id="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.</td></tr><tr><td 
id="name">Message Selector</td><td id="default-v
 alue"></td><td id="allowable-values"></td><td id="description">The JMS Message 
Selector to use in order to narrow the messages that are 
pulled</td></tr><tr><td id="name"><strong>Copy JMS Properties to 
Attributes</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 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</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="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>All
 FlowFiles are routed to success</td></tr></table><h3>Reads Attribu
 tes: </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 does not 
allow an incoming relationship.<h3>System Resource Considerations:</h3>None 
specified.<h3>See Also:</h3><p><a 
href="../org.apache.nifi.processors.standard.PutJMS/index.html">PutJMS</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.GetJMSTopic/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.GetJMSTopic/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.GetJMSTopic/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.GetJMSTopic/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>GetJMSTopic</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;">GetJMSTopic</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.ConsumeJMS/index.html">ConsumeJMS</a></p><h2>Description:
 </h2><p>Pulls messages from a ActiveMQ JMS Topic, creating a FlowFile for each 
JMS Message or bundle of messages, as configured.</p><h3>Tags: </h3><p>jms, 
topic, subscription, durable, non-durable, listen, get, pull, source, consume, 
consumer</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 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 
id="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>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>Acknowledgement 
Mode</strong></td><td id="default-value">Client Acknowledge</td><td 
id="allowable-values"><ul><li>Client Acknowledge</li><li>Auto 
Acknowledge</li></ul></td><td id="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.</td></tr><tr><td 
id="name">Me
 ssage Selector</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The JMS Message Selector to use 
in order to narrow the messages that are pulled</td></tr><tr><td 
id="name"><strong>Copy JMS Properties to Attributes</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 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</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><tr><td id="name"><strong>Use Durable 
Subscription</strong></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, connections to the specified topic will 
 >use Durable Subscription so that messages are queued when we are not pulling 
 >them</td></tr></table><h3>Relationships: </h3><table 
 >id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>All
 > FlowFiles are routed to success</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 does not allow an incoming relationship.<h3>System Resource 
 >Considerations:</h3>None specified.<h3>See Also:</h3><p><a 
 >href="../org.apache.nifi.processors.standard.PutJMS/index.html">PutJMS</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.GetSFTP/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.GetSFTP/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.GetSFTP/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.GetSFTP/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>GetSFTP</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;">GetSFTP</h1><h2>Description: </h2><p>Fetches files from an SFTP Server 
and creates FlowFiles from them</p><h3>Tags: </h3><p>sftp, get, retrieve, 
files, fetch, remote, ingest, source, input</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: t
 rue</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">File Filter Regex</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Provides a Java Regular Expression for filtering Filenames; if 
a filter is supplied, only files whose names match that Regular Expression will 
be fetched</td></tr><tr><td id="name">Path Filter Regex</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">When Search Recursively is true, then only subdirectories 
whose path matches the given Regular Expression will be 
scanned</td></tr><tr><td id="name"><strong>Polling Interval</strong></td><td 
id="default-value">60 sec</td><td id="allowable-values"></td><td 
id="description">Determines how long to wait between fetching the listing for 
new files</td></tr><tr><td id="name"><strong>Search 
Recursively</strong></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, will pull files from arbitrarily nes
 ted subdirectories; otherwise, will not traverse 
subdirectories</td></tr><tr><td id="name"><strong>Ignore Dotted 
Files</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, files whose names begin with a dot (".") will be 
ignored</td></tr><tr><td id="name"><strong>Delete Original</strong></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 the file is deleted from the remote 
system after it has been successfully transferred</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 transferr
 ing 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">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"><strong>Max 
Selects</strong></td><td id="default-value">100</td><td 
id="allowable-values"></td><td id="description">The maximum number of files to 
pull in a single connection</td></tr><tr><td id="name"><strong>Remote Poll 
Batch Size</strong></td><td id="default-value">5000</td><td 
id="allowable-values"></td><td id="description">The value specifies how many 
file paths to find in a given directory on the remote system when doing a file 
listing. This value in general should not need to be modified but when polling 
against a remote system with a tremendous number of files this value can be
  critical.  Setting this value too high can result very poor performance and 
setting it too low can cause the flow to be slower than 
normal.</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 message 
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><tr><td id="name"><strong>Use
  Natural Ordering</strong></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, will pull files in the order in which they are 
naturally listed; otherwise, the order in which the files will be pulled is not 
defined</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>All
 FlowFiles that are received are routed to success</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>filename</td><td>The
 filename is set to the name of the file on the remote 
server</td></tr><tr><td>path</td><td>The path is set to the path of the file's 
directory on the remote server. For example, if the &lt;Remote Path&gt; 
property is set to /tmp, files picked up from /tmp will have the path attribute 
set to /tmp. If the &lt;Search Recursivel
 y&gt; property is set to true and a file is picked up from /tmp/abc/1/2/3, 
then the path attribute will be set to 
/tmp/abc/1/2/3</td></tr><tr><td>file.lastModifiedTime</td><td>The date and time 
that the source file was last modified</td></tr><tr><td>file.owner</td><td>The 
numeric owner id of the source file</td></tr><tr><td>file.group</td><td>The 
numeric group id of the source 
file</td></tr><tr><td>file.permissions</td><td>The read/write/execute 
permissions of the source file</td></tr><tr><td>absolute.path</td><td>The 
full/absolute path from where a file was picked up. The current 'path' 
attribute is still populated, but may be a relative 
path</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 does not allow an incoming 
relationship.<h3>System Resource Considerations:</h3>None specified.<h3>See 
Also:</h3><p><a href="../org.apache.nifi.processors.standard.PutS
 FTP/index.html">PutSFTP</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.HandleHttpRequest/additionalDetails.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.HandleHttpRequest/additionalDetails.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.HandleHttpRequest/additionalDetails.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.HandleHttpRequest/additionalDetails.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1,43 @@
+<!DOCTYPE html>
+<html lang="en">
+    <!--
+      Licensed to the Apache Software Foundation (ASF) under one or more
+      contributor license agreements.  See the NOTICE file distributed with
+      this work for additional information regarding copyright ownership.
+      The ASF licenses this file to You under the Apache License, Version 2.0
+      (the "License"); you may not use this file except in compliance with
+      the License.  You may obtain a copy of the License at
+          http://www.apache.org/licenses/LICENSE-2.0
+      Unless required by applicable law or agreed to in writing, software
+      distributed under the License is distributed on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+      See the License for the specific language governing permissions and
+      limitations under the License.
+    -->
+    <head>
+        <meta charset="utf-8" />
+        <title>HandleHttpRequest</title>
+        <link rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css" />
+    </head>
+
+    <body>
+        <h2>Usage Description</h2>
+        <p>
+            The pairing of this Processor with a <a 
href="../org.apache.nifi.processors.standard.HandleHttpResponse/index.html">HandleHttpResponse</a>
 Processor
+            provides the ability to use NiFi to visually construct a web 
server that can carry out any functionality that is available
+            through the existing Processors. For example, one could construct 
a Web-based front end to an SFTP Server by constructing a
+            flow such as:
+        </p>
+
+        <p>
+            <a href="index.html">HandleHttpRequest</a> -> 
+            <a 
href="../org.apache.nifi.processors.standard.PutSFTP/index.html">PutSFTP</a> ->
+            <a 
href="../org.apache.nifi.processors.standard.HandleHttpResponse/index.html">HandleHttpResponse</a>
+        </p>
+
+        <p>
+            The HandleHttpRequest Processor provides several Properties to 
configure which methods are supported, the paths that are
+            supported, and SSL configuration. 
+        </p>
+    </body>
+</html>

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.HandleHttpRequest/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.HandleHttpRequest/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.HandleHttpRequest/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.HandleHttpRequest/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>HandleHttpRequest</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;">HandleHttpRequest</h1><h2>Description: </h2><p>Starts an HTTP Server and 
listens for HTTP Requests. For each request, creates a FlowFile and transfers 
to 'success'. This Processor is designed to be used in conjunction with the 
HandleHttpResponse Processor in order to create a Web Service</p><p><a 
href="additionalDetails.html">Additional Details...</a></p><h3>Tags: 
</h3><p>http, https, request, listen, ingress, web service</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. Th
 e table also indicates any default values.</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>Listening 
Port</strong></td><td id="default-value">80</td><td 
id="allowable-values"></td><td id="description">The Port to listen on for 
incoming HTTP requests</td></tr><tr><td id="name">Hostname</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
Hostname to bind to. If not specified, will bind to all hosts</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/>RestrictedSSLContextService<br/><strong>Implementation: 
</strong><a 
href="../../../nifi-ssl-context-service-nar/1.6.0/org.apache.nifi.ssl.StandardRestrictedSSLContextService/index.html">StandardRestrictedSSLContextService</a></td><td
 id="description">The SSL Context Service to use in order to secure the server. 
If s
 pecified, the server will accept only HTTPS requests; otherwise, the server 
will accept only HTTP requests</td></tr><tr><td id="name"><strong>HTTP Context 
Map</strong></td><td id="default-value"></td><td 
id="allowable-values"><strong>Controller Service API: 
</strong><br/>HttpContextMap<br/><strong>Implementation: </strong><a 
href="../../../nifi-http-context-map-nar/1.6.0/org.apache.nifi.http.StandardHttpContextMap/index.html">StandardHttpContextMap</a></td><td
 id="description">The HTTP Context Map Controller Service to use for caching 
the HTTP Request Information</td></tr><tr><td id="name">Allowed Paths</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">A 
Regular Expression that specifies the valid HTTP Paths that are allowed in the 
incoming URL Requests. If this value is specified and the path of the HTTP 
Requests does not match this Regular Expression, the Processor will respond 
with a 404: NotFound</td></tr><tr><td id="name"><strong>Default URL Ch
 aracter Set</strong></td><td id="default-value">UTF-8</td><td 
id="allowable-values"></td><td id="description">The character set to use for 
decoding URL parameters if the HTTP Request does not supply 
one</td></tr><tr><td id="name"><strong>Allow GET</strong></td><td 
id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Allow HTTP GET Method</td></tr><tr><td id="name"><strong>Allow 
POST</strong></td><td id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Allow HTTP POST Method</td></tr><tr><td 
id="name"><strong>Allow PUT</strong></td><td id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Allow HTTP PUT Method</td></tr><tr><td id="name"><strong>Allow 
DELETE</strong></td><td id="default-value">true</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Allow HTTP 
 DELETE Method</td></tr><tr><td id="name"><strong>Allow HEAD</strong></td><td 
id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Allow HTTP HEAD Method</td></tr><tr><td 
id="name"><strong>Allow OPTIONS</strong></td><td 
id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Allow HTTP OPTIONS Method</td></tr><tr><td 
id="name">Additional HTTP Methods</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">A comma-separated list of 
non-standard HTTP Methods that should be allowed</td></tr><tr><td 
id="name"><strong>Client Authentication</strong></td><td id="default-value">No 
Authentication</td><td id="allowable-values"><ul><li>No Authentication <img 
src="../../../../../html/images/iconInfo.png" alt="Processor will not 
authenticate clients. Anyone can communicate with this Processor anonymously" 
title="Processor will not authenticate cl
 ients. Anyone can communicate with this Processor 
anonymously"></img></li><li>Want Authentication <img 
src="../../../../../html/images/iconInfo.png" alt="Processor will try to verify 
the client but if unable to verify will allow the client to communicate 
anonymously" title="Processor will try to verify the client but if unable to 
verify will allow the client to communicate anonymously"></img></li><li>Need 
Authentication <img src="../../../../../html/images/iconInfo.png" 
alt="Processor will reject communications from any client unless the client 
provides a certificate that is trusted by the TrustStorespecified in the SSL 
Context Service" title="Processor will reject communications from any client 
unless the client provides a certificate that is trusted by the 
TrustStorespecified in the SSL Context Service"></img></li></ul></td><td 
id="description">Specifies whether or not the Processor should authenticate 
clients. This value is ignored if the &lt;SSL Context Service&gt; Property is n
 ot specified or the SSL Context provided uses only a KeyStore and not a 
TrustStore.</td></tr><tr><td id="name"><strong>Container Queue 
Size</strong></td><td id="default-value">50</td><td 
id="allowable-values"></td><td id="description">The size of the queue for Http 
Request Containers</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>All
 content that is received is routed to the 'success' 
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>http.context.identifier</td><td>An
 identifier that allows the HandleHttpRequest and HandleHttpResponse to 
coordinate which FlowFile belongs to which HTTP 
Request/Response.</td></tr><tr><td>mime.type</td><td>The MIME Type of the data, 
according to the HTTP Header 
"Content-Type"</td></tr><tr><td>http.servlet.path</td><td>The part of the reques
 t URL that is considered the Servlet 
Path</td></tr><tr><td>http.context.path</td><td>The part of the request URL 
that is considered to be the Context 
Path</td></tr><tr><td>http.method</td><td>The HTTP Method that was used for the 
request, such as GET or POST</td></tr><tr><td>http.local.name</td><td>IP 
address/hostname of the 
server</td></tr><tr><td>http.server.port</td><td>Listening port of the 
server</td></tr><tr><td>http.query.string</td><td>The query string portion of 
the Request URL</td></tr><tr><td>http.remote.host</td><td>The hostname of the 
requestor</td></tr><tr><td>http.remote.addr</td><td>The hostname:port 
combination of the requestor</td></tr><tr><td>http.remote.user</td><td>The 
username of the requestor</td></tr><tr><td>http.protocol</td><td>The protocol 
used to communicate</td></tr><tr><td>http.request.uri</td><td>The full Request 
URL</td></tr><tr><td>http.auth.type</td><td>The type of HTTP Authorization 
used</td></tr><tr><td>http.principal.name</td><td>The name of the 
 authenticated user making the 
request</td></tr><tr><td>http.subject.dn</td><td>The Distinguished Name of the 
requestor. This value will not be populated unless the Processor is configured 
to use an SSLContext Service</td></tr><tr><td>http.issuer.dn</td><td>The 
Distinguished Name of the entity that issued the Subject's certificate. This 
value will not be populated unless the Processor is configured to use an 
SSLContext Service</td></tr><tr><td>http.headers.XXX</td><td>Each of the HTTP 
Headers that is received in the request will be added as an attribute, prefixed 
with "http.headers." For example, if the request contains an HTTP Header named 
"x-my-header", then the value will be added to an attribute named 
"http.headers.x-my-header"</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 does not allow an 
incoming relationship.<h3>System Resource Considerations:</h3
 >None specified.<h3>See Also:</h3><p><a 
 >href="../org.apache.nifi.processors.standard.HandleHttpResponse/index.html">HandleHttpResponse</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.HandleHttpResponse/additionalDetails.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.HandleHttpResponse/additionalDetails.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.HandleHttpResponse/additionalDetails.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.HandleHttpResponse/additionalDetails.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1,44 @@
+<!DOCTYPE html>
+<html lang="en">
+    <!--
+      Licensed to the Apache Software Foundation (ASF) under one or more
+      contributor license agreements.  See the NOTICE file distributed with
+      this work for additional information regarding copyright ownership.
+      The ASF licenses this file to You under the Apache License, Version 2.0
+      (the "License"); you may not use this file except in compliance with
+      the License.  You may obtain a copy of the License at
+          http://www.apache.org/licenses/LICENSE-2.0
+      Unless required by applicable law or agreed to in writing, software
+      distributed under the License is distributed on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+      See the License for the specific language governing permissions and
+      limitations under the License.
+    -->
+    <head>
+        <meta charset="utf-8" />
+        <title>HandleHttpResponse</title>
+        <link rel="stylesheet" href="../../../../../css/component-usage.css" 
type="text/css" />
+    </head>
+
+    <body>
+        <!-- Processor Documentation 
================================================== -->
+        <h2>Usage Description:</h2>
+        <p>
+            The pairing of this Processor with a <a 
href="../org.apache.nifi.processors.standard.HandleHttpRequest/index.html">HandleHttpRequest</a>
 Processor
+            provides the ability to use NiFi to visually construct a web 
server that can carry out any functionality that is available
+            through the existing Processors. For example, one could construct 
a Web-based front end to an SFTP Server by constructing a
+            flow such as:
+        </p>
+
+        <p>
+            <a 
href="../org.apache.nifi.processors.standard.HandleHttpRequest/index.html">HandleHttpRequest</a>
 -> 
+            <a 
href="../org.apache.nifi.processors.standard.PutSFTP/index.html">PutSFTP</a> ->
+            <a href="index.html">HandleHttpResponse</a>
+        </p>
+
+        <p>
+            This Processor must be configured with the same &lt;HTTP Context 
Map&gt; service as the corresponding HandleHttpRequest Processor.
+            Otherwise, all FlowFiles will be routed to the 'failure' 
relationship.
+        </p>
+    </body>
+</html>

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.HandleHttpResponse/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.HandleHttpResponse/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.HandleHttpResponse/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.HandleHttpResponse/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>HandleHttpResponse</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;">HandleHttpResponse</h1><h2>Description: </h2><p>Sends an HTTP Response 
to the Requestor that generated a FlowFile. This Processor is designed to be 
used in conjunction with the HandleHttpRequest in order to create a web 
service.</p><p><a href="additionalDetails.html">Additional 
Details...</a></p><h3>Tags: </h3><p>http, https, response, egress, web 
service</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 s
 upports 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>HTTP Status Code</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The HTTP Status Code to use 
when responding to the HTTP Request. See Section 10 of RFC 2616 for more 
information.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>HTTP Context 
Map</strong></td><td id="default-value"></td><td 
id="allowable-values"><strong>Controller Service API: 
</strong><br/>HttpContextMap<br/><strong>Implementation: </strong><a 
href="../../../nifi-http-context-map-nar/1.6.0/org.apache.nifi.http.StandardHttpContextMap/index.html">StandardHttpContextMap</a></td><td
 id="description">The HTTP Context Map Controller Service to use for caching 
the HTTP Request Information</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">An HTTP header name</td><td id="value">An HTTP header 
value</td><td>These HTTPHeaders are set in the HTTP 
Response</td></tr></table></p><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>FlowFiles
 will be routed to this Relationship after the response has been successfully 
sent to the requestor</td></tr><tr><td>failure</td><td>FlowFiles will be routed 
to this Relationship if the Processor is unable to respond to the requestor. 
This may happen, for instance, if the connection times out or if NiFi is 
restarted before responding to the HTTP Request.</td></tr></table><h3>Reads 
Attributes: </h3><table 
id="reads-attributes"><tr><th>Name</th><th>Description</th></tr><tr><td>http.context.identifier</td><
 td>The value of this attribute is used to lookup the HTTP Response so that the 
proper message can be sent back to the requestor. If this attribute is missing, 
the FlowFile will be routed to 
'failure.'</td></tr><tr><td>http.request.uri</td><td>Value of the URI requested 
by the client. Used for provenance 
event.</td></tr><tr><td>http.remote.host</td><td>IP address of the client. Used 
for provenance event.</td></tr><tr><td>http.local.name</td><td>IP 
address/hostname of the server. Used for provenance 
event.</td></tr><tr><td>http.server.port</td><td>Listening port of the server. 
Used for provenance event.</td></tr><tr><td>http.subject.dn</td><td>SSL 
distinguished name (if any). Used for provenance 
event.</td></tr></table><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 Consideration
 s:</h3>None specified.<h3>See Also:</h3><p><a 
href="../org.apache.nifi.processors.standard.HandleHttpRequest/index.html">HandleHttpRequest</a>,
 <a 
href="../../../nifi-http-context-map-nar/1.6.0/org.apache.nifi.http.StandardHttpContextMap/index.html">StandardHttpContextMap</a>,
 <a 
href="../../../nifi-ssl-context-service-nar/1.6.0/org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</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.HashAttribute/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.HashAttribute/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.HashAttribute/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.6.0/org.apache.nifi.processors.standard.HashAttribute/index.html
 Sat Apr  7 00:33:22 2018
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>HashAttribute</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;">HashAttribute</h1><h2>Description: </h2><p>Hashes together the key/value 
pairs of several FlowFile Attributes and adds the hash as a new attribute. 
Optional properties are to be added such that the name of the property is the 
name of a FlowFile Attribute to consider and the value of the property is a 
regular expression that, if matched by the attribute value, will cause that 
attribute to be used as part of the hash. If the regular expression contains a 
capturing group, only the value of the capturing group will be 
used.</p><h3>Tags: </h3><p>attributes, hash</p><h3>Properties: </h3><p>In the 
list b
 elow, 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.</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>Hash Value 
Attribute Key</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The name of the FlowFile 
Attribute where the hash value should be stored</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">A flowfile attribute key for attribute inspection</td><td 
id="value">A Regular Expression</td><td>This regular expression is evaluated 
against the flowfile attribute values. If the regular expression contains a 
capturing group, the value of that group
  will be used when comparing flow file attributes. Otherwise, the original 
flow file attribute's value will be used if and only if the value matches the 
given regular expression.</td></tr></table></p><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>Used
 for FlowFiles that have a hash value 
added</td></tr><tr><td>failure</td><td>Used for FlowFiles that are missing 
required attributes</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>&lt;Hash
 Value Attribute Key&gt;</td><td>This Processor adds an attribute whose value 
is the result of Hashing the existing FlowFile attributes. The name of this 
attribute is specified by the &lt;Hash Value Attribute Key&gt; 
property.</td></tr></table><h3>State management: </h3>This component does not 
store state.<h3>Restricted: </h3>This component is not restricted.<h3>Inpu
 t requirement: </h3>This component requires an incoming 
relationship.<h3>System Resource Considerations:</h3>None 
specified.</body></html>
\ No newline at end of file


Reply via email to