SoftNAS® FlexFiles Architect is a NiFi-based solution with the primary purpose of managing data flows between systems. In particular, SoftNAS' FlexFiles implementation, it controls the flows between SoftNAS Cloud Instances/Virtual Machines it is running on. FlexFiles Architect helps to provide visibility by representing objects moving through the data flow, as well as providing at a glance content information (such as Map of Key/Value attributes, Content/Payload, etc...)
Refer to this figure the above image to help identify specific commands needed through the remainder of this checklist.
SoftNAS® FlexFiles Architect provides insight to where corrections or modifications are required within the various components within the templates. For example, in the image below there are 6 items needing to be addressed within this template. As you proceed through the following sections, key an eye out for these markers to help guide you where issues need to be addressed. Once all the templates have been configured, you should not have any outstanding issues to be addressed.
All flow files arrive and depart through one path. The Processor may copy or modify the flow file. Processors also can generate new flow files to introduce data in the flow. The flow file may be removed from the flow or routed to a downstream relationship for further processing.
Processors can also have properties to help govern behavior. Some properties may be required before the processor can be started. Properties may also have to pass validation before the processor can be started. Processor properties may also have default values.
During the configuration of both the target and source FlexFile templates, you will be providing the specific details to successfully move objects through FlexFiles Nifi between SoftNAS Instances/Virtual Machines. Create a table with the below information, to better plan your deployment. These details will be utilized to illustrate how to configure the FlexFiles templates for both the Target and Source Nodes.
| Node Name | IP Address | Volume 1 | Volume 2 | ||
|---|---|---|---|---|---|
| Source 1 | xx.xx.xx.xx (public IP address) | Name of Volume (for example NY-ENG) | Name of Volume (for example NY-QA) | ||
Source 2 | xx.xx.xx.xx (public IP address) | Name of Volume (for example TX-ENG) | Name of Volume (for example TX-QA | ||
| Target | xx.xx.xx.xx (public IP address) | Location and Name of Volumes - For example: | Tenn/NY-ENG | Location and Name of Volumes - For example: | Tenn/NY-QA |
| Tenn/TX-ENG | Tenn/TX-QA | ||||