Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListenTCP/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListenTCP/index.html?rev=1736720&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListenTCP/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListenTCP/index.html
 Sun Mar 27 04:51:17 2016
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ListenTCP</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Listens for 
incoming TCP connections and reads data from each connection using a line 
separator as the message demarcator. The default behavior is for each message 
to produce a single FlowFile, however this can be controlled by increasing the 
Batch Size to a larger value for higher throughput. The Receive Buffer Size 
must be set as large as the largest messages expected to be received, meaning 
if every 100kb there is a line separator, then the Receive Buffer Size must be 
greater than 100kb.</p><h3>Tags: </h3><p>listen, tcp, tls, 
ssl</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 support
 s 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">Local Network Interface</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The name of a local network 
interface to be used to restrict listening to a specific 
LAN.<br/><strong>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 to listen on for 
communication.</td></tr><tr><td id="name"><strong>Receive Buffer 
Size</strong></td><td id="default-value">65507 B</td><td 
id="allowable-values"></td><td id="description">The size of each buffer used to 
receive messages. Adjust this value appropriately based on the expected size of 
the incoming messages.</td></tr><tr><td id="name"><strong>Max Size of Message 
Que
 ue</strong></td><td id="default-value">10000</td><td 
id="allowable-values"></td><td id="description">The maximum size of the 
internal queue used to buffer messages being transferred from the underlying 
channel to the processor. Setting this value higher allows more messages to be 
buffered in memory during surges of incoming messages, but increases the total 
memory used by the processor.</td></tr><tr><td id="name"><strong>Max Size of 
Socket Buffer</strong></td><td id="default-value">1 MB</td><td 
id="allowable-values"></td><td id="description">The maximum size of the socket 
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>Character Set</strong></td><td 
id="default-value">UTF-8</td><td id="allowable-values"></td><td 
id="description">Specifies the character set of t
 he received data.</td></tr><tr><td id="name"><strong>Max Batch 
Size</strong></td><td id="default-value">1</td><td 
id="allowable-values"></td><td id="description">The maximum number of messages 
to add to a single FlowFile. If multiple messages are available, they will be 
concatenated along with the &lt;Message Delimiter&gt; up to this configured 
maximum number of messages</td></tr><tr><td id="name"><strong>Batching Message 
Delimiter</strong></td><td id="default-value">\n</td><td 
id="allowable-values"></td><td id="description">Specifies the delimiter to 
place between messages when multiple messages are bundled together (see &lt;Max 
Batch Size&gt; property).</td></tr><tr><td id="name"><strong>Max Number of TCP 
Connections</strong></td><td id="default-value">2</td><td 
id="allowable-values"></td><td id="description">The maximum number of 
concurrent TCP connections to accept.</td></tr><tr><td id="name">SSL Context 
Service</td><td id="default-value"></td><td id="allowable-values"><strong>C
 ontroller Service API: 
</strong><br/>SSLContextService<br/><strong>Implementation:</strong><br/><a 
href="../org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</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 received over a secure 
connection.</td></tr><tr><td id="name">Client Auth</td><td 
id="default-value">REQUIRED</td><td 
id="allowable-values"><ul><li>WANT</li><li>REQUIRED</li><li>NONE</li></ul></td><td
 id="description">The client authentication policy to use for the SSL Context. 
Only used if an SSL Context Service is 
provided.</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>Messages
 received successfully will be sent out this 
relationship.</td></tr></table><h3>Reads Attributes: </h3>None 
specified.<h3>Writes Attributes: </h3><table 
id="writes-attributes"><tr><th>Name</th><th>Des
 cription</th></tr><tr><td>tcp.sender</td><td>The sending host of the 
messages.</td></tr><tr><td>tcp.port</td><td>The sending port the messages were 
received.</td></tr></table></body></html>
\ No newline at end of file

Modified: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListenUDP/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListenUDP/index.html?rev=1736720&r1=1736719&r2=1736720&view=diff
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListenUDP/index.html
 (original)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.ListenUDP/index.html
 Sun Mar 27 04:51:17 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ListenUDP</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Listens for 
Datagram Packets on a given port and concatenates the contents of those packets 
together generating flow files</p><h3>Tags: </h3><p>ingest, udp, listen, 
source</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">Sending Host</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">IP, or name, of a remote host. 
Only Datagrams fro
 m the specified Sending Host Port and this host will be accepted. Improves 
Performance. May be a system property or an environment 
variable.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Sending Host Port</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Port being used by remote host to send Datagrams. Only 
Datagrams from the specified Sending Host and this port will be accepted. 
Improves Performance. May be a system property or an environment 
variable.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name">Local Network Interface</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">The 
name of a local network interface to be used to restrict listening for UDP 
Datagrams to a specific LAN.May be a system property or an environment 
variable.<br/><strong>Supports Expression Language: 
true</strong></td></tr><tr><td id="name"><strong>Channel Reader Interval</
 strong></td><td id="default-value">50 ms</td><td 
id="allowable-values"></td><td id="description">Scheduling interval for each 
read channel.</td></tr><tr><td id="name"><strong>FlowFile Size 
Trigger</strong></td><td id="default-value">1 MB</td><td 
id="allowable-values"></td><td id="description">Determines the (almost) upper 
bound size at which a flow file would be generated.</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">Determines the size 
each receive buffer may be</td></tr><tr><td id="name"><strong>Max size of UDP 
Buffer</strong></td><td id="default-value">1 MB</td><td 
id="allowable-values"></td><td id="description">The maximum UDP buffer size 
that should be used. This is a suggestion to the Operating System to indicate 
how big the udp socket buffer should be.</td></tr><tr><td 
id="name"><strong>Port</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="desc
 ription">Port to listen on. Must be known by senders of 
Datagrams.</td></tr><tr><td id="name"><strong>Receive Buffer 
Count</strong></td><td id="default-value">4</td><td 
id="allowable-values"></td><td id="description">Number of receiving buffers to 
be used to accept data from the socket. Higher numbers means more ram is 
allocated but can allow better throughput.</td></tr><tr><td 
id="name"><strong>FlowFiles Per Session</strong></td><td 
id="default-value">10</td><td id="allowable-values"></td><td 
id="description">The number of flow files per session.</td></tr><tr><td 
id="name"><strong>Receive Timeout</strong></td><td id="default-value">5 
secs</td><td id="allowable-values"></td><td id="description">The time out 
period when waiting to receive data from the socket. Specify 
units.</td></tr><tr><td id="name"><strong>FlowFile Per 
Datagram</strong></td><td id="default-value">false</td><td 
id="allowable-values"><ul><li>true</li><li>false</li></ul></td><td 
id="description">Determines if this pr
 ocessor emits each datagram as a FlowFile, or if multiple datagrams can be 
placed in a single FlowFile.</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>success</td><td>Connection
 which contains concatenated Datagram Packets</td></tr></table><h3>Reads 
Attributes: </h3>None specified.<h3>Writes Attributes: </h3>None 
specified.</body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>ListenUDP</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Listens for 
Datagram Packets on a given port. The default behavior produces a FlowFile per 
datagram, however for higher throughput the Max Batch Size property may be 
increased to specify the number of datagrams to batch together in a single 
FlowFile. This processor can be restricted to listening for datagrams from  a 
specific remote host and port by specifying the Sending Host and Sending Host 
Port properties, otherwise it will listen for datagrams from all hosts and 
ports.</p><h3>Tags: </h3><p>ingest, udp, listen, source</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 hr
 ef="../../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">Local Network Interface</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The name of a local network 
interface to be used to restrict listening to a specific 
LAN.<br/><strong>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 to listen on for 
communication.</td></tr><tr><td id="name"><strong>Receive Buffer 
Size</strong></td><td id="default-value">65507 B</td><td 
id="allowable-values"></td><td id="description">The size of each buffer used to 
receive messages. Adjust this value appropriately based on the expected size of 
the incoming messages.</td></tr><tr><td id="name"><strong>Max Size of Message 
Queue</strong>
 </td><td id="default-value">10000</td><td id="allowable-values"></td><td 
id="description">The maximum size of the internal queue used to buffer messages 
being transferred from the underlying channel to the processor. Setting this 
value higher allows more messages to be buffered in memory during surges of 
incoming messages, but increases the total memory used by the 
processor.</td></tr><tr><td id="name"><strong>Max Size of Socket 
Buffer</strong></td><td id="default-value">1 MB</td><td 
id="allowable-values"></td><td id="description">The maximum size of the socket 
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>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 received
  data.</td></tr><tr><td id="name"><strong>Max Batch Size</strong></td><td 
id="default-value">1</td><td id="allowable-values"></td><td 
id="description">The maximum number of messages to add to a single FlowFile. If 
multiple messages are available, they will be concatenated along with the 
&lt;Message Delimiter&gt; up to this configured maximum number of 
messages</td></tr><tr><td id="name"><strong>Batching Message 
Delimiter</strong></td><td id="default-value">\n</td><td 
id="allowable-values"></td><td id="description">Specifies the delimiter to 
place between messages when multiple messages are bundled together (see &lt;Max 
Batch Size&gt; property).</td></tr><tr><td id="name">Sending Host</td><td 
id="default-value"></td><td id="allowable-values"></td><td id="description">IP, 
or name, of a remote host. Only Datagrams from the specified Sending Host Port 
and this host will be accepted. Improves Performance. May be a system property 
or an environment variable.<br/><strong>Supports Expressio
 n Language: true</strong></td></tr><tr><td id="name">Sending Host Port</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Port being used by remote host to send Datagrams. Only 
Datagrams from the specified Sending Host and this port will be accepted. 
Improves Performance. May be a system property or an environment 
variable.<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>Messages
 received successfully will be sent out 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>udp.sender</td><td>The
 sending host of the messages.</td></tr><tr><td>udp.port</td><td>The sending 
port the messages were received.</td></tr></table></body></html>
\ No newline at end of file

Modified: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.PutSyslog/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.PutSyslog/index.html?rev=1736720&r1=1736719&r2=1736720&view=diff
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.PutSyslog/index.html
 (original)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.PutSyslog/index.html
 Sun Mar 27 04:51:17 2016
@@ -1 +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><body><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 rout
 ed 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="allowable-values"></td><td 
id="description">The ip address or hostname of the Syslog 
server.</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>UD
 P</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.</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>Implementation:</strong><br/><a 
href="../org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</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 
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></t
 r><tr><td id="name"><strong>Send Buffer Size</strong></td><td 
id="default-value">2048 B</td><td id="allowable-values"></td><td 
id="description">The size of each buffer used to send a Syslog message. Adjust 
this value appropriately based on the expected size of the Syslog messages 
being produced. Messages larger than this buffer size will still be sent, but 
will not make use of the buffer pool.</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.</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</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 mes
 sages, 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 Expre
 ssion 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>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
+<!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><body><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 rout
 ed 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="allowable-values"></td><td 
id="description">The ip address or hostname of the Syslog 
server.</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>UD
 P</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.</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">SSL Context Service</td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: 
</strong><br/>SSLContextService<br/><strong>Implementation:</strong><br/><a 
href="../org.apache.nifi.ssl.StandardSSLContextService/index.html">StandardSSLContextService</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 
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">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</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.</td></tr><tr><td id="name"><strong>Character 
Set</strong></td><td id="default-value">UTF-8</td><td id="allowable-valu
 es"></td><td id="description">Specifies the character set of the Syslog 
messages</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 Expr
 ession 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>Non
 e specified.<h3>Writes Attributes: </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.processors.standard.QueryDatabaseTable/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.QueryDatabaseTable/index.html?rev=1736720&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.QueryDatabaseTable/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.QueryDatabaseTable/index.html
 Sun Mar 27 04:51:17 2016
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>QueryDatabaseTable</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Execute provided 
SQL select query. Query result will be converted to Avro format. Streaming is 
used so arbitrarily large result sets are supported. This processor can be 
scheduled to run on a timer, or cron expression, using the standard scheduling 
methods, or it can be triggered by an incoming FlowFile. If it is triggered by 
an incoming FlowFile, then attributes of that FlowFile will be available when 
evaluating the select query. FlowFile attribute 'querydbtable.row.count' 
indicates how many rows were selected.</p><h3>Tags: </h3><p>sql, select, jdbc, 
query, database</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 de
 fault 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>Database Connection Pooling Service</strong></td><td 
id="default-value"></td><td id="allowable-values"><strong>Controller Service 
API: </strong><br/>DBCPService<br/><strong>Implementation:</strong><br/><a 
href="../org.apache.nifi.dbcp.DBCPConnectionPool/index.html">DBCPConnectionPool</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>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.</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.</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. This 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.</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 t
 han 1 second will be equal to zero.</td></tr><tr><td id="name"><strong>SQL 
Pre-processing Strategy</strong></td><td id="default-value">None</td><td 
id="allowable-values"><ul><li>None</li><li>Oracle</li></ul></td><td 
id="description">The strategy to employ when generating the SQL for querying 
the table. A strategy may include custom or database-specific code, such as the 
treatment of time/date formats.</td></tr></table><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></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>querydbtable.row.count</td><td>Not
 Specified</td></tr></table></body></html>
\ No newline at end of file

Modified: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.RouteText/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.RouteText/index.html?rev=1736720&r1=1736719&r2=1736720&view=diff
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.RouteText/index.html
 (original)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.RouteText/index.html
 Sun Mar 27 04:51:17 2016
@@ -1 +1 @@
-<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>RouteText</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Routes textual 
data based on a set of user-defined rules. Each line in an incoming FlowFile is 
compared against the values specified by user-defined Properties. The mechanism 
by which the text is compared to these user-defined properties is defined by 
the 'Matching Strategy'. The data is then routed according to these rules, 
routing each line of the text individually.</p><h3>Tags: </h3><p>attributes, 
routing, text, regexp, regex, Regular Expression, Expression 
Language</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.</p><table 
id="properties"><tr><th>Name</th><th>Default Value</th><th>Allowable 
Values</th><th>D
 escription</th></tr><tr><td id="name"><strong>Routing 
Strategy</strong></td><td id="default-value">Route to each matching Property 
Name</td><td id="allowable-values"><ul><li>Route to each matching Property Name 
<img src="../../html/images/iconInfo.png" alt="Lines will be routed to each 
relationship whose corresponding expression evaluates to 'true'" title="Lines 
will be routed to each relationship whose corresponding expression evaluates to 
'true'"></img></li><li>Route to 'matched' if line matches all conditions <img 
src="../../html/images/iconInfo.png" alt="Requires that all user-defined 
expressions evaluate to 'true' for the line to be considered a match" 
title="Requires that all user-defined expressions evaluate to 'true' for the 
line to be considered a match"></img></li><li>Route to 'matched' if lines 
matches any condition <img src="../../html/images/iconInfo.png" alt="Requires 
that at least one user-defined expression evaluate to 'true' for the line to be 
considered a match" ti
 tle="Requires that at least one user-defined expression evaluate to 'true' for 
the line to be considered a match"></img></li></ul></td><td 
id="description">Specifies how to determine which Relationship(s) to use when 
evaluating the lines of incoming text against the 'Matching Strategy' and 
user-defined properties.</td></tr><tr><td id="name"><strong>Matching 
Strategy</strong></td><td id="default-value"></td><td 
id="allowable-values"><ul><li>Starts With <img 
src="../../html/images/iconInfo.png" alt="Match lines based on whether the line 
starts with the property value" title="Match lines based on whether the line 
starts with the property value"></img></li><li>Ends With <img 
src="../../html/images/iconInfo.png" alt="Match lines based on whether the line 
ends with the property value" title="Match lines based on whether the line ends 
with the property value"></img></li><li>Contains <img 
src="../../html/images/iconInfo.png" alt="Match lines based on whether the line 
contains the property v
 alue" title="Match lines based on whether the line contains the property 
value"></img></li><li>Equals <img src="../../html/images/iconInfo.png" 
alt="Match lines based on whether the line equals the property value" 
title="Match lines based on whether the line equals the property 
value"></img></li><li>Matches Regular Expression <img 
src="../../html/images/iconInfo.png" alt="Match lines based on whether the line 
exactly matches the Regular Expression that is provided as the Property value" 
title="Match lines based on whether the line exactly matches the Regular 
Expression that is provided as the Property value"></img></li><li>Contains 
Regular Expression <img src="../../html/images/iconInfo.png" alt="Match lines 
based on whether the line contains some text that matches the Regular 
Expression that is provided as the Property value" title="Match lines based on 
whether the line contains some text that matches the Regular Expression that is 
provided as the Property value"></img></li></ul></
 td><td id="description">Specifies how to evaluate each line of incoming text 
against the user-defined properties.</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">The Character Set in which the incoming text is 
encoded</td></tr><tr><td id="name"><strong>Ignore Leading/Trailing 
Whitespace</strong></td><td id="default-value">true</td><td 
id="allowable-values"></td><td id="description">Indicates whether or not the 
whitespace at the beginning and end of the lines should be ignored when 
evaluating the line.</td></tr><tr><td id="name"><strong>Ignore 
Case</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, capitalization will not be taken into account when 
comparing values. E.g., matching against 'HELLO' or 'hello' will have the same 
result.</td></tr><tr><td id="name">Grouping Regular Expression</td><td 
 id="default-value"></td><td id="allowable-values"></td><td 
id="description">Specifies a Regular Expression to evaluate against each line 
to determine which Group the line should be placed in. The Regular Expression 
must have at least one Capturing Group that defines the line's Group. If 
multiple Capturing Groups exist in the Regular Expression, the Group from all 
Capturing Groups. Two lines will not be placed into the same FlowFile unless 
the they both have the same value for the Group (or neither line matches the 
Regular Expression). For example, to group together all lines in a CSV File by 
the first column, we can set this value to "(.*?),.*". Two lines that have the 
same Group but different Relationships will never be placed into the same 
FlowFile.</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
 ">Relationship Name</td><td id="value">value to match against</td><td>Routes 
data that matches the value specified in the Dynamic Property Value to the 
Relationship specified in the Dynamic Property 
Key.</td></tr></table></p><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>original</td><td>The
 original input file will be routed to this destination when the lines have 
been successfully routed to 1 or more 
relationships</td></tr><tr><td>unmatched</td><td>Data that does not satisfy the 
required user-defined rules will be routed to this 
Relationship</td></tr></table><h3>Dynamic Relationships: </h3><p>A Dynamic 
Relationship may be created based on how the user configures the 
Processor.<table 
id="dynamic-relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>Name
 from Dynamic Property</td><td>FlowFiles that match the Dynamic Property's 
value</td></tr></table></p><h3>Reads Attributes: </h3>None specified.<h3>Writes 
Attributes: </
 h3>None specified.</body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>RouteText</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Routes textual 
data based on a set of user-defined rules. Each line in an incoming FlowFile is 
compared against the values specified by user-defined Properties. The mechanism 
by which the text is compared to these user-defined properties is defined by 
the 'Matching Strategy'. The data is then routed according to these rules, 
routing each line of the text individually.</p><h3>Tags: </h3><p>attributes, 
routing, text, regexp, regex, Regular Expression, Expression Language, csv, 
filter, logs, delimited</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.</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>Routing Strategy</strong></td><td id="default-value">Route to 
each matching Property Name</td><td id="allowable-values"><ul><li>Route to each 
matching Property Name <img src="../../html/images/iconInfo.png" alt="Lines 
will be routed to each relationship whose corresponding expression evaluates to 
'true'" title="Lines will be routed to each relationship whose corresponding 
expression evaluates to 'true'"></img></li><li>Route to 'matched' if line 
matches all conditions <img src="../../html/images/iconInfo.png" alt="Requires 
that all user-defined expressions evaluate to 'true' for the line to be 
considered a match" title="Requires that all user-defined expressions evaluate 
to 'true' for the line to be considered a match"></img></li><li>Route to 
'matched' if lines matches any condition <img 
src="../../html/images/iconInfo.png" alt="Requires that at least one 
user-defined expression evaluate to 'true' for the lin
 e to be considered a match" title="Requires that at least one user-defined 
expression evaluate to 'true' for the line to be considered a 
match"></img></li></ul></td><td id="description">Specifies how to determine 
which Relationship(s) to use when evaluating the lines of incoming text against 
the 'Matching Strategy' and user-defined properties.</td></tr><tr><td 
id="name"><strong>Matching Strategy</strong></td><td 
id="default-value"></td><td id="allowable-values"><ul><li>Satisfies Expression 
<img src="../../html/images/iconInfo.png" alt="Match lines based on whether or 
not the the text satisfies the given Expression Language expression. I.e., the 
line will match if the property value, evaluated as an Expression, returns 
true. The expression is able to reference FlowFile Attributes, as well as the 
variables 'line' (which is the text of the line to evaluate) and 'lineNo' 
(which is the line number being evaluated. This will be 1 for the first line, 2 
for the second and so on)." title="Ma
 tch lines based on whether or not the the text satisfies the given Expression 
Language expression. I.e., the line will match if the property value, evaluated 
as an Expression, returns true. The expression is able to reference FlowFile 
Attributes, as well as the variables 'line' (which is the text of the line to 
evaluate) and 'lineNo' (which is the line number being evaluated. This will be 
1 for the first line, 2 for the second and so on)."></img></li><li>Starts With 
<img src="../../html/images/iconInfo.png" alt="Match lines based on whether the 
line starts with the property value" title="Match lines based on whether the 
line starts with the property value"></img></li><li>Ends With <img 
src="../../html/images/iconInfo.png" alt="Match lines based on whether the line 
ends with the property value" title="Match lines based on whether the line ends 
with the property value"></img></li><li>Contains <img 
src="../../html/images/iconInfo.png" alt="Match lines based on whether the line 
contains
  the property value" title="Match lines based on whether the line contains the 
property value"></img></li><li>Equals <img src="../../html/images/iconInfo.png" 
alt="Match lines based on whether the line equals the property value" 
title="Match lines based on whether the line equals the property 
value"></img></li><li>Matches Regular Expression <img 
src="../../html/images/iconInfo.png" alt="Match lines based on whether the line 
exactly matches the Regular Expression that is provided as the Property value" 
title="Match lines based on whether the line exactly matches the Regular 
Expression that is provided as the Property value"></img></li><li>Contains 
Regular Expression <img src="../../html/images/iconInfo.png" alt="Match lines 
based on whether the line contains some text that matches the Regular 
Expression that is provided as the Property value" title="Match lines based on 
whether the line contains some text that matches the Regular Expression that is 
provided as the Property value"></i
 mg></li></ul></td><td id="description">Specifies how to evaluate each line of 
incoming text against the user-defined properties.</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">The Character Set in which the incoming text is 
encoded</td></tr><tr><td id="name"><strong>Ignore Leading/Trailing 
Whitespace</strong></td><td id="default-value">true</td><td 
id="allowable-values"></td><td id="description">Indicates whether or not the 
whitespace at the beginning and end of the lines should be ignored when 
evaluating the line.</td></tr><tr><td id="name"><strong>Ignore 
Case</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, capitalization will not be taken into account when 
comparing values. E.g., matching against 'HELLO' or 'hello' will have the same 
result. This property is ignored if the 'Matching Strate
 gy' is set to 'Satisfies Expression'.</td></tr><tr><td id="name">Grouping 
Regular Expression</td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Specifies a Regular Expression 
to evaluate against each line to determine which Group the line should be 
placed in. The Regular Expression must have at least one Capturing Group that 
defines the line's Group. If multiple Capturing Groups exist in the Regular 
Expression, the Group from all Capturing Groups. Two lines will not be placed 
into the same FlowFile unless the they both have the same value for the Group 
(or neither line matches the Regular Expression). For example, to group 
together all lines in a CSV File by the first column, we can set this value to 
"(.*?),.*". Two lines that have the same Group but different Relationships will 
never be placed into the same FlowFile.</td></tr></table><h3>Dynamic 
Properties: </h3><p>Dynamic Properties allow the user to specify both the name 
and value of a property.<t
 able 
id="dynamic-properties"><tr><th>Name</th><th>Value</th><th>Description</th></tr><tr><td
 id="name">Relationship Name</td><td id="value">value to match 
against</td><td>Routes data that matches the value specified in the Dynamic 
Property Value to the Relationship specified in the Dynamic Property 
Key.</td></tr></table></p><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>original</td><td>The
 original input file will be routed to this destination when the lines have 
been successfully routed to 1 or more 
relationships</td></tr><tr><td>unmatched</td><td>Data that does not satisfy the 
required user-defined rules will be routed to this 
Relationship</td></tr></table><h3>Dynamic Relationships: </h3><p>A Dynamic 
Relationship may be created based on how the user configures the 
Processor.<table 
id="dynamic-relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>Name
 from Dynamic Property</td><td>FlowFiles that match the Dynamic Prop
 erty's value</td></tr></table></p><h3>Reads Attributes: </h3>None 
specified.<h3>Writes Attributes: </h3>None specified.</body></html>
\ No newline at end of file

Modified: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.SplitText/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.SplitText/index.html?rev=1736720&r1=1736719&r2=1736720&view=diff
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.SplitText/index.html
 (original)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.processors.standard.SplitText/index.html
 Sun Mar 27 04:51:17 2016
@@ -1 +1,2 @@
-<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>SplitText</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Splits a text file 
into multiple smaller text files on line boundaries, each having up to a 
configured number of lines</p><h3>Tags: </h3><p>split, text</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.</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>Line Split 
Count</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The number of lines that will 
be added to each split file</td></tr><tr><td id="name"><strong>Header Line 
Count</strong></td><td id="default-value">0</td><td id="allow
 able-values"></td><td id="description">The number of lines that should be 
considered part of the header; the header lines will be duplicated to all split 
files</td></tr><tr><td id="name"><strong>Remove Trailing 
Newlines</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 to remove newlines at the end of each split file. This 
should be false if you intend to merge the split files 
later</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>failure</td><td>If
 a file cannot be split for some reason, the original file will be routed to 
this destination and nothing will be routed 
elsewhere</td></tr><tr><td>original</td><td>The original input file will be 
routed to this destination when it has been successfully split into 1 or more 
files</td></tr><tr><td>splits</td><td>The split files will be routed to this 
destination when an input file is
  successfully split into 1 or more split files</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>text.line.count</td><td>The
 number of lines of text from the original FlowFile that were copied to this 
FlowFile</td></tr><tr><td>fragment.identifier</td><td>All split FlowFiles 
produced from the same parent FlowFile will have the same randomly generated 
UUID added for this attribute</td></tr><tr><td>fragment.index</td><td>A one-up 
number that indicates the ordering of the split FlowFiles that were created 
from a single parent FlowFile</td></tr><tr><td>fragment.count</td><td>The 
number of split FlowFiles generated from the parent 
FlowFile</td></tr><tr><td>segment.original.filename </td><td>The filename of 
the parent FlowFile</td></tr></table><h3>See Also:</h3><p><a 
href="../org.apache.nifi.processors.standard.MergeContent/index.html">MergeContent</a></p></body></html>
\ No newline at end of file
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>SplitText</title><link rel="stylesheet" 
href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>Splits a text file 
into multiple smaller text files on line boundaries, each having up to a 
configured number of lines.</p><h3>Tags: </h3><p>split, text</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.</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>Line Split 
Count</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The number of lines that will 
be added to each split file (excluding the header, if the Header Line Count 
property is greater than 0).</td></tr><tr><td id="name"><st
 rong>Header Line Count</strong></td><td id="default-value">0</td><td 
id="allowable-values"></td><td id="description">The number of lines that should 
be considered part of the header; the header lines will be duplicated to all 
split files</td></tr><tr><td id="name"><strong>Remove Trailing 
Newlines</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 to remove newlines at the end of each split file. This 
should be false if you intend to merge the split files later. If this is set to 
'true' and a FlowFile is generated that contains only 'empty lines' (i.e., 
consists only of 
 and 
+ characters), the FlowFile will not be emitted. Note, however, that if the 
Header Line Count is greater than 0, the resultant FlowFile will never be empty 
as it will consist of the header lines, so a FlowFile may be emitted that 
contians only the header lines.</td></tr></table><h3>Relationships: </h3><table 
id="relationships"><tr><th>Name</th><th>Description</th></tr><tr><td>failure</td><td>If
 a file cannot be split for some reason, the original file will be routed to 
this destination and nothing will be routed 
elsewhere</td></tr><tr><td>original</td><td>The original input file will be 
routed to this destination when it has been successfully split into 1 or more 
files</td></tr><tr><td>splits</td><td>The split files will be routed to this 
destination when an input file is successfully split into 1 or more split 
files</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>te
 xt.line.count</td><td>The number of lines of text from the original FlowFile 
that were copied to this 
FlowFile</td></tr><tr><td>fragment.identifier</td><td>All split FlowFiles 
produced from the same parent FlowFile will have the same randomly generated 
UUID added for this attribute</td></tr><tr><td>fragment.index</td><td>A one-up 
number that indicates the ordering of the split FlowFiles that were created 
from a single parent FlowFile</td></tr><tr><td>fragment.count</td><td>The 
number of split FlowFiles generated from the parent 
FlowFile</td></tr><tr><td>segment.original.filename </td><td>The filename of 
the parent FlowFile</td></tr></table><h3>See Also:</h3><p><a 
href="../org.apache.nifi.processors.standard.MergeContent/index.html">MergeContent</a></p></body></html>
\ No newline at end of file

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.spring.SpringContextProcessor/additionalDetails.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.spring.SpringContextProcessor/additionalDetails.html?rev=1736720&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.spring.SpringContextProcessor/additionalDetails.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.spring.SpringContextProcessor/additionalDetails.html
 Sun Mar 27 04:51:17 2016
@@ -0,0 +1,94 @@
+<!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>SpringContextProcessor</title>
+        <link rel="stylesheet" href="../../css/component-usage.css" 
type="text/css" />
+    </head>
+
+    <body>
+        <!-- Processor Documentation 
================================================== -->
+        <h2>Description:</h2>
+        <p>
+            <b>SpringContextProcessor</b> – allows integration of processes 
encapsulated in Spring Application Context to run as NiFi
+            processor by becoming a runtime host for an instance of Spring 
Application Context.
+        </p>
+        <p>
+            Communication between NiFi and process encapsulated within Spring 
Application Context is accomplished via Spring Messaging
+            (one of the core modules of Spring Framework) and supports 3 usage 
modes:
+            <ul>
+                <li><i>Headless</i> - no interaction with NiFi, meaning 
nothing is sent to it and nothing is received from it (i.e., some monitoring 
app).
+                In this case NiFi simply plays the role of the runtime 
host.</li>
+                <li><i>One way (NiFi -&gt; Spring or Spring -&gt; NiFi). </i> 
- This depends on existence of pre-defined message channel in Spring
+                Application Context. The name of the channel should be 
“fromNiFi” and the type 
<i>org.springframework.messaging.MessageChannel.</i></li>
+                <li><i>By-directional (NiFi -&gt; Spring -&gt; Nifi or Spring 
-&gt; NiFi -&gt; Spring)</i> - This depends on existence of two channels
+                in Spring Application Context. One channel receives messages 
from NiFi with name “fromNiFi” and type 
<i>org.springframework.messaging.MessageChannel</i>i>
+                and another is to receive messages from Spring with name 
“toNiFi” and type <i>org.springframework.messaging.PollableChannel.</i></li>
+            </ul>
+            The example below demonstrates template configuration for 
bi-directional Spring Application Context configuration:
+            <code>
+            <pre>
+    &lt;int:channel id=”fromNiFi”/&gt;
+
+    &lt;!—
+    your custom app configuration to receive messages from ‘fromNiFi’ 
channel and optionally send back to NiFi via ‘toNiFi’ channel.
+    It could contain any Spring-based application (i.e., Spring Integration, 
Apache Camel and/or custom code). All you need to do is inject
+    channels into your beans and send/receive messages from it.
+    --&gt;
+
+    &lt;int:channel id="toNiFi"&gt;
+        &lt;int:queue/&gt;
+    &lt;/int:channel&gt;
+            </pre>
+            </code>
+        </p>
+        <p>
+        The component is based on assumption that user has an existing Spring 
Application encapsulated in Spring Context that exposes optional in/out
+        MessagingChannels to allow data to flow to/from ApplicationContext and 
into/out-of. NiFi.
+        Such application is realized by having a directory on the file system, 
which contains contains all required resources for such application to run.
+        Such resources usually are JAR files to satisfy application's 
class-path as well as JAR representing the application and its configuration.
+        Below is the example of what such directory may contain. In this case 
the 'SI_DEMO-0.0.1-SNAPSHOT.jar' represents the actual application and the rest
+        of the JARs represent class-path dependency required by an application.
+        <pre>
+        deps
+         ├── SI_DEMO-0.0.1-SNAPSHOT.jar
+         ├── aopalliance-1.0.jar
+         ├── commons-logging-1.2.jar
+         ├── spring-aop-4.2.4.RELEASE.jar
+         ├── spring-beans-4.2.4.RELEASE.jar
+         ├── spring-context-4.2.4.RELEASE.jar
+         ├── spring-core-4.2.4.RELEASE.jar
+         ├── spring-expression-4.2.4.RELEASE.jar
+         ├── spring-integration-core-4.2.5.RELEASE.jar
+         ├── spring-messaging-4.2.4.RELEASE.jar
+        </pre>
+        </p>
+        <p>
+        You introduce the processor the usual way and then configure its 
properties:
+        <ul>
+        <li><i><b>Application Context config path</b></i> [REQUIRED] - a path 
to the Application Context configuration.
+        The path is relative to the class-path of the application defined by 
the <i>Application Context class path</i> property </li>
+        <li><i><b>Application Context class path</b></i> [REQUIRED] - a path 
to a directory on the file system where application dependencies are. </li>
+        <li><i>Send Timeout</i> [OPTIONAL] - the wait time for sending 
messages to Spring Application Context. Only required if NiFi plans to send 
data to Spring.
+        Defaults to 0 (don't wait). FlowFiles that were successfully sent to 
Spring will be removed from session while FlowFiles that could not be sent to
+        Spring will be routed to <i>failure</i> relationship.</li>
+        <li><i>Receive Timeout</i> - [OPTIONAL] - the wait time for receiving 
messages from Spring Application Context. Only required if NiFi plans to 
receive data from Spring.
+        Defaults to 0 (don't wait). FlowFile is created if and only if a 
message is successfully received from Spring. It is then transfered to 
<i>success</i> relationship.</li>
+        </ul>
+        </p>
+    </body>
+</html>

Added: 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.spring.SpringContextProcessor/index.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.spring.SpringContextProcessor/index.html?rev=1736720&view=auto
==============================================================================
--- 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.spring.SpringContextProcessor/index.html
 (added)
+++ 
nifi/site/trunk/docs/nifi-docs/components/org.apache.nifi.spring.SpringContextProcessor/index.html
 Sun Mar 27 04:51:17 2016
@@ -0,0 +1 @@
+<!DOCTYPE html><html lang="en"><head><meta 
charset="utf-8"></meta><title>SpringContextProcessor</title><link 
rel="stylesheet" href="../../css/component-usage.css" 
type="text/css"></link></head><body><h2>Description: </h2><p>A Processor that 
supports sending and receiving data from application defined in Spring 
Application Context via predefined in/out MessageChannels.</p><p><a 
href="additionalDetails.html">Additional Details...</a></p><h3>Tags: 
</h3><p>Spring, Message, Get, Put, Integration</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.</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>Application 
Context config path</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">The path to the Sp
 ring Application Context configuration file relative to the 
classpath</td></tr><tr><td id="name"><strong>Application Context class 
path</strong></td><td id="default-value"></td><td 
id="allowable-values"></td><td id="description">Path to the directory with 
resources (i.e., JARs, configuration files etc.) required to be on the 
classpath of the ApplicationContext.</td></tr><tr><td id="name">Send 
Timeout</td><td id="default-value"></td><td id="allowable-values"></td><td 
id="description">Timeout for sending data to Spring Application Context. 
Defaults to 0.</td></tr><tr><td id="name">Receive Timeout</td><td 
id="default-value"></td><td id="allowable-values"></td><td 
id="description">Timeout for receiving date from Spring context. Defaults to 
0.</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 successfully received from Spring Application Context are 
routed to this relationship</td></
 tr><tr><td>failure</td><td>All FlowFiles that cannot be sent to Spring 
Application Context are routed to this relationship</td></tr></table><h3>Reads 
Attributes: </h3>None specified.<h3>Writes Attributes: </h3>None 
specified.</body></html>
\ No newline at end of file

Modified: nifi/site/trunk/docs/nifi-docs/html/administration-guide.html
URL: 
http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/html/administration-guide.html?rev=1736720&r1=1736719&r2=1736720&view=diff
==============================================================================
--- nifi/site/trunk/docs/nifi-docs/html/administration-guide.html (original)
+++ nifi/site/trunk/docs/nifi-docs/html/administration-guide.html Sun Mar 27 
04:51:17 2016
@@ -443,7 +443,12 @@ body.book #toc,body.book #preamble,body.
 <li><a href="#how-to-install-and-start-nifi">How to install and start 
NiFi</a></li>
 <li><a href="#configuration-best-practices">Configuration Best 
Practices</a></li>
 <li><a href="#security-configuration">Security Configuration</a></li>
-<li><a href="#user-authentication">User Authentication</a></li>
+<li><a href="#user-authentication">User Authentication</a>
+<ul class="sectlevel2">
+<li><a href="#lightweight-directory-access-protocol-ldap">Lightweight 
Directory Access Protocol (LDAP)</a></li>
+<li><a href="#kerberos_login_identity_provider">Kerberos</a></li>
+</ul>
+</li>
 <li><a href="#controlling-levels-of-access">Controlling Levels of 
Access</a></li>
 <li><a href="#encryption">Encryption Configuration</a>
 <ul class="sectlevel2">
@@ -464,6 +469,11 @@ body.book #toc,body.book #preamble,body.
 </li>
 <li><a href="#bootstrap_properties">Bootstrap Properties</a></li>
 <li><a href="#notification_services">Notification Services</a></li>
+<li><a href="#kerberos_service">Kerberos Service</a>
+<ul class="sectlevel2">
+<li><a href="#kerberos_service_notes">Notes</a></li>
+</ul>
+</li>
 <li><a href="#system_properties">System Properties</a></li>
 </ul>
 </div>
@@ -880,6 +890,8 @@ explicity enabled.</p>
 <div class="paragraph">
 <p>NiFi does not perform user authentication over HTTP. Using HTTP all users 
will be granted all roles.</p>
 </div>
+<div class="sect2">
+<h3 id="lightweight-directory-access-protocol-ldap"><a class="anchor" 
href="#lightweight-directory-access-protocol-ldap"></a>Lightweight Directory 
Access Protocol (LDAP)</h3>
 <div class="paragraph">
 <p>Below is an example and description of configuring a Login Identity 
Provider that integrates with a Directory Server to authenticate users.</p>
 </div>
@@ -1016,6 +1028,63 @@ explicity enabled.</p>
 </tbody>
 </table>
 </div>
+<div class="sect2">
+<h3 id="kerberos_login_identity_provider"><a class="anchor" 
href="#kerberos_login_identity_provider"></a>Kerberos</h3>
+<div class="paragraph">
+<p>Below is an example and description of configuring a Login Identity 
Provider that integrates with a Kerberos Key Distribution Center (KDC) to 
authenticate users.</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>&lt;provider&gt;
+    &lt;identifier&gt;kerberos-provider&lt;/identifier&gt;
+    &lt;class&gt;org.apache.nifi.kerberos.KerberosProvider&lt;/class&gt;
+    &lt;property name="Default Realm"&gt;NIFI.APACHE.ORG&lt;/property&gt;
+    &lt;property name="Kerberos Config File"&gt;/etc/krb5.conf&lt;/property&gt;
+    &lt;property name="Authentication Expiration"&gt;12 hours&lt;/property&gt;
+&lt;/provider&gt;</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>With this configuration, username/password authentication can be enabled by 
referencing this provider in <em>nifi.properties</em>.</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>nifi.security.user.login.identity.provider=kerberos-provider</pre>
+</div>
+</div>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 50%;">
+<col style="width: 50%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Property Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+</tr>
+</thead>
+<tfoot>
+<tr>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>Authentication Expiration</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The 
duration of how long the user authentication is valid for. If the user never 
logs out, they will be required to log back in following this duration.</p></td>
+</tr>
+</tfoot>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>Default Realm</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Default 
realm to provide when user enters incomplete user principal (i.e. 
NIFI.APACHE.ORG).</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock"><code>Kerberos Config File</code></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Absolute 
path to Kerberos client configuration file.</p></td>
+</tr>
+</tbody>
+</table>
+<div class="paragraph">
+<p>See also <a href="#kerberos_service">Kerberos Service</a> to allow single 
sign-on access via client Kerberos tickets.</p>
+</div>
+</div>
+</div>
 </div>
 <div class="sect1">
 <h2 id="controlling-levels-of-access"><a class="anchor" 
href="#controlling-levels-of-access"></a>Controlling Levels of Access</h2>
@@ -1069,7 +1138,7 @@ in place of "user dn - read only and adm
 </div>
 </div>
 <div class="paragraph">
-<p>Here is an example entry using the name John Smith:</p>
+<p>Here is an LDAP example entry using the name John Smith:</p>
 </div>
 <div class="listingblock">
 <div class="content">
@@ -1081,6 +1150,18 @@ in place of "user dn - read only and adm
 </div>
 </div>
 <div class="paragraph">
+<p>Here is a Kerberos example entry using the name John Smith and realm 
<code>NIFI.APACHE.ORG</code>:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre>&lt;users&gt;
+    &lt;user dn="johnsm...@nifi.apache.org"&gt;
+        &lt;role name="ROLE_ADMIN"/&gt;
+    &lt;/user&gt;
+&lt;/users&gt;</pre>
+</div>
+</div>
+<div class="paragraph">
 <p>After the <em>authorized-users.xml</em> file has been edited and saved, 
restart NiFi.
 Once the application starts, the ADMIN user is
 able to access the UI at the HTTPS URL that is configured in the 
<em>nifi.properties</em> file.</p>
@@ -2458,6 +2539,94 @@ must be set.</p>
 </div>
 </div>
 <div class="sect1">
+<h2 id="kerberos_service"><a class="anchor" 
href="#kerberos_service"></a>Kerberos Service</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>NiFi can be configured to use Kerberos SPNEGO (or "Kerberos Service") for 
authentication. In this scenario, users will hit the REST endpoint 
<code>/access/kerberos</code> and the server will respond with a 
<code>401</code> status code and the challenge response header 
<code>WWW-Authenticate: Negotiate</code>. This communicates to the browser to 
use the GSS-API and load the user&#8217;s Kerberos ticket and provide it as a 
Base64-encoded header value in the subsequent request. It will be of the form 
<code>Authorization: Negotiate YII...</code>. NiFi will attempt to validate 
this ticket with the KDC. If it is successful, the user&#8217;s 
<em>principal</em> will be returned as the identity, and the flow will follow 
login/credential authentication, in that a JWT will be issued in the response 
to prevent the unnecessary overhead of Kerberos authentication on every 
subsequent request. If the ticket cannot be validated, it will return with the 
appropriate error response code. The user wi
 ll then be able to provide their Kerberos credentials to the login form if the 
<code>KerberosLoginIdentityProvider</code> has been configured. See <a 
href="#kerberos_login_identity_provider">Kerberos</a> login identity provider 
for more details.</p>
+</div>
+<div class="paragraph">
+<p>NiFi will only respond to Kerberos SPNEGO negotiation over an HTTPS 
connection, as unsecured requests are never authenticated.</p>
+</div>
+<div class="paragraph">
+<p>The following properties must be set in <em>nifi.properties</em> to enable 
Kerberos service authentication.</p>
+</div>
+<table class="tableblock frame-all grid-all spread">
+<colgroup>
+<col style="width: 33%;">
+<col style="width: 33%;">
+<col style="width: 33%;">
+</colgroup>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock"><strong>Property</strong></p></td>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock"><strong>Required</strong></p></td>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock"><strong>Description</strong></p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Service 
Principal</p></td>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The 
service principal used by NiFi to communicate with the KDC</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Keytab 
Location</p></td>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock">true</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The file 
path to the keytab containing the service principal</p></td>
+</tr>
+</tbody>
+</table>
+<div class="paragraph">
+<p>See <a href="#kerberos_properties">[kerberos_properties]</a> for complete 
documentation.</p>
+</div>
+<div class="sect2">
+<h3 id="kerberos_service_notes"><a class="anchor" 
href="#kerberos_service_notes"></a>Notes</h3>
+<div class="ulist">
+<ul>
+<li>
+<p>Kerberos is case-sensitive in many places and the error messages (or lack 
thereof) may not be sufficiently explanatory. Check the case sensitivity of the 
service principal in your configuration files. Convention is 
<code>HTTP/fully.qualified.domain@REALM</code>.</p>
+</li>
+<li>
+<p>Browsers have varying levels of restriction when dealing with SPNEGO 
negotiations. Some will provide the local Kerberos ticket to any domain that 
requests it, while others whitelist the trusted domains. See <a 
href="http://docs.spring.io/autorepo/docs/spring-security-kerberos/1.0.2.BUILD-SNAPSHOT/reference/htmlsingle/#browserspnegoconfig";>Spring
 Security Kerberos - Reference Documentation: Appendix E. Configure browsers 
for SPNEGO Negotiation</a> for common browsers.</p>
+</li>
+<li>
+<p>Some browsers (legacy IE) do not support recent encryption algorithms such 
as AES, and are restricted to legacy algorithms (DES). This should be noted 
when generating keytabs.</p>
+</li>
+<li>
+<p>The KDC must be configured and a service principal defined for NiFi and a 
keytab exported. Comprehensive instructions for Kerberos server configuration 
and administration are beyond the scope of this document (see <a 
href="http://web.mit.edu/kerberos/krb5-current/doc/admin/index.html";>MIT 
Kerberos Admin Guide</a>), but an example is below:</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>Adding a service principal for a server at 
<code>nifi.nifi.apache.org</code> and exporting the keytab from the KDC:</p>
+</div>
+<div class="literalblock">
+<div class="content">
+<pre>root@kdc:/etc/krb5kdc# kadmin.local
+Authenticating as principal admin/ad...@nifi.apache.org with password.
+kadmin.local:  listprincs
+K/m...@nifi.apache.org
+admin/ad...@nifi.apache.org
+...
+kadmin.local:  addprinc -randkey HTTP/nifi.nifi.apache.org
+WARNING: no policy specified for HTTP/nifi.nifi.apache....@nifi.apache.org; 
defaulting to no policy
+Principal "HTTP/nifi.nifi.apache....@nifi.apache.org" created.
+kadmin.local:  ktadd -k /http-nifi.keytab HTTP/nifi.nifi.apache.org
+Entry for principal HTTP/nifi.nifi.apache.org with kvno 2, encryption type 
des3-cbc-sha1 added to keytab WRFILE:/http-nifi.keytab.
+Entry for principal HTTP/nifi.nifi.apache.org with kvno 2, encryption type 
des-cbc-crc added to keytab WRFILE:/http-nifi.keytab.
+kadmin.local:  listprincs
+HTTP/nifi.nifi.apache....@nifi.apache.org
+K/m...@nifi.apache.org
+admin/ad...@nifi.apache.org
+...
+kadmin.local: q
+root@kdc:~# ll /http*
+-rw------- 1 root root 162 Mar 14 21:43 /http-nifi.keytab
+root@kdc:~#</pre>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
 <h2 id="system_properties"><a class="anchor" 
href="#system_properties"></a>System Properties</h2>
 <div class="sectionbody">
 <div class="paragraph">
@@ -2551,7 +2720,16 @@ only consider if <code>nifi.security.use
 </tr>
 <tr>
 <td class="tableblock halign-left valign-top"><p 
class="tableblock">nifi.nar.library.directory</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">The 
location of the nar library. The default value is ./lib and probably should be 
left as is.</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The 
location of the nar library. The default value is ./lib and probably should be 
left as is.<br>
+<br>
+<strong>NOTE</strong>: Additional library directories can be specified by 
using the <strong><em>nifi.nar.library.directory.</em></strong> prefix with 
unique suffixes and separate paths as values.<br>
+<br>
+For example, to provide two additional library locations, a user could also 
specify additional properties with keys of:<br>
+<br>
+nifi.nar.library.directory.lib1=/nars/lib1<br>
+nifi.nar.library.directory.lib2=/nars/lib2<br>
+<br>
+Providing three total locations, including  
<em>nifi.nar.library.directory</em>.</p></td>
 </tr>
 <tr>
 <td class="tableblock halign-left valign-top"><p 
class="tableblock">nifi.nar.working.directory</p></td>
@@ -2561,6 +2739,10 @@ only consider if <code>nifi.security.use
 <td class="tableblock halign-left valign-top"><p 
class="tableblock">nifi.documentation.working.directory</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">The 
documentation working directory. The default value is ./work/docs/components 
and probably should be left as is.</p></td>
 </tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock">nifi.processor.scheduling.timeout</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Time to 
wait for a Processor&#8217;s life-cycle operation (@OnScheduled and 
@OnUnscheduled) to finish before other life-cycle operation (e.g., stop) could 
be invoked. Default is infinite.</p></td>
+</tr>
 </tbody>
 </table>
 <div class="paragraph">
@@ -2839,7 +3021,7 @@ Providing three total locations, includi
 </tr>
 <tr>
 <td class="tableblock halign-left valign-top"><p 
class="tableblock">nifi.provenance.repository.rollover.time</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">The amount 
of time to wait before rolling over the latest data provenance information so 
that it is available in the User Interface. The default value is 5 
mins.</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The amount 
of time to wait before rolling over the latest data provenance information so 
that it is available in the User Interface. The default value is 30 
secs.</p></td>
 </tr>
 <tr>
 <td class="tableblock halign-left valign-top"><p 
class="tableblock">nifi.provenance.repository.rollover.size</p></td>
@@ -3292,8 +3474,8 @@ If multicast is used, the following nifi
 </tr>
 </tbody>
 </table>
-<div class="paragraph">
-<p><strong>Kerberos</strong><br></p>
+<div id="kerberos_properties" class="paragraph">
+<p><strong>Kerberos Properties</strong><br></p>
 </div>
 <table class="tableblock frame-all grid-all spread">
 <colgroup>
@@ -3309,7 +3491,23 @@ If multicast is used, the following nifi
 <td class="tableblock halign-left valign-top"><p 
class="tableblock">nifi.kerberos.krb5.file*</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">The 
location of the krb5 file, if used. It is blank by default. Note that this 
property is not used to authenticate NiFi users.
     Rather, it is made available for extension points, such as Hadoop-based 
Processors, to use. At this time, only a single krb5 file is allowed to
-    be specified per NiFi instance, so this property is configured here rather 
than in individual Processors.</p></td>
+    be specified per NiFi instance, so this property is configured here rather 
than in individual Processors.
+    Example: <code>/etc/krb5.conf</code></p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock">nifi.kerberos.service.principal*</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The name 
of the NiFi Kerberos service principal, if used. It is blank by default. Note 
that this property is used to authenticate NiFi users.
+   Example: <code>HTTP/nifi.example.com</code> or 
<code>HTTP/nifi.example....@example.com</code></p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock">nifi.kerberos.keytab.location*</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The file 
path of the NiFi Kerberos keytab, if used. It is blank by default. Note that 
this property is used to authenticate NiFi users.
+  Example: <code>/etc/http-nifi.keytab</code></p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p 
class="tableblock">nifi.kerberos.authentication.expiration*</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">The 
expiration duration of a successful Kerberos user authentication, if used. It 
is 12 hours by default.
+  Example: <code>12 hours</code></p></td>
 </tr>
 </tbody>
 </table>
@@ -3330,7 +3528,7 @@ If multicast is used, the following nifi
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2016-02-23 18:48:07 EST
+Last updated 2016-03-23 18:55:20 -04:00
 </div>
 </div>
 </body>


Reply via email to