Thru Node for Distributed Hybrid Architecture
A Managed File Transfer (MFT) Agent
The Thru Node, also referred to as a managed file transfer (MFT) agent, is a key component in creating a distributed hybrid architecture for Thru’s cloud-native managed file transfer workflow. The node or nodes, which are runtimes installed on a server or a cluster of servers, connect to Thru in the cloud.
How Does Thru Node Work?
The on-premises Thru Node complements Thru in the cloud by providing an instance on the network to orchestrate file transfers. Nodes can be used for files traversing a network and for file transfers between systems on a network or between the network and cloud. The primary benefit of this hybrid architecture is to maximize the use of a SaaS model and minimize the on-premises footprint for file transfers across the enterprise landscape.
Note: Thru Node only uses an outbound HTTPS connection for the data and control channels which is easier to manage than SFTP connections.
Using Thru Node in Your Network
Thru Node is a runtime installed on a machine within a network to connect to Thru over an outbound HTTPS connection, usually over port 443. In accordance with its workflow, simply called a flow, the node picks up and drops off files from any path or directory address that it has access rights to on the network.
Note: Thru Node does not need to be installed on the system from which it is picking up or dropping off files. As long as the node has access to the folder path from the machine it is installed on, the node can function.
Understanding Thru Flows
Flows are created using the graphical user interface, known as Thru Flow Studio, or via APIs. A flow is a directional workflow consisting of any number of source and target endpoints. A node can be an endpoint of a flow as a source, target or both. Each endpoint in a flow can have a set of specific processing and file routing rules.
When a flow’s source and target locations are on the same network, the file remains on the network and is not exposed to the internet. The file is moved from the source to target location over the network’s file sharing protocol such as NFS, SMB, etc. The metadata associated with the file transfer is recorded in Thru Audit and transmitted via an outbound connection over HTTPS.
Authentication & Network Firewall Permissions
Thru Node connects to Thru in the cloud over HTTPS with token-based authentication. Connection direction is always from Thru Node to Thru in the cloud. This means no inbound ports are opened in the corporate firewall when the node is installed on an internal network.
Monitoring & Alerting
Thru Node(s) connects with Thru in the cloud via an API and each node has a unique ID. Each time the node requests an update from Thru, it also reports its health in terms of being responsive or not. This status is available via an API that can be consumed by an event or IT service management tool for alerts and remediation.
Thru Node Processing Features
Thru node, in addition to transferring files, also has the capability to apply a range of rules based on the flow endpoint:
- Zip file
- Compress/decompress file
- Archive file at source
- Rename file at source or target
- Trigger files
- File filters
- Date filters
Installation & Deployment
When a node is created in Thru, an installation script (Windows PowerShell or Linux Script) is made accessible via the GUI. The runtime package downloads and installs when the script is executed.
Deploy the node in minutes:
- Create a Thru Node in the web portal and download it.
- A secret key is automatically set up when a new node is created.
- Create a File Share endpoint and connect it with the node.
- Add the node as an endpoint in your file transfer workflows.
Upgrading Thru Nodes
Thru Nodes follow a continuous deployment pipeline and are automatically updated when a new release is pushed by Thru.
Internal and Remote Automated File Transfer Use Cases
Between Systems on a Network
Thru Node(s) connects with Thru in the cloud via an API and each node has a unique ID. Each time the node requests an update from Thru, it also reports its health in terms of being responsive or not. This status is available via an API that can be consumed by an event or IT service management tool for alerts and remediation.
Learn more about controlling internal systematic file transfer from the cloud »
Between Remote Networks and Central Network
Use of Thru Node is also common in retail and distribution network landscapes where remote locations transfer daily business critical data files between core systems on the central network and many remote locations. In some cases, the remote locations number in the thousands.
Read more about the remote file transfer use case »
Using MFT Agent for File Transfer Is Easier for Non-Technical Partners
File Transfer Integration Challenge
A food franchise company receives point-of-sale (POS) information daily from its franchisees. Its franchisees’ personnel are not technical and only have laptops to use.
File Transfer Integration Solution
The franchisees install and use Thru Nodes to transfer POS data. By using the nodes, the company successfully meets its security and ease of use requirements.
