Modified: nifi/site/trunk/docs/nifi-docs/html/user-guide.html URL: http://svn.apache.org/viewvc/nifi/site/trunk/docs/nifi-docs/html/user-guide.html?rev=1719609&r1=1719608&r2=1719609&view=diff ============================================================================== --- nifi/site/trunk/docs/nifi-docs/html/user-guide.html (original) +++ nifi/site/trunk/docs/nifi-docs/html/user-guide.html Sat Dec 12 00:55:22 2015 @@ -455,61 +455,62 @@ body.book #toc,body.book #preamble,body. <div id="toc" class="toc"> <div id="toctitle">Table of Contents</div> <ul class="sectlevel1"> -<li><a href="user-guide.html#introduction">Introduction</a></li> -<li><a href="user-guide.html#terminology">Terminology</a></li> -<li><a href="user-guide.html#User_Interface">NiFi User Interface</a></li> -<li><a href="user-guide.html#building-a-dataflow">Building a DataFlow</a> +<li><a href="#introduction">Introduction</a></li> +<li><a href="#terminology">Terminology</a></li> +<li><a href="#User_Interface">NiFi User Interface</a></li> +<li><a href="#logging-in">Logging In</a></li> +<li><a href="#building-dataflow">Building a DataFlow</a> <ul class="sectlevel2"> -<li><a href="user-guide.html#adding-components-to-the-canvas">Adding Components to the Canvas</a></li> -<li><a href="user-guide.html#configuring-a-processor">Configuring a Processor</a></li> -<li><a href="user-guide.html#additional-help">Additional Help</a></li> -<li><a href="user-guide.html#Controller_Services_and_Reporting_Tasks">Controller Services and Reporting Tasks</a></li> -<li><a href="user-guide.html#connecting-components">Connecting Components</a></li> -<li><a href="user-guide.html#processor-validation">Processor Validation</a></li> -<li><a href="user-guide.html#site-to-site">Site-to-Site</a></li> -<li><a href="user-guide.html#example-dataflow">Example Dataflow</a></li> +<li><a href="#adding-components-to-the-canvas">Adding Components to the Canvas</a></li> +<li><a href="#Configuring_a_Processor">Configuring a Processor</a></li> +<li><a href="#additional-help">Additional Help</a></li> +<li><a href="#Controller_Services_and_Reporting_Tasks">Controller Services and Reporting Tasks</a></li> +<li><a href="#Connecting_Components">Connecting Components</a></li> +<li><a href="#processor-validation">Processor Validation</a></li> +<li><a href="#site-to-site">Site-to-Site</a></li> +<li><a href="#example-dataflow">Example Dataflow</a></li> </ul> </li> -<li><a href="user-guide.html#command-and-control-of-dataflow">Command and Control of DataFlow</a> +<li><a href="#command-and-control-of-the-dataflow">Command and Control of the DataFlow</a> <ul class="sectlevel2"> -<li><a href="user-guide.html#starting-a-component">Starting a Component</a></li> -<li><a href="user-guide.html#stopping-a-component">Stopping a Component</a></li> -<li><a href="user-guide.html#enabling-disabling-a-component">Enabling/Disabling a Component</a></li> -<li><a href="user-guide.html#Remote_Group_Transmission">Remote Process Group Transmission</a></li> +<li><a href="#starting-a-component">Starting a Component</a></li> +<li><a href="#stopping-a-component">Stopping a Component</a></li> +<li><a href="#enabling-disabling-a-component">Enabling/Disabling a Component</a></li> +<li><a href="#Remote_Group_Transmission">Remote Process Group Transmission</a></li> </ul> </li> -<li><a href="user-guide.html#navigating">Navigating within a DataFlow</a></li> -<li><a href="user-guide.html#monitoring">Monitoring of DataFlow</a> +<li><a href="#navigating">Navigating within a DataFlow</a></li> +<li><a href="#monitoring">Monitoring of DataFlow</a> <ul class="sectlevel2"> -<li><a href="user-guide.html#processor_anatomy">Anatomy of a Processor</a></li> -<li><a href="user-guide.html#process_group_anatomy">Anatomy of a Process Group</a></li> -<li><a href="user-guide.html#remote_group_anatomy">Anatomy of a Remote Process Group</a></li> -<li><a href="user-guide.html#Summary_Page">Summary Page</a></li> -<li><a href="user-guide.html#Stats_History">Historical Statistics of a Component</a></li> +<li><a href="#processor_anatomy">Anatomy of a Processor</a></li> +<li><a href="#process_group_anatomy">Anatomy of a Process Group</a></li> +<li><a href="#remote_group_anatomy">Anatomy of a Remote Process Group</a></li> +<li><a href="#Summary_Page">Summary Page</a></li> +<li><a href="#Stats_History">Historical Statistics of a Component</a></li> </ul> </li> -<li><a href="user-guide.html#templates">Templates</a> +<li><a href="#templates">Templates</a> <ul class="sectlevel2"> -<li><a href="user-guide.html#Create_Template">Creating a Template</a></li> -<li><a href="user-guide.html#instantiating-a-template">Instantiating a Template</a></li> -<li><a href="user-guide.html#Manage_Templates">Managing Templates</a></li> +<li><a href="#Create_Template">Creating a Template</a></li> +<li><a href="#instantiating-a-template">Instantiating a Template</a></li> +<li><a href="#Manage_Templates">Managing Templates</a></li> </ul> </li> -<li><a href="user-guide.html#data-provenance">Data Provenance</a> +<li><a href="#data-provenance">Data Provenance</a> <ul class="sectlevel2"> -<li><a href="user-guide.html#searching-for-events">Searching for Events</a></li> -<li><a href="user-guide.html#event_details">Details of an Event</a></li> -<li><a href="user-guide.html#replaying-a-flowfile">Replaying a FlowFile</a></li> -<li><a href="user-guide.html#viewing-flowfile-lineage">Viewing FlowFile Lineage</a></li> +<li><a href="#searching-for-events">Searching for Events</a></li> +<li><a href="#event_details">Details of an Event</a></li> +<li><a href="#replaying-a-flowfile">Replaying a FlowFile</a></li> +<li><a href="#viewing-flowfile-lineage">Viewing FlowFile Lineage</a></li> </ul> </li> -<li><a href="user-guide.html#other_management_features">Other Management Features</a></li> +<li><a href="#other_management_features">Other Management Features</a></li> </ul> </div> </div> <div id="content"> <div class="sect1"> -<h2 id="introduction"><a class="anchor" href="user-guide.html#introduction"></a>Introduction</h2> +<h2 id="introduction"><a class="anchor" href="#introduction"></a>Introduction</h2> <div class="sectionbody"> <div class="paragraph"> <p>Apache NiFi is a dataflow system based on the concepts of flow-based programming. It supports @@ -540,12 +541,12 @@ use a supported web browser to view the </ul> </div> <div class="paragraph"> -<p>Note that there is a known issue in Internet Explorer (IE) 10 and 11 that can cause problems when moving items on the NiFi graph. If you encounter this problem, we suggest using a browser other than IE. This known issue is described here: <a href="https://connect.microsoft.com/IE/Feedback/Details/1050422"; class="bare">https://connect.microsoft.com/IE/Feedback/Details/1050422</a>.</p> +<p>Note that there is a known issue in Internet Explorer (IE) 10 and 11 that can cause problems when moving items on the NiFi canvas. If you encounter this problem, we suggest using a browser other than IE. This known issue is described here: <a href="https://connect.microsoft.com/IE/Feedback/Details/1050422"; class="bare">https://connect.microsoft.com/IE/Feedback/Details/1050422</a>.</p> </div> </div> </div> <div class="sect1"> -<h2 id="terminology"><a class="anchor" href="user-guide.html#terminology"></a>Terminology</h2> +<h2 id="terminology"><a class="anchor" href="#terminology"></a>Terminology</h2> <div class="sectionbody"> <div class="paragraph"> <p><strong>DataFlow Manager</strong>: A DataFlow Manager (DFM) is a NiFi user who has permissions to add, remove, and modify components of a NiFi dataflow.</p> @@ -625,10 +626,16 @@ use a supported web browser to view the As a result, several components may be combined together to make a larger building block from which to create a dataflow. These templates can also be exported as XML and imported into another NiFi instance, allowing these building blocks to be shared.</p> </div> +<div class="paragraph"> +<p><strong>flow.xml.gz</strong>: Everything the DFM puts onto the NiFi User Interface canvas is written, in real time, to one file called the flow.xml.gz. This file is located in the nifi/conf directory. + Any change made on the canvas is automatically saved to this file, without the user needing to click a "save" button. In addition, the user may create a back-up copy of this file at any time + by selecting the Controller Settings button in the far-right section of the tool bar and clicking "Back-up flow" on the General tab. By default, this action saves a copy of the current flow in the nifi/conf/archive directory. + See <a href="#Controller_Settings">Controller Settings</a> for a description of where the "Back-up flow" button may be found. (Note that in a NiFi Cluster, the NiFi Cluster Manager’s copy of this file is named flow.tar, whereas this file is still named flow.xml.gz on the nodes.)</p> +</div> </div> </div> <div class="sect1"> -<h2 id="User_Interface"><a class="anchor" href="user-guide.html#User_Interface"></a>NiFi User Interface</h2> +<h2 id="User_Interface"><a class="anchor" href="#User_Interface"></a>NiFi User Interface</h2> <div class="sectionbody"> <div class="paragraph"> <p>The NiFi User Interface (UI) provides mechanisms for creating automated dataflows, as well as visualizing, @@ -647,7 +654,7 @@ able to view and modify the dataflow. Fo </div> <div class="imageblock"> <div class="content"> -<img src="images/new-flow.png" alt="Empty Flow"> +<img src="./images/new-flow.png" alt="Empty Flow"> </div> </div> <div class="paragraph"> @@ -656,8 +663,8 @@ To the left is the Components Toolbar. T </div> <div class="paragraph"> <p>Next to the Components Toolbar is the Actions Toolbar. This toolbar consists of buttons to manipulate the existing -components on the graph. To the right of the Actions Toolbar is the Search Toolbar. This toolbar consists of a single -Search field that allows users to easily find components on the graph. Users are able to search by component name, +components on the canvas. To the right of the Actions Toolbar is the Search Toolbar. This toolbar consists of a single +Search field that allows users to easily find components on the canvas. Users are able to search by component name, type, identifier, configuration properties, and their values.</p> </div> <div class="paragraph"> @@ -667,12 +674,12 @@ and configure system properties, such as </div> <div class="imageblock"> <div class="content"> -<img src="images/nifi-toolbar-components.png" alt="NiFi Components Toolbar"> +<img src="./images/nifi-toolbar-components.png" alt="NiFi Components Toolbar"> </div> </div> <div class="paragraph"> -<p>Next, we have segments that provide capabilities to easily navigate around the graph. On the left-hand side is a toolbar that -provides the ability to pan around the graph and zoom in and out. On the right-hand side is a âBirds-Eye Viewâ of the dataflow. +<p>Next, we have segments that provide capabilities to easily navigate around the canvas. On the left-hand side is a toolbar that +provides the ability to pan around the canvas and zoom in and out. On the right-hand side is a âBirds-Eye Viewâ of the dataflow. This provides a high-level view of the dataflow and allows the user to quickly and easily pan across large portions of the dataflow. Along the top of the screen is a trail of breadcrumbs. As users navigate into and out of Process Groups, the breadcrumbs show the depth in the flow and each Process Group that was entered to reach this depth. Each of the Process Groups listed in the breadcrumbs @@ -680,12 +687,12 @@ is a link that will take you back up to </div> <div class="imageblock"> <div class="content"> -<img src="images/nifi-navigation.png" alt="NiFi Navigation"> +<img src="./images/nifi-navigation.png" alt="NiFi Navigation"> </div> </div> <div id="status_bar" class="paragraph"> -<p>Below the breadcrumbs lives the Status bar. The Status bar provides information about how many Processors exist in the graph in -each state (Stopped, Running, Invalid, Disabled), how many Remote Process Groups exist on the graph in each state +<p>Below the breadcrumbs lives the Status bar. The Status bar provides information about how many Processors exist on the canvas in +each state (Stopped, Running, Invalid, Disabled), how many Remote Process Groups exist on the canvas in each state (Transmitting, Not Transmitting), the number of threads that are currently active in the flow, the amount of data that currently exists in the flow, and the timestamp at which all of this information was last refreshed. If there are any System-Level bulletins, these are shown in the Status bar as well. Additionally, if the instance of NiFi is clustered, the Status bar shows how many nodes @@ -693,39 +700,80 @@ are in the cluster and how many are curr </div> <div class="imageblock"> <div class="content"> -<img src="images/status-bar.png" alt="NiFi Status Bar"> +<img src="./images/status-bar.png" alt="NiFi Status Bar"> </div> </div> </div> </div> <div class="sect1"> -<h2 id="building-a-dataflow"><a class="anchor" href="user-guide.html#building-a-dataflow"></a>Building a DataFlow</h2> +<h2 id="logging-in"><a class="anchor" href="#logging-in"></a>Logging In</h2> +<div class="sectionbody"> +<div class="paragraph"> +<p>If NiFi is configured to run securely, users will be able to request access to the DataFlow. For information on configuring NiFi to run +securely, see the <a href="administration-guide.html">Admin Guide</a>. If NiFi supports anonymous access, users will be given access +accordingly and given an option to log in.</p> +</div> +<div class="imageblock"> +<div class="content"> +<img src="./images/anonymous-access.png" alt="Anonymous Access"> +</div> +</div> +<div class="paragraph"> +<p>Clicking the <em>login</em> link will open the log in page. If the user is logging in with their username/password they will be presented with +a form to do so. If NiFi is not configured to support anonymous access and the user is logging in with their username/password, they will +be immediately sent to the login form bypassing the canvas.</p> +</div> +<div class="imageblock"> +<div class="content"> +<img src="./images/login.png" alt="Log In"> +</div> +</div> +<div class="paragraph"> +<p>Once the user has logged in or if they are accessing NiFi using a client certificate loaded in their browser, they will be prompted +to request access by submitting a justification if this is the first time they have accessed this NiFi. Fill in an optional justification +that the administrator will review while granting the account access. If NiFi is not configured to support anonymous access and the +user is using a client certificate, they will be immediately sent to the form to request access bypassing the canvas and login form.</p> +</div> +<div class="imageblock"> +<div class="content"> +<img src="./images/request-access.png" alt="Request Access"> +</div> +</div> +<div class="paragraph"> +<p>Press Submit to send the account request. If NiFi supports anonymous access, the user can continue accessing the DataFlow by closing the +login page. Returning to the login page will check the status of the account request. If access has been granted, press the home link or +reload the page to assume the new roles.</p> +</div> +</div> +</div> +<div class="sect1"> +<h2 id="building-dataflow"><a class="anchor" href="#building-dataflow"></a>Building a DataFlow</h2> <div class="sectionbody"> <div class="paragraph"> <p>A DFM is able to build an automated dataflow using the NiFi User Interface (UI). Simply drag components from the toolbar to the canvas, configure the components to meet specific needs, and connect the components together.</p> </div> <div class="sect2"> -<h3 id="adding-components-to-the-canvas"><a class="anchor" href="user-guide.html#adding-components-to-the-canvas"></a>Adding Components to the Canvas</h3> +<h3 id="adding-components-to-the-canvas"><a class="anchor" href="#adding-components-to-the-canvas"></a>Adding Components to the Canvas</h3> <div class="paragraph"> <p>In the User Interface section above outlined the different segments of the UI and pointed out a Components Toolbar. This section looks at each of the Components in that toolbar:</p> </div> <div class="imageblock"> <div class="content"> -<img src="images/components.png" alt="Components"> +<img src="./images/components.png" alt="Components"> </div> </div> <div id="processor" class="paragraph"> -<p><span class="image"><img src="images/iconProcessor.png" alt="Processor" width="32"></span> +<p><span class="image"><img src="./images/iconProcessor.png" alt="Processor" width="32"></span> <strong>Processor</strong>: The Processor is the most commonly used component, as it is responsible for data ingress, egress, routing, and manipulating. There are many different types of Processors. In fact, this is a very common Extension Point in NiFi, meaning that many vendors may implement their own Processors to perform whatever functions are necessary for their use case. - When a Processor is dragged onto the graph, the user is presented with a dialog to choose which type of Processor to use:</p> + When a Processor is dragged onto the canvas, the user is presented with a dialog to choose which type of Processor to use:</p> </div> <div class="imageblock"> <div class="content"> -<img src="images/add-processor.png" alt="Add Processor Dialog"> +<img src="./images/add-processor.png" alt="Add Processor Dialog"> </div> </div> <div class="paragraph"> @@ -738,7 +786,7 @@ Processors that allow us to ingest data </div> <div class="imageblock"> <div class="content"> -<img src="images/add-processor-with-tag-cloud.png" alt="Add Processor with Tag Cloud"> +<img src="./images/add-processor-with-tag-cloud.png" alt="Add Processor with Tag Cloud"> </div> </div> <div class="paragraph"> @@ -746,43 +794,135 @@ Processors that allow us to ingest data location that it was dropped.</p> </div> <div class="paragraph"> -<p><strong>Note</strong>: For any component added to the graph, it is possible to select it with the mouse and move it anywhere on the graph. Also, it is possible to select multiple items at once by either holding down the Shift key and selecting each item or by holding down the Shift key and dragging a selection box around the desired components.</p> +<p><strong>Note</strong>: For any component added to the canvas, it is possible to select it with the mouse and move it anywhere on the canvas. Also, it is possible to select multiple items at once by either holding down the Shift key and selecting each item or by holding down the Shift key and dragging a selection box around the desired components.</p> +</div> +<div class="paragraph"> +<p>Once a Processor has been dragged onto the canvas, the user may interact with it by right-clicking on the Processor and selecting an option from +context menu.</p> +</div> +<div class="imageblock"> +<div class="content"> +<img src="./images/nifi-processor-menu.png" alt="Processor Menu" width="300"> +</div> +</div> +<div class="paragraph"> +<p>The following options are available:</p> +</div> +<div class="ulist"> +<ul> +<li> +<p><strong>Configure</strong>: This option allows the user to establish or change the configuration of the Processor. (See <a href="#Configuring_a_Processor">Configuring a Processor</a>.)</p> +</li> +<li> +<p><strong>Start</strong> or <strong>Stop</strong>: This option allows the user to start or stop a Processor; the option will be either Start or Stop, depending on the current state of the Processor.</p> +</li> +<li> +<p><strong>Stats</strong>: This option opens a graphical representation of the Processor’s statistical information over time.</p> +</li> +<li> +<p><strong>Upstream connections</strong>: This option allows the user to see and "jump to" upstream connections that are coming into the Processor. This is particularly useful when processors connect into and out of other Process Groups.</p> +</li> +<li> +<p><strong>Downstream connections</strong>: This option allows the user to see and "jump to" downstream connections that are going out of the Processor. This is particularly useful when processors connect into and out of other Process Groups.</p> +</li> +<li> +<p><strong>Usage</strong>: This option takes the user to the Processor’s usage documentation.</p> +</li> +<li> +<p><strong>Change color</strong>: This option allows the user to change the color of the Processor, which can make the visual management of large flows easier.</p> +</li> +<li> +<p><strong>Center in view</strong>: This option centers the view of the canvas on the given Processor.</p> +</li> +<li> +<p><strong>Copy</strong>: This option places a copy of the selected Processor on the clipboard, so that it may be pasted elsewhere on the canvas by right-clicking on the canvas and selecting Paste. The Copy/Paste actions also may be done using the keystrokes Ctrl-C (Command-C) and Ctrl-V (Command-V).</p> +</li> +<li> +<p><strong>Delete</strong>: This option allows the DFM to delete a Processor from the canvas.</p> +</li> +</ul> </div> <div id="input_port" class="paragraph"> -<p><span class="image"><img src="images/iconInputPort.png" alt="Input Port" width="32"></span> +<p><span class="image"><img src="./images/iconInputPort.png" alt="Input Port" width="32"></span> <strong>Input Port</strong>: Input Ports provide a mechanism for transferring data into a Process Group. When an Input Port is dragged onto the canvas, the DFM is prompted to name the Port. All Ports within a Process Group must have unique names.</p> </div> <div class="paragraph"> <p>All components exist only within a Process Group. When a user initially navigates to the NiFi page, the user is placed in the Root Process Group. If the Input Port is dragged onto the Root Process Group, the Input Port provides a mechanism -to receive data from remote instances of NiFi via <a href="user-guide.html#site-to-site">Site-to-Site</a>. In this case, the Input Port can be configured +to receive data from remote instances of NiFi via <a href="#site-to-site">Site-to-Site</a>. In this case, the Input Port can be configured to restrict access to appropriate users, if NiFi is configured to run securely. For information on configuring NiFi to run securely, see the <a href="administration-guide.html">Admin Guide</a>.</p> </div> <div id="output_port" class="paragraph"> -<p><span class="image"><img src="images/iconOutputPort.png" alt="Output Port" width="32"></span> +<p><span class="image"><img src="./images/iconOutputPort.png" alt="Output Port" width="32"></span> <strong>Output Port</strong>: Output Ports provide a mechanism for transferring data from a Process Group to destinations outside of the Process Group. When an Output Port is dragged onto the canvas, the DFM is prompted to name the Port. All Ports within a Process Group must have unique names.</p> </div> <div class="paragraph"> <p>If the Output Port is dragged onto the Root Process Group, the Output Port provides a mechanism for sending data to -remote instances of NiFi via <a href="user-guide.html#site-to-site">Site-to-Site</a>. In this case, the Port acts as a queue. As remote instances +remote instances of NiFi via <a href="#site-to-site">Site-to-Site</a>. In this case, the Port acts as a queue. As remote instances of NiFi pull data from the port, that data is removed from the queues of the incoming Connections. If NiFi is configured to run securely, the Output Port can be configured to restrict access to appropriate users. For information on configuring NiFi to run securely, see the <a href="administration-guide.html">Admin Guide</a>.</p> </div> <div id="process_group" class="paragraph"> -<p><span class="image"><img src="images/iconProcessGroup.png" alt="Process Group" width="32"></span> +<p><span class="image"><img src="./images/iconProcessGroup.png" alt="Process Group" width="32"></span> <strong>Process Group</strong>: Process Groups can be used to logically group a set of components so that the dataflow is easier to understand and maintain. When a Process Group is dragged onto the canvas, the DFM is prompted to name the Process Group. All Process Groups within the same parent group must have unique names. The Process Group will then be nested within that parent group.</p> </div> +<div class="paragraph"> +<p>Once a Process Group has been dragged onto the canvas, the user may interact with it by right-clicking on the Process Group and selecting an option from +context menu.</p> +</div> +<div class="imageblock"> +<div class="content"> +<img src="./images/nifi-process-group-menu.png" alt="Process Group Menu" width="300"> +</div> +</div> +<div class="paragraph"> +<p>The following options are available:</p> +</div> +<div class="ulist"> +<ul> +<li> +<p><strong>Configure</strong>: This option allows the user to establish or change the configuration of the Process Group.</p> +</li> +<li> +<p><strong>Enter group</strong>: This option allows the user to enter the Process Group. It is also possible to double-click on the Process Group to enter it.</p> +</li> +<li> +<p><strong>Start</strong>: This option allows the user to start a Process Group.</p> +</li> +<li> +<p><strong>Stop</strong>: This option allows the user to stop a Process Group.</p> +</li> +<li> +<p><strong>Stats</strong>: This option opens a graphical representation of the Process Group’s statistical information over time.</p> +</li> +<li> +<p><strong>Upstream connections</strong>: This option allows the user to see and "jump to" upstream connections that are coming into the Process Group.</p> +</li> +<li> +<p><strong>Downstream connections</strong>: This option allows the user to see and "jump to" downstream connections that are going out of the Process Group.</p> +</li> +<li> +<p><strong>Center in view</strong>: This option centers the view of the canvas on the given Process Group.</p> +</li> +<li> +<p><strong>Copy</strong>: This option places a copy of the selected Process Group on the clipboard, so that it may be pasted elsewhere on the canvas by right-clicking on the canvas and selecting Paste. The Copy/Paste actions also may be done using the keystrokes Ctrl-C (Command-C) and Ctrl-V (Command-V).</p> +</li> +<li> +<p><strong>Delete</strong>: This option allows the DFM to delete a Process Group.</p> +</li> +</ul> +</div> <div id="remote_process_group" class="paragraph"> -<p><span class="image"><img src="images/iconRemoteProcessGroup.png" alt="Remote Process Group" width="32"></span> +<p><span class="image"><img src="./images/iconRemoteProcessGroup.png" alt="Remote Process Group" width="32"></span> <strong>Remote Process Group</strong>: Remote Process Groups appear and behave similar to Process Groups. However, the Remote Process Group (RPG) references a remote instance of NiFi. When an RPG is dragged onto the canvas, rather than being prompted for a name, the DFM is prompted for the URL of the remote NiFi instance. If the remote NiFi is a clustered instance, the URL that should be used @@ -790,10 +930,62 @@ is the URL of the remote instance’ via an RPG, the RPG it will first connect to the remote instance’s NCM to determine which nodes are in the cluster and how busy each node is. This information is then used to load balance the data that is pushed to each node. The remote NCM is then interrogated periodically to determine information about any nodes that are dropped from or added to the cluster and to -recalculate the load balancing based on each node’s load. For more information, see the section on <a href="user-guide.html#site-to-site">Site-to-Site</a>.</p> +recalculate the load balancing based on each node’s load. For more information, see the section on <a href="#site-to-site">Site-to-Site</a>.</p> +</div> +<div class="paragraph"> +<p>Once a Remote Process Group has been dragged onto the canvas, the user may interact with it by right-clicking on the Remote Process Group and selecting an option from +context menu.</p> +</div> +<div class="imageblock"> +<div class="content"> +<img src="./images/nifi-rpg-menu.png" alt="Remote Process Group Menu" width="300"> +</div> +</div> +<div class="paragraph"> +<p>The following options are available:</p> +</div> +<div class="ulist"> +<ul> +<li> +<p><strong>Configure</strong>: This option allows the user to establish or change the configuration of the Remote Process Group.</p> +</li> +<li> +<p><strong>Remote Ports</strong>: This option allows the user to see input ports and/or output ports that exist on the remote instance of NiFi that the Remote Process Group is connected to. Note that if the Site-to-Site configuration is secure, only the ports that the connecting NiFi has been given accessed to will be visible.</p> +</li> +<li> +<p><strong>Enable transmission</strong>: Makes the transmission of data between NiFi instances active. (See <a href="#Remote_Group_Transmission">Remote Process Group Transmission</a> )</p> +</li> +<li> +<p><strong>Disable transmission</strong>: Disables the transmission of data between NiFi instances.</p> +</li> +<li> +<p><strong>Stats</strong>: This option opens a graphical representation of the Remote Process Group’s statistical information over time.</p> +</li> +<li> +<p><strong>Upstream connections</strong>: This option allows the user to see and "jump to" upstream connections that are coming into the Remote Process Group.</p> +</li> +<li> +<p><strong>Downstream connections</strong>: This option allows the user to see and "jump to" downstream connections that are going out of the Remote Process Group.</p> +</li> +<li> +<p><strong>Refresh</strong>: This option refreshes the view of the status of the remote NiFi instance.</p> +</li> +<li> +<p><strong>Go to</strong>: This option opens a view of the remote NiFi instance in a new tab of the browser. Note that if the Site-to-Site configuration is secure, the user must have access to the remote NiFi instance in order to view it.</p> +</li> +<li> +<p><strong>Center in view</strong>: This option centers the view of the canvas on the given Remote Process Group.</p> +</li> +<li> +<p><strong>Copy</strong>: This option places a copy of the selected Process Group on the clipboard, so that it may be pasted elsewhere on the canvas by right-clicking on the canvas and selecting Paste. The Copy/Paste actions also may be done using the keystrokes Ctrl-C (Command-C) and Ctrl-V (Command-V).</p> +</li> +<li> +<p><strong>Delete</strong>: This option allows the DFM to delete a Remote Process Group from the canvas.</p> +</li> +</ul> </div> <div id="funnel" class="paragraph"> -<p><span class="image"><img src="images/iconFunnel.png" alt="Funnel" width="32"></span> +<p><span class="image"><img src="./images/iconFunnel.png" alt="Funnel" width="32"></span> <strong>Funnel</strong>: Funnels are used to combine the data from many Connections into a single Connection. This has two advantages. First, if many Connections are created with the same destination, the canvas can become cluttered if those Connections have to span a large space. By funneling these Connections into a single Connection, that single Connection can then be @@ -802,14 +994,14 @@ several Connections can be funneled into one Connection, rather than prioritizing the data on each Connection independently.</p> </div> <div id="template" class="paragraph"> -<p><span class="image"><img src="images/iconTemplate.png" alt="Template" width="32"></span> +<p><span class="image"><img src="./images/iconTemplate.png" alt="Template" width="32"></span> <strong>Template</strong>: Templates can be created by DFMs from sections of the flow, or they can be imported from other dataflows. These Templates provide larger building blocks for creating a complex flow quickly. When the Template is dragged onto the canvas, the DFM is provided a dialog to choose which Template to add to the canvas:</p> </div> <div class="imageblock"> <div class="content"> -<img src="images/instantiate-template.png" alt="Instantiate Template Dialog"> +<img src="./images/instantiate-template.png" alt="Instantiate Template Dialog"> </div> </div> <div class="paragraph"> @@ -818,11 +1010,11 @@ icon, indicating that there is more info </div> <div class="imageblock"> <div class="content"> -<img src="images/instantiate-template-description.png" alt="Instantiate Template Dialog"> +<img src="./images/instantiate-template-description.png" alt="Instantiate Template Dialog"> </div> </div> <div id="label" class="paragraph"> -<p><span class="image"><img src="images/iconLabel.png" alt="Label"></span> +<p><span class="image"><img src="./images/iconLabel.png" alt="Label"></span> <strong>Label</strong>: Labels are used to provide documentation to parts of a dataflow. When a Label is dropped onto the canvas, it is created with a default size. The Label can then be resized by dragging the handle in the bottom-right corner. The Label has no text when initially created. The text of the Label can be added by right-clicking on the Label and @@ -830,10 +1022,9 @@ choosing <code>Configure...</code></p> </div> </div> <div class="sect2"> -<h3 id="configuring-a-processor"><a class="anchor" href="user-guide.html#configuring-a-processor"></a>Configuring a Processor</h3> +<h3 id="Configuring_a_Processor"><a class="anchor" href="#Configuring_a_Processor"></a>Configuring a Processor</h3> <div class="paragraph"> -<p>Once a Processor has been dragged onto the Canvas, it is ready to configure. This is done by right-clicking on the -Processor and clicking the <code>Configure...</code> option from the context menu. The configuration dialog is opened with four +<p>To configure a processor, right-click on the Processor and select the <code>Configure...</code> option from the context menu. The configuration dialog is opened with four different tabs, each of which is discussed below. Once you have finished configuring the Processor, you can apply the changes by clicking the <code>Apply</code> button or cancel all changes by clicking the <code>Cancel</code> button.</p> </div> @@ -844,19 +1035,19 @@ running. You must first stop the Process the Processor again.</p> </div> <div class="sect3"> -<h4 id="settings-tab"><a class="anchor" href="user-guide.html#settings-tab"></a>Settings Tab</h4> +<h4 id="settings-tab"><a class="anchor" href="#settings-tab"></a>Settings Tab</h4> <div class="paragraph"> <p>The first tab in the Processor Configuration dialog is the Settings tab:</p> </div> <div class="imageblock"> <div class="content"> -<img src="images/settings-tab.png" alt="Settings Tab"> +<img src="./images/settings-tab.png" alt="Settings Tab"> </div> </div> <div class="paragraph"> <p>This tab contains several different configuration items. First, it allows the DFM to change the name of the Processor. The name of a Processor by default is the same as the Processor type. Next to the Processor Name is a checkbox, indicating - whether the Processor is Enabled. When a Processor is added to the graph, it is enabled. If the + whether the Processor is Enabled. When a Processor is added to the canvas, it is enabled. If the Processor is disabled, it cannot be started. The disabled state is used to indicate that when a group of Processors is started, such as when a DFM starts an entire Process Group, this (disabled) Processor should be excluded.</p> </div> @@ -897,13 +1088,13 @@ auto-terminated, the auto-termination st </div> </div> <div class="sect3"> -<h4 id="scheduling-tab"><a class="anchor" href="user-guide.html#scheduling-tab"></a>Scheduling Tab</h4> +<h4 id="scheduling-tab"><a class="anchor" href="#scheduling-tab"></a>Scheduling Tab</h4> <div class="paragraph"> <p>The second tab in the Processor Configuration dialog is the Scheduling Tab:</p> </div> <div class="imageblock"> <div class="content"> -<img src="images/scheduling-tab.png" alt="Scheduling Tab"> +<img src="./images/scheduling-tab.png" alt="Scheduling Tab"> </div> </div> <div class="paragraph"> @@ -1000,20 +1191,20 @@ Lower Latency or Higher Throughput.</p> </div> </div> <div class="sect3"> -<h4 id="properties-tab"><a class="anchor" href="user-guide.html#properties-tab"></a>Properties Tab</h4> +<h4 id="properties-tab"><a class="anchor" href="#properties-tab"></a>Properties Tab</h4> <div class="paragraph"> <p>The Properties Tab provides a mechanism to configure Processor-specific behavior. There are no default properties. Each type of Processor must define which Properties make sense for its use case. Below, we see the Properties Tab for a RouteOnAttribute Processor:</p> </div> <div class="imageblock"> <div class="content"> -<img src="images/properties-tab.png" alt="Properties Tab"> +<img src="./images/properties-tab.png" alt="Properties Tab"> </div> </div> <div class="paragraph"> <p>This Processor, by default, has only a single property: ‘Routing Strategy.’ The default value is ‘Route on Property name.’ Next to the name of this property is a small question-mark symbol ( -<span class="image"><img src="images/iconInfo.png" alt="Question Mark"></span> +<span class="image"><img src="./images/iconInfo.png" alt="Question Mark"></span> ). This help symbol is seen in other places throughout the User Interface, and it indicates that more information is available. Hovering over this symbol with the mouse will provide additional details about the property and the default value, as well as historical values that have been set for the Property.</p> @@ -1024,7 +1215,7 @@ the user is either provided a drop-down </div> <div class="imageblock"> <div class="content"> -<img src="images/edit-property-dropdown.png" alt="Edit Property with Dropdown"> +<img src="./images/edit-property-dropdown.png" alt="Edit Property with Dropdown"> </div> </div> <div class="paragraph"> @@ -1034,38 +1225,38 @@ the Processor becomes invalid when User- In fact, this Processor will not be valid until the user has added a property.</p> </div> <div class="paragraph"> -<p><span class="image"><img src="images/edit-property-textarea.png" alt="Edit Property with Text Area"></span></p> +<p><span class="image"><img src="./images/edit-property-textarea.png" alt="Edit Property with Text Area"></span></p> </div> <div class="paragraph"> <p>Note that after a User-Defined property has been added, an icon will appear on the right-hand side of that row ( -<span class="image"><img src="images/iconDelete.png" alt="Delete Icon"></span> +<span class="image"><img src="./images/iconDelete.png" alt="Delete Icon"></span> ). Clicking this button will remove the User-Defined property from the Processor.</p> </div> <div class="paragraph"> <p>Some processors also have an Advanced User Interface (UI) built into them. For example, the UpdateAttribute processor has an Advanced UI. To access the Advanced UI, click the <code>Advanced</code> button that appears at the bottom of the Configure Processor window. Only processors that have an Advanced UI will have this button.</p> </div> <div class="paragraph"> -<p>Some processors have properties that refer to other components, such as Controller Services, which also need to be configured. For example, the GetHTTP processor has an SSLContextService property, which refers to the StandardSSLContextService controller service. When DFMs want to configure this property but have not yet created and configured the controller service, they have the option to create the service on the spot, as depicted in the image below. For more information about configuring Controller Services, see the <a href="user-guide.html#Controller_Services_and_Reporting_Tasks">Controller Services and Reporting Tasks</a> section.</p> +<p>Some processors have properties that refer to other components, such as Controller Services, which also need to be configured. For example, the GetHTTP processor has an SSLContextService property, which refers to the StandardSSLContextService controller service. When DFMs want to configure this property but have not yet created and configured the controller service, they have the option to create the service on the spot, as depicted in the image below. For more information about configuring Controller Services, see the <a href="#Controller_Services_and_Reporting_Tasks">Controller Services and Reporting Tasks</a> section.</p> </div> <div class="paragraph"> -<p><span class="image"><img src="images/create-service-ssl-context.png" alt="Create Service" width="700"></span></p> +<p><span class="image"><img src="./images/create-service-ssl-context.png" alt="Create Service" width="700"></span></p> </div> </div> <div class="sect3"> -<h4 id="comments-tab"><a class="anchor" href="user-guide.html#comments-tab"></a>Comments Tab</h4> +<h4 id="comments-tab"><a class="anchor" href="#comments-tab"></a>Comments Tab</h4> <div class="paragraph"> <p>The last tab in the Processor configuration dialog is the Comments tab. This tab simply provides an area for users to include whatever comments are appropriate for this component. Use of the Comments tab is optional:</p> </div> <div class="imageblock"> <div class="content"> -<img src="images/comments-tab.png" alt="Comments Tab"> +<img src="./images/comments-tab.png" alt="Comments Tab"> </div> </div> </div> </div> <div class="sect2"> -<h3 id="additional-help"><a class="anchor" href="user-guide.html#additional-help"></a>Additional Help</h3> +<h3 id="additional-help"><a class="anchor" href="#additional-help"></a>Additional Help</h3> <div class="paragraph"> <p>The user may access additional documentation about each Processor’s usage by right-clicking on the Processor and then selecting ‘Usage’ from the context menu. Alternatively, clicking the ‘Help’ link in the top-right @@ -1074,12 +1265,14 @@ for all the Processors that are availabl </div> </div> <div class="sect2"> -<h3 id="Controller_Services_and_Reporting_Tasks"><a class="anchor" href="user-guide.html#Controller_Services_and_Reporting_Tasks"></a>Controller Services and Reporting Tasks</h3> +<h3 id="Controller_Services_and_Reporting_Tasks"><a class="anchor" href="#Controller_Services_and_Reporting_Tasks"></a>Controller Services and Reporting Tasks</h3> <div class="paragraph"> <p>While DFMs have the ability to create Controller Services from the Configure Processor window, there is also a central place within the User Interface for adding and configuring both Controller Services and Reporting Tasks. To get there, click on the Controller Settings button in the Management section of the toolbar.</p> </div> +<div class="sect3"> +<h4 id="Controller_Settings"><a class="anchor" href="#Controller_Settings"></a>Controller Settings</h4> <div class="paragraph"> -<p><span class="image"><img src="images/controller-settings-button.png" alt="Controller Settings Button" width="200"></span></p> +<p><span class="image"><img src="./images/controller-settings-button.png" alt="Controller Settings Button" width="200"></span></p> </div> <div class="paragraph"> <p>The Controller Settings window has three tabs across the top: General, Controller Services, and Reporting Tasks. The General tab is for settings that pertain to general information about the NiFi instance. For example, here, the DFM can provide a unique name for the overall dataflow, as well as comments that describe the flow. Be aware that this information is visible to any other NiFi instance that connects remotely to this instance (using Remote Process Groups, a.k.a., Site-to-Site).</p> @@ -1088,37 +1281,37 @@ for all the Processors that are availabl <p>The General tab also provides settings for the overall maximum thread counts of the instance, as well as the ability to click "Back-up flow" to create a backup copy of the current flow, which is saved by default in the /conf/archive directory.</p> </div> <div class="paragraph"> -<p><span class="image"><img src="images/settings-general-tab.png" alt="Controller Settings General Tab" width="700"></span></p> +<p><span class="image"><img src="./images/settings-general-tab.png" alt="Controller Settings General Tab" width="700"></span></p> </div> <div class="paragraph"> <p>To the right of the General tab is the Controller Services tab. From this tab, the DFM may click the "+" button in the upper-right corner to create a new Controller Service.</p> </div> <div class="paragraph"> -<p><span class="image"><img src="images/controller-services-tab.png" alt="Controller Services Tab" width="900"></span></p> +<p><span class="image"><img src="./images/controller-services-tab.png" alt="Controller Services Tab" width="900"></span></p> </div> <div class="paragraph"> -<p>The Add Controller Service window opens. This window is similar to the Add Processor window. It provides a list of the available Controller Services on the right and a tag cloud, showing the most common catagory tags used for Controller Services, on the left. The DFM may click any tag in the tag cloud in order to narrow down the list of Controller Services to those that fit the categories desired. The DFM may also use the Filter field at the top of the window to search for the desired Contoller Service. Upon selecting a Controller Service from the list, the DFM can see a description of the the service below. Select the desired controller service and click Add, or simply double-click the name of the service to add it.</p> +<p>The Add Controller Service window opens. This window is similar to the Add Processor window. It provides a list of the available Controller Services on the right and a tag cloud, showing the most common category tags used for Controller Services, on the left. The DFM may click any tag in the tag cloud in order to narrow down the list of Controller Services to those that fit the categories desired. The DFM may also use the Filter field at the top of the window to search for the desired Controller Service. Upon selecting a Controller Service from the list, the DFM can see a description of the the service below. Select the desired controller service and click Add, or simply double-click the name of the service to add it.</p> </div> <div class="paragraph"> -<p><span class="image"><img src="images/add-controller-service-window.png" alt="Add Controller Service Window" width="700"></span></p> +<p><span class="image"><img src="./images/add-controller-service-window.png" alt="Add Controller Service Window" width="700"></span></p> </div> <div class="paragraph"> <p>Once a Controller Service has been added, the DFM may configure it by clicking the Edit button (pencil icon) in the far-right column. Other buttons in this column include the Enable button (to enable a configured service), the Remove button, and the Usage button, which links to the documentation for the particular Controller Service.</p> </div> <div class="paragraph"> -<p><span class="image"><img src="images/controller-services-edit-buttons.png" alt="Controller Services Buttons"></span></p> +<p><span class="image"><img src="./images/controller-services-edit-buttons.png" alt="Controller Services Buttons"></span></p> </div> <div class="paragraph"> <p>When the DFM clicks the Edit button, a Configure Controller Service window opens. It has three tabs: Settings, Properties, and Comments. This window is similar to the Configure Processor window. The Settings tab provides a place for the DFM to give the Controller Service a unique name (if desired). It also lists the UUID for the service and provides a list of other components (processors or other controller services) that reference the service.</p> </div> <div class="paragraph"> -<p><span class="image"><img src="images/configure-controller-service-settings.png" alt="Configure Controller Service Settings" width="700"></span></p> +<p><span class="image"><img src="./images/configure-controller-service-settings.png" alt="Configure Controller Service Settings" width="700"></span></p> </div> <div class="paragraph"> <p>The Properties tab lists the various properties that apply to the particular controller service. As with configuring processors, the DFM may hover the mouse over the question mark icons to see more information about each property.</p> </div> <div class="paragraph"> -<p><span class="image"><img src="images/configure-controller-service-properties.png" alt="Configure Controller Service Properties" width="700"></span></p> +<p><span class="image"><img src="./images/configure-controller-service-properties.png" alt="Configure Controller Service Properties" width="700"></span></p> </div> <div class="paragraph"> <p>The Comments tab is just an open-text field, where the DFM may include comments about the service. After configuring a Controller Service, click the Apply button to apply the configuration and close the window, or click the Cancel button to cancel the changes and close the window.</p> @@ -1130,25 +1323,25 @@ for all the Processors that are availabl <p>The Reporting Tasks tab behaves similarly to the Controller Services tab. The DFM has the option to add Reporting Tasks and configure them in the same way as Controller Services.</p> </div> <div class="paragraph"> -<p><span class="image"><img src="images/reporting-tasks-tab.png" alt="Reporting Tasks Tab" width="900"></span></p> +<p><span class="image"><img src="./images/reporting-tasks-tab.png" alt="Reporting Tasks Tab" width="900"></span></p> </div> <div class="paragraph"> <p>Once a Reporting Task has been added, the DFM may configure it by clicking the Edit (pencil icon) in the far-right column. Other buttons in this column include the Start button, Remove button, and Usage button, which links to the documentation for the particular Reporting Task.</p> </div> <div class="paragraph"> -<p><span class="image"><img src="images/reporting-tasks-edit-buttons2.png" alt="Reporting Tasks Buttons"></span></p> +<p><span class="image"><img src="./images/reporting-tasks-edit-buttons2.png" alt="Reporting Tasks Buttons"></span></p> </div> <div class="paragraph"> <p>When the DFM clicks the Edit button, a Configure Reporting Task window opens. It has three tabs: Settings, Properties, and Comments. This window is also similar to the Configure Processor window. The Settings tab provides a place for the DFM to give the Reporting Task a unique name (if desired). It also lists a UUID for the Reporting Task and provides settings for the task’s Scheduling Strategy and Run Schedule (similar to the same settings in a processor). The DFM may hover the mouse over the question mark icons to see more information about each setting.</p> </div> <div class="paragraph"> -<p><span class="image"><img src="images/configure-reporting-task-settings.png" alt="Configure Reporting Task Settings" width="700"></span></p> +<p><span class="image"><img src="./images/configure-reporting-task-settings.png" alt="Configure Reporting Task Settings" width="700"></span></p> </div> <div class="paragraph"> <p>The Properties tab for a Reporting Task lists the properties that may be configured for the task. The DFM may hover the mouse over the question mark icons to see more information about each property.</p> </div> <div class="paragraph"> -<p><span class="image"><img src="images/configure-reporting-task-properties.png" alt="Configure Reporting Task Properties" width="700"></span></p> +<p><span class="image"><img src="./images/configure-reporting-task-properties.png" alt="Configure Reporting Task Properties" width="700"></span></p> </div> <div class="paragraph"> <p>The Comments tab is just an open-text field, where the DFM may include comments about the task. After configuring the Reporting Task, click the Apply button to apply the configuration and close the window, or click Cancel to cancel the changes and close the window.</p> @@ -1157,17 +1350,18 @@ for all the Processors that are availabl <p>When you want to run the Reporting Task, click the Start button in the far-right column of the Reporting Tasks tab.</p> </div> </div> +</div> <div class="sect2"> -<h3 id="connecting-components"><a class="anchor" href="user-guide.html#connecting-components"></a>Connecting Components</h3> +<h3 id="Connecting_Components"><a class="anchor" href="#Connecting_Components"></a>Connecting Components</h3> <div class="paragraph"> -<p>Once processors and other components have been added to the graph and configured, the next step is to connect them +<p>Once processors and other components have been added to the canvas and configured, the next step is to connect them to one another so that NiFi knows what to do with each FlowFile after it has been processed. This is accomplished by creating a Connection between each component. When the user hovers the mouse over the center of a component, a new Connection icon ( -<span class="image"><img src="images/addConnect.png" alt="Connection Bubble"></span> +<span class="image"><img src="./images/addConnect.png" alt="Connection Bubble"></span> ) appears:</p> </div> <div class="paragraph"> -<p><span class="image"><img src="images/processor-connection-bubble.png" alt="Processor with Connection Bubble"></span></p> +<p><span class="image"><img src="./images/processor-connection-bubble.png" alt="Processor with Connection Bubble"></span></p> </div> <div class="paragraph"> <p>The user drags the Connection bubble from one component to another until the second component is highlighted. When the user @@ -1177,14 +1371,14 @@ useful if the DFM wants the processor to connection, simply drag the connection bubble away and then back to the same processor until it is highlighted. Then release the mouse and the same <em>Create Connection</em> dialog appears.</p> </div> <div class="sect3"> -<h4 id="details-tab"><a class="anchor" href="user-guide.html#details-tab"></a>Details Tab</h4> +<h4 id="details-tab"><a class="anchor" href="#details-tab"></a>Details Tab</h4> <div class="paragraph"> <p>The Details Tab of the <em>Create Connection</em> dialog provides information about the source and destination components, including the component name, the component type, and the Process Group in which the component lives:</p> </div> <div class="imageblock"> <div class="content"> -<img src="images/create-connection.png" alt="Create Connection"> +<img src="./images/create-connection.png" alt="Create Connection"> </div> </div> <div class="paragraph"> @@ -1197,13 +1391,13 @@ automatically be ‘cloned’, a </div> </div> <div class="sect3"> -<h4 id="settings"><a class="anchor" href="user-guide.html#settings"></a>Settings</h4> +<h4 id="settings"><a class="anchor" href="#settings"></a>Settings</h4> <div class="paragraph"> <p>The Settings Tab provides the ability to configure the Connection’s name, FlowFile expiration, Back Pressure thresholds, and Prioritization:</p> </div> <div class="paragraph"> -<p><span class="image"><img src="images/connection-settings.png" alt="Connection Settings"></span></p> +<p><span class="image"><img src="./images/connection-settings.png" alt="Connection Settings"></span></p> </div> <div class="paragraph"> <p>The Connection name is optional. If not specified, the name shown for the Connection will be names of the Relationships @@ -1214,7 +1408,7 @@ that are active for the Connection.</p> This is useful, for example, when the volume of data is expected to exceed the volume that can be sent to a remote site. In this case, the expiration can be used in conjunction with Prioritizers to ensure that the highest priority data is processed first and then anything that cannot be processed within a certain time period (one hour, for example) can be dropped. The expiration period is based on the time that the data entered the NiFi instance. In other words, if the file expiration on a given connection is set to <em>1 hour</em>, and a file that has been in the NiFi instance for one hour reaches that connection, it will expire. The default -value of <code>0 sec</code> indicates that the data will never expire. When a file expiration other than <em>0 sec</em> is set, a small clock icon appears on the connection label, so the DFM can see it at-a-glance when looking at a flow on the graph.</p> +value of <code>0 sec</code> indicates that the data will never expire. When a file expiration other than <em>0 sec</em> is set, a small clock icon appears on the connection label, so the DFM can see it at-a-glance when looking at a flow on the canvas.</p> </div> <div class="paragraph"> <p>NiFi provides two configuration elements for Back Pressure. These thresholds indicate how much data should be @@ -1249,17 +1443,54 @@ prioritizers’ list to the ‘A <p><strong>OldestFlowFileFirstPrioritizer</strong>: Given two FlowFiles, the on that is oldest in the dataflow will be processed first. This is the default scheme that is used if no prioritizers are selected.</p> </li> <li> -<p><strong>PriorityAttributePrioritizer</strong>: Given two FlowFiles that both have a "priority" attribute, the one that has the highest priority value will be prprocessed first. Note that an UpdateAttribute processor should be used to add the "priority" attribute to the FlowFiles before they reach a connection that has this prioritizer set. Values for the "priority" attribute may be alphanumeric, where "a" is a higher priority than "z", and "1" is a higher priority than "9", for example.</p> +<p><strong>PriorityAttributePrioritizer</strong>: Given two FlowFiles that both have a "priority" attribute, the one that has the highest priority value will be processed first. Note that an UpdateAttribute processor should be used to add the "priority" attribute to the FlowFiles before they reach a connection that has this prioritizer set. Values for the "priority" attribute may be alphanumeric, where "a" is a higher priority than "z", and "1" is a higher priority than "9", for example.</p> </li> </ul> </div> <div class="paragraph"> <p><strong>Note</strong>: After a connection has been drawn between two components, the connection’s configuration may be changed, and the connection may be moved to a new destination; however, the processors on either side of the connection must be stopped before a configuration or destination change may be made.</p> </div> +<div class="paragraph"> +<p><span class="image"><img src="./images/nifi-connection.png" alt="Connection" width="300"></span></p> +</div> +<div class="paragraph"> +<p>To change a connection’s configuration or interact with the connection in other ways, right-click on the connection to open the connection context menu.</p> +</div> +<div class="paragraph"> +<p><span class="image"><img src="./images/nifi-connection-menu.png" alt="Connection Menu" width="200"></span></p> +</div> +<div class="paragraph"> +<p>The following options are available:</p> +</div> +<div class="ulist"> +<ul> +<li> +<p><strong>Configure</strong>: This option allows the user to change the configuration of the connection.</p> +</li> +<li> +<p><strong>Stats</strong>: This option opens a graphical representation of the connection’s statistical information over time.</p> +</li> +<li> +<p><strong>Bring to front</strong>: This option brings the connection to the front of the canvas if something else (such as another connection) is overlapping it.</p> +</li> +<li> +<p><strong>Go to source</strong>: This option can be useful if there is a long distance between the connection’s source and destination components on the canvas. By clicking this option, the view of the canvas will jump to the source of the connection.</p> +</li> +<li> +<p><strong>Go to destination</strong>: Similar to the "Go to source" option, this option changes the view to the destination component on the canvas and can be useful if there is a long distance between two connected components.</p> +</li> +<li> +<p><strong>Empty queue</strong>: This option allows the DFM to clear the queue of FlowFiles that may be waiting to be processed. This option can be especially useful during testing, when the DFM is not concerned about deleting data from the queue. When this option is selected, users must confirm that they want to delete the data in the queue.</p> +</li> +<li> +<p><strong>Delete</strong>: This option allows the DFM to delete a connection between two components. Note that the components on both sides of the connection must be stopped and the connection must be empty before it can be deleted.</p> +</li> +</ul> +</div> </div> </div> <div class="sect2"> -<h3 id="processor-validation"><a class="anchor" href="user-guide.html#processor-validation"></a>Processor Validation</h3> +<h3 id="processor-validation"><a class="anchor" href="#processor-validation"></a>Processor Validation</h3> <div class="paragraph"> <p>Before trying to start a Processor, it’s important to make sure that the Processor’s configuration is valid. A status indicator is shown in the top-left of the Processor. If the Processor is invalid, the indicator @@ -1267,7 +1498,7 @@ will show a yellow Warning indicator wit </div> <div class="imageblock"> <div class="content"> -<img src="images/invalid-processor.png" alt="Invalid Processor"> +<img src="./images/invalid-processor.png" alt="Invalid Processor"> </div> </div> <div class="paragraph"> @@ -1277,12 +1508,12 @@ to a Stop icon, indicating that the Proc </div> <div class="imageblock"> <div class="content"> -<img src="images/valid-processor.png" alt="Valid Processor"> +<img src="./images/valid-processor.png" alt="Valid Processor"> </div> </div> </div> <div class="sect2"> -<h3 id="site-to-site"><a class="anchor" href="user-guide.html#site-to-site"></a>Site-to-Site</h3> +<h3 id="site-to-site"><a class="anchor" href="#site-to-site"></a>Site-to-Site</h3> <div class="paragraph"> <p>When sending data from one instance of NiFi to another, there are many different protocols that can be used. The preferred protocol, though, is the NiFi Site-to-Site Protocol. Site-to-Site makes it easy to transfer data from one NiFi instance to @@ -1389,9 +1620,9 @@ or deficiency is ever discovered in a pr </ul> </div> <div class="paragraph"> -<p>In order to communicate with a remote NiFi instance via Site-to-Site, simply drag a <a href="user-guide.html#remote_process_group">Remote Process Group</a> onto the graph +<p>In order to communicate with a remote NiFi instance via Site-to-Site, simply drag a <a href="#remote_process_group">Remote Process Group</a> onto the canvas and enter the URL of the remote NiFi instance (for more information on the components of a Remote Process Group, see -<a href="user-guide.html#Remote_Group_Transmission">Remote Process Group Transmission</a> section of this guide.) The URL is the same +<a href="#Remote_Group_Transmission">Remote Process Group Transmission</a> section of this guide.) The URL is the same URL you would use to go to that instance’s User Interface. At that point, you can drag a connection to or from the Remote Process Group in the same way you would drag a connection to or from a Processor or a local Process Group. When you drag the connection, you will have a chance to choose which Port to connect to. Note that it may take up to one minute for the Remote Process Group to determine @@ -1408,8 +1639,8 @@ communicate with. For information on con <a href="administration-guide.html">Admin Guide</a>.</p> </div> <div class="paragraph"> -<p>In order to allow another NiFi instance to push data to your local instance, you can simply drag an <a href="user-guide.html#input_port">Input Port</a> onto the Root Process Group -of your graph. After entering a name for the port, it will be added to your flow. You can now right-click on the Input Port and choose Configure in order +<p>In order to allow another NiFi instance to push data to your local instance, you can simply drag an <a href="#input_port">Input Port</a> onto the Root Process Group +of your canvas. After entering a name for the port, it will be added to your flow. You can now right-click on the Input Port and choose Configure in order to adjust the name and the number of concurrent tasks that are used for the port. If Site-to-Site is configured to run securely, you will also be given the ability to adjust who has access to the port. If secure, only those who have been granted access to communicate with the port will be able to see that the port exists.</p> @@ -1419,7 +1650,7 @@ that the port exists.</p> Process Group and choose to "Refresh" the flow.</p> </div> <div class="paragraph"> -<p>Similar to an Input Port, a DataFlow Manager may choose to add an <a href="user-guide.html#output_port">Output Port</a> to the Root Process Group. The Output Port allows an +<p>Similar to an Input Port, a DataFlow Manager may choose to add an <a href="#output_port">Output Port</a> to the Root Process Group. The Output Port allows an authorized NiFi instance to remotely connect to your instance and pull data from the Output Port. Configuring the Output Port will again allow the DFM to control how many concurrent tasks are allowed, as well as which NiFi instances are authorized to pull data from the instance being configured.</p> </div> @@ -1441,14 +1672,14 @@ section of the <a href="administration-g </div> </div> <div class="sect2"> -<h3 id="example-dataflow"><a class="anchor" href="user-guide.html#example-dataflow"></a>Example Dataflow</h3> +<h3 id="example-dataflow"><a class="anchor" href="#example-dataflow"></a>Example Dataflow</h3> <div class="paragraph"> <p>This section has described the steps required to build a dataflow. Now, to put it all together. The following example dataflow consists of just two processors: GenerateFlowFile and LogAttribute. These processors are normally used for testing, but they can also be used to build a quick flow for demonstration purposes and see NiFi in action.</p> </div> <div class="paragraph"> -<p>After you drag the GenerateFlowFile and LogAttribute processors to the graph and connect them (using the guidelines provided above), configure them as follows:</p> +<p>After you drag the GenerateFlowFile and LogAttribute processors to the canvas and connect them (using the guidelines provided above), configure them as follows:</p> </div> <div class="ulist"> <ul> @@ -1473,7 +1704,7 @@ to build a quick flow for demonstration <p>On the Settings tab, under Auto-terminate relationships, select the checkbox next to Success. This will terminate FlowFiles after this processor has successfully processed them.</p> </li> <li> -<p>Also on the Settings tab, set the Bulletin level to Info. This way, when the dataflow is running, this processor will display the bulletin icon (see <a href="user-guide.html#processor_anatomy">Anatomy of a Processor</a>), and the user may hover over it with the mouse to see the attributes that the processor is logging.</p> +<p>Also on the Settings tab, set the Bulletin level to Info. This way, when the dataflow is running, this processor will display the bulletin icon (see <a href="#processor_anatomy">Anatomy of a Processor</a>), and the user may hover over it with the mouse to see the attributes that the processor is logging.</p> </li> </ul> </div> @@ -1485,17 +1716,17 @@ to build a quick flow for demonstration </div> <div class="imageblock"> <div class="content"> -<img src="images/simple-flow.png" alt="Simple Flow" width="900"> +<img src="./images/simple-flow.png" alt="Simple Flow" width="900"> </div> </div> <div class="paragraph"> -<p>Now see the following section on how to start and stop the dataflow. When the dataflow is running, be sure to note the statistical information that is displayed on the face of each processor (see <a href="user-guide.html#processor_anatomy">Anatomy of a Processor</a>).</p> +<p>Now see the following section on how to start and stop the dataflow. When the dataflow is running, be sure to note the statistical information that is displayed on the face of each processor (see <a href="#processor_anatomy">Anatomy of a Processor</a>).</p> </div> </div> </div> </div> <div class="sect1"> -<h2 id="command-and-control-of-dataflow"><a class="anchor" href="user-guide.html#command-and-control-of-dataflow"></a>Command and Control of DataFlow</h2> +<h2 id="command-and-control-of-the-dataflow"><a class="anchor" href="#command-and-control-of-the-dataflow"></a>Command and Control of the DataFlow</h2> <div class="sectionbody"> <div class="paragraph"> <p>When a component is added to the NiFi canvas, it is in the Stopped state. In order to cause the component to @@ -1503,7 +1734,7 @@ be triggered, the component must be star Stopped state, the component can be configured, started, or disabled.</p> </div> <div class="sect2"> -<h3 id="starting-a-component"><a class="anchor" href="user-guide.html#starting-a-component"></a>Starting a Component</h3> +<h3 id="starting-a-component"><a class="anchor" href="#starting-a-component"></a>Starting a Component</h3> <div class="paragraph"> <p>In order to start a component, the following conditions must be met:</p> </div> @@ -1523,13 +1754,13 @@ Stopped state, the component can be conf </li> <li> <p>The component must have no active tasks. For more information about active tasks, see the “Anatomy of …​” -sections under <a href="user-guide.html#monitoring">Monitoring of DataFlow</a> (<a href="user-guide.html#processor_anatomy">Anatomy of a Processor</a>, <a href="user-guide.html#process_group_anatomy">Anatomy of a Process Group</a>, <a href="user-guide.html#remote_group_anatomy">Anatomy of a Remote Process Group</a>).</p> +sections under <a href="#monitoring">Monitoring of DataFlow</a> (<a href="#processor_anatomy">Anatomy of a Processor</a>, <a href="#process_group_anatomy">Anatomy of a Process Group</a>, <a href="#remote_group_anatomy">Anatomy of a Remote Process Group</a>).</p> </li> </ul> </div> <div class="paragraph"> <p>Components can be started by selecting all of the components to start and then clicking the Start icon ( -<span class="image"><img src="images/iconRun.png" alt="Start"></span> +<span class="image"><img src="./images/iconRun.png" alt="Start"></span> ) in the Actions Toolbar or by right-clicking a single component and choosing Start from the context menu.</p> </div> @@ -1539,16 +1770,16 @@ be started, with the exception of those </div> <div class="paragraph"> <p>Once started, the status indicator of a Processor will change to a Play symbol ( -<span class="image"><img src="images/iconRun.png" alt="Run"></span> +<span class="image"><img src="./images/iconRun.png" alt="Run"></span> ).</p> </div> </div> <div class="sect2"> -<h3 id="stopping-a-component"><a class="anchor" href="user-guide.html#stopping-a-component"></a>Stopping a Component</h3> +<h3 id="stopping-a-component"><a class="anchor" href="#stopping-a-component"></a>Stopping a Component</h3> <div class="paragraph"> <p>A component can be stopped any time that it is running. A component is stopped by right-clicking on the component and clicking Stop from the context menu, or by selecting the component and clicking the Stop icon ( -<span class="image"><img src="images/iconStop.png" alt="Stop"></span> +<span class="image"><img src="./images/iconStop.png" alt="Stop"></span> ) in the Actions Toolbar.</p> </div> <div class="paragraph"> @@ -1557,17 +1788,17 @@ will be stopped.</p> </div> <div class="paragraph"> <p>Once stopped, the status indicator of a component will change to the Stop symbol ( -<span class="image"><img src="images/iconStop.png" alt="Stop"></span> +<span class="image"><img src="./images/iconStop.png" alt="Stop"></span> ).</p> </div> <div class="paragraph"> <p>Stopping a component does not interrupt its currently running tasks. Rather, it stops scheduling new tasks to -be performed. The number of active tasks is shown in the top-right corner of the Processor (see <a href="user-guide.html#processor_anatomy">Anatomy of a Processor</a> +be performed. The number of active tasks is shown in the top-right corner of the Processor (see <a href="#processor_anatomy">Anatomy of a Processor</a> for more information).</p> </div> </div> <div class="sect2"> -<h3 id="enabling-disabling-a-component"><a class="anchor" href="user-guide.html#enabling-disabling-a-component"></a>Enabling/Disabling a Component</h3> +<h3 id="enabling-disabling-a-component"><a class="anchor" href="#enabling-disabling-a-component"></a>Enabling/Disabling a Component</h3> <div class="paragraph"> <p>When a component is enabled, it is able to be started. Users may choose to disable components when they are part of a dataflow that is still being assembled, for example. Typically, if a component is not intended to be run, the component @@ -1578,21 +1809,21 @@ configuration) and inadvertently were ne <div class="paragraph"> <p>When it is desirable to re-enable a component, it can be enabled by selecting the component and clicking the Enable icon ( -<span class="image"><img src="images/iconEnable.png" alt="Enable"></span> +<span class="image"><img src="./images/iconEnable.png" alt="Enable"></span> ) in the Actions Toolbar. This is available only when the selected component or components are disabled. Alternatively, a component can be enabled by checking the checkbox next to the “Enabled” option in the Settings tab of the Processor configuration dialog or the configuration dialog for a Port.</p> </div> <div class="paragraph"> <p>Once enabled, the component’s status indicator will change to either Invalid ( -<span class="image"><img src="images/iconAlert.png" alt="Invalid"></span> +<span class="image"><img src="./images/iconAlert.png" alt="Invalid"></span> ) or Stopped ( -<span class="image"><img src="images/iconStop.png" alt="Stopped"></span> +<span class="image"><img src="./images/iconStop.png" alt="Stopped"></span> ), depending on whether or not the component is valid.</p> </div> <div class="paragraph"> <p>A component is then disabled by selecting the component and clicking the Disable icon ( -<span class="image"><img src="images/iconDisable.png" alt="Disable"></span> +<span class="image"><img src="./images/iconDisable.png" alt="Disable"></span> ) in the Actions Toolbar, or by clearing the checkbox next to the “Enabled” option in the Settings tab of the Processor configuration dialog or the configuration dialog for a Port.</p> </div> @@ -1601,26 +1832,26 @@ of the Processor configuration dialog or </div> </div> <div class="sect2"> -<h3 id="Remote_Group_Transmission"><a class="anchor" href="user-guide.html#Remote_Group_Transmission"></a>Remote Process Group Transmission</h3> +<h3 id="Remote_Group_Transmission"><a class="anchor" href="#Remote_Group_Transmission"></a>Remote Process Group Transmission</h3> <div class="paragraph"> <p>Remote Process Groups provide a mechanism for sending data to or retrieving data from a remote instance -of NiFi. When a Remote Process Group (RPG) is added to the canvas, it is added with the Transmision Disabled, +of NiFi. When a Remote Process Group (RPG) is added to the canvas, it is added with the Transmission Disabled, as indicated by the icon ( -<span class="image"><img src="images/iconTransmissionInactive.png" alt="Transmission Disabled"></span> +<span class="image"><img src="./images/iconTransmissionInactive.png" alt="Transmission Disabled"></span> ) in the top-left corner. When Transmission is Disabled, it can be enabled by right-clicking on the RPG and clicking the “Enable Transmission” menu item. This will cause all ports for which there is a Connection to begin transmitting data. This will cause the status indicator to then change to the Transmission Enabled icon ( -<span class="image"><img src="images/iconTransmissionActive.png" alt="Transmission Enabled"></span> +<span class="image"><img src="./images/iconTransmissionActive.png" alt="Transmission Enabled"></span> ).</p> </div> <div class="paragraph"> <p>If there are problems communicating with the Remote Process Group, a Warning indicator ( -<span class="image"><img src="images/iconAlert.png" alt="Warning"></span> +<span class="image"><img src="./images/iconAlert.png" alt="Warning"></span> ) may instead be present in the top-left corner. Hovering over this Warning indicator with the mouse will provide more information about the problem.</p> </div> <div class="sect3"> -<h4 id="Remote_Port_Configuration"><a class="anchor" href="user-guide.html#Remote_Port_Configuration"></a>Individual Port Transmission</h4> +<h4 id="Remote_Port_Configuration"><a class="anchor" href="#Remote_Port_Configuration"></a>Individual Port Transmission</h4> <div class="paragraph"> <p>There are times when the DFM may want to either enable or disable transmission for only a specific Port within the Remote Process Group. This can be accomplished by right-clicking on the Remote Process Group @@ -1629,7 +1860,7 @@ configured:</p> </div> <div class="imageblock"> <div class="content"> -<img src="images/remote-group-ports-dialog.png" alt="Remote Process Groups"> +<img src="./images/remote-group-ports-dialog.png" alt="Remote Process Groups"> </div> </div> <div class="paragraph"> @@ -1644,7 +1875,7 @@ be shown.</p> permissions and that the Remote Process Group’s flow is current. This can be checked by closing the Port Configuration Dialog and looking at the bottom-right corner of the Remote Process Group. The date at which the flow was last refreshed is shown. If the flow appears to be outdated, it can be updated by right-clicking -on the Remote Process Group and selecting “Refresh flow.” (See <a href="user-guide.html#remote_group_anatomy">Anatomy of a Remote Process Group</a> for more information).</p> +on the Remote Process Group and selecting “Refresh flow.” (See <a href="#remote_group_anatomy">Anatomy of a Remote Process Group</a> for more information).</p> </div> <div class="paragraph"> <p>Each Port is shown with the Port name, followed by its description, currently configured number of Concurrent @@ -1653,14 +1884,14 @@ to turn the Port on or off. Those Ports </div> <div class="imageblock"> <div class="content"> -<img src="images/remote-port-connection-status.png" alt="Remote Port Statuses"> +<img src="./images/remote-port-connection-status.png" alt="Remote Port Statuses"> </div> </div> <div class="paragraph"> <p>The on/off switch provides a mechanism to enable and disable transmission for each Port in the Remote Process Group independently. Those Ports that are connected but are not currently transmitting can be configured by clicking the pencil icon ( -<span class="image"><img src="images/iconEdit.png" alt="Edit"></span> +<span class="image"><img src="./images/iconEdit.png" alt="Edit"></span> ) below the on/off switch. Clicking this icon will allow the DFM to change the number of Concurrent tasks and whether or not compression should be used when transmitting data to or from this Port.</p> </div> @@ -1669,36 +1900,36 @@ or not compression should be used when t </div> </div> <div class="sect1"> -<h2 id="navigating"><a class="anchor" href="user-guide.html#navigating"></a>Navigating within a DataFlow</h2> +<h2 id="navigating"><a class="anchor" href="#navigating"></a>Navigating within a DataFlow</h2> <div class="sectionbody"> <div class="paragraph"> -<p>NiFi provides various mechanisms for getting around a dataflow. The <a href="user-guide.html#User_Interface">NiFi User Interface</a> section discussed various ways to navigate around -the NiFi graph; however, once a flow exists on the graph, there are additional ways to get from one component to another. The <a href="user-guide.html#User Interface">[User Interface]</a> section showed that when multiple Process Groups exist in a flow, breadcrumbs appear under the toolbar, providing a way to navigate between them. In addition, to enter a Process Group that is currently visible on the graph, simply double-click it, thereby "drilling down" into it. Connections also provide a way to jump from one location to another within the flow. Right-click on a connection and select "Go to source" or "Go to destination" in order to jump to one end of the connection or another. This can be very useful in large, complex dataflows, where the connection lines may be long and span large areas of the graph. Finally, all components provide the ability to jump forward or backward within the flow. Right-click any component (e.g., a processor, process group, port, etc.) and select either " Upstream connections" or "Downstream connections". A dialog window will open, showing the available upstream or downstream connections that the user may jump to. This can be especially useful when trying to follow a dataflow in a backward direction. It is typically easy to follow the path of a dataflow from start to finish, drilling down into nested process groups; however, it can be more difficult to follow the dataflow in the other direction.</p> +<p>NiFi provides various mechanisms for getting around a dataflow. The <a href="#User_Interface">NiFi User Interface</a> section discussed various ways to navigate around +the NiFi canvas; however, once a flow exists on the canvas, there are additional ways to get from one component to another. The <a href="#User Interface">[User Interface]</a> section showed that when multiple Process Groups exist in a flow, breadcrumbs appear under the toolbar, providing a way to navigate between them. In addition, to enter a Process Group that is currently visible on the canvas, simply double-click it, thereby "drilling down" into it. Connections also provide a way to jump from one location to another within the flow. Right-click on a connection and select "Go to source" or "Go to destination" in order to jump to one end of the connection or another. This can be very useful in large, complex dataflows, where the connection lines may be long and span large areas of the canvas. Finally, all components provide the ability to jump forward or backward within the flow. Right-click any component (e.g., a processor, process group, port, etc.) and select either "Upstream co nnections" or "Downstream connections". A dialog window will open, showing the available upstream or downstream connections that the user may jump to. This can be especially useful when trying to follow a dataflow in a backward direction. It is typically easy to follow the path of a dataflow from start to finish, drilling down into nested process groups; however, it can be more difficult to follow the dataflow in the other direction.</p> </div> </div> </div> <div class="sect1"> -<h2 id="monitoring"><a class="anchor" href="user-guide.html#monitoring"></a>Monitoring of DataFlow</h2> +<h2 id="monitoring"><a class="anchor" href="#monitoring"></a>Monitoring of DataFlow</h2> <div class="sectionbody"> <div class="paragraph"> <p>NiFi provides a great deal of information about the status of the DataFlow in order to monitor the health and status. The Status bar provides information about the overall system health -(See <a href="user-guide.html#status_bar">[status_bar]</a> above for more information). Processors, Process Groups, and Remote Process Groups +(See <a href="#status_bar">[status_bar]</a> above for more information). Processors, Process Groups, and Remote Process Groups provide fine-grained details about their operations. Connections and Process Groups provide information about the amount of data in their queues. The Summary Page provides information about all of the components -on the graph in a tabular format and also provides System Diagnostics information that includes disk usage, +on the canvas in a tabular format and also provides System Diagnostics information that includes disk usage, CPU utilization, and Java Heap and Garbage Collection information. In a clustered environment, this information is available per-node or as aggregates across the entire cluster. We will explore each of these monitoring artifacts below.</p> </div> <div class="sect2"> -<h3 id="processor_anatomy"><a class="anchor" href="user-guide.html#processor_anatomy"></a>Anatomy of a Processor</h3> +<h3 id="processor_anatomy"><a class="anchor" href="#processor_anatomy"></a>Anatomy of a Processor</h3> <div class="paragraph"> <p>NiFi provides a significant amount of information about each Processor on the canvas. The following diagram shows the anatomy of a Processor:</p> </div> <div class="paragraph"> -<p><span class="image"><img src="images/processor-anatomy.png" alt="Anatomy of a Processor"></span></p> +<p><span class="image"><img src="./images/processor-anatomy.png" alt="Anatomy of a Processor"></span></p> </div> <div class="paragraph"> <p>The image outlines the following elements:</p> @@ -1726,20 +1957,20 @@ it will also show the Node that emitted <div class="ulist"> <ul> <li> -<p><span class="image"><img src="images/iconRun.png" alt="Running"></span> +<p><span class="image"><img src="./images/iconRun.png" alt="Running"></span> <strong>Running</strong>: The Processor is currently running.</p> </li> <li> -<p><span class="image"><img src="images/iconStop.png" alt="Stopped"></span> +<p><span class="image"><img src="./images/iconStop.png" alt="Stopped"></span> <strong>Stopped</strong>: The Processor is valid and enabled but is not running.</p> </li> <li> -<p><span class="image"><img src="images/iconAlert.png" alt="Invalid"></span> +<p><span class="image"><img src="./images/iconAlert.png" alt="Invalid"></span> <strong>Invalid</strong>: The Processor is enabled but is not currently valid and cannot be started. Hovering over this icon will provide a tooltip indicating why the Processor is not valid.</p> </li> <li> -<p><span class="image"><img src="images/iconDisable.png" alt="Disabled"></span> +<p><span class="image"><img src="./images/iconDisable.png" alt="Disabled"></span> <strong>Disabled</strong>: The Processor is not running and cannot be started until it has been enabled. This status does not indicate whether or not the Processor is valid.</p> </li> @@ -1807,7 +2038,7 @@ time it would have taken to perform the </div> </div> <div class="sect2"> -<h3 id="process_group_anatomy"><a class="anchor" href="user-guide.html#process_group_anatomy"></a>Anatomy of a Process Group</h3> +<h3 id="process_group_anatomy"><a class="anchor" href="#process_group_anatomy"></a>Anatomy of a Process Group</h3> <div class="paragraph"> <p>The Process Group provides a mechanism for grouping components together into a logical construct in order to organize the DataFlow in a way that makes it more understandable from a higher level. @@ -1815,7 +2046,7 @@ The following image highlights the diffe </div> <div class="imageblock"> <div class="content"> -<img src="images/process-group-anatomy.png" alt="Anatomy of a Process Group"> +<img src="./images/process-group-anatomy.png" alt="Anatomy of a Process Group"> </div> </div> <div class="paragraph"> @@ -1883,42 +2114,42 @@ within the Process Group. The following <div class="ulist"> <ul> <li> -<p><span class="image"><img src="images/iconInputPortSmall.png" alt="Input Port" width="16"></span> +<p><span class="image"><img src="./images/iconInputPortSmall.png" alt="Input Port" width="16"></span> <strong>Input Ports</strong>: The number of Input Ports that exist directly within this Process Group. This does not include any Input Ports that exist within child Process Groups, as child groups' ports cannot be accessed directly.</p> </li> <li> -<p><span class="image"><img src="images/iconOutputPortSmall.png" alt="Output Port"></span> +<p><span class="image"><img src="./images/iconOutputPortSmall.png" alt="Output Port"></span> <strong>Output Ports</strong>: The number of Output Ports that exist directly within this Process Group. This does not include any Output Ports that exist within child Process Group as child groups' ports cannot be accessed directly.</p> </li> <li> -<p><span class="image"><img src="images/iconTransmissionActive.png" alt="Transmission Active"></span> +<p><span class="image"><img src="./images/iconTransmissionActive.png" alt="Transmission Active"></span> <strong>Transmitting Ports</strong>: The number of Remote Process Group Ports that currently are configured to transmit data to remote instances of NiFi or pull data from remote instances of NiFi.</p> </li> <li> -<p><span class="image"><img src="images/iconTransmissionInactive.png" alt="Transmission Inactive"></span> +<p><span class="image"><img src="./images/iconTransmissionInactive.png" alt="Transmission Inactive"></span> <strong>Non-Transmitting Ports</strong>: The number of Remote Process Group Ports that are currently connected to components within this Process Group but currently have their transmission disabled.</p> </li> <li> -<p><span class="image"><img src="images/iconRun.png" alt="Running"></span> +<p><span class="image"><img src="./images/iconRun.png" alt="Running"></span> <strong>Running Components</strong>: The number of Processors, Input Ports, and Output Ports that are currently running within this Process Group.</p> </li> <li> -<p><span class="image"><img src="images/iconStop.png" alt="Stopped Components"></span> +<p><span class="image"><img src="./images/iconStop.png" alt="Stopped Components"></span> <strong>Stopped Components</strong>: The number of Processors, Input Ports, and Output Ports that are currently not running but are valid and enabled. These components are ready to be started.</p> </li> <li> -<p><span class="image"><img src="images/iconAlert.png" alt="Invalid Components"></span> +<p><span class="image"><img src="./images/iconAlert.png" alt="Invalid Components"></span>
[... 471 lines stripped ...]
