Skip to main content
Feedback

MFT node runtime

The MFT Node serves as a runtime environment, enabling MFT Cloud to effectively coordinate the node's actions, granting direct access to local folders and directory structures within a local area network through the creation of a File Share endpoint or to any other external endpoint type.

External endpoints now have the option to be served by MFT Node in addition to MFT Cloud. When a flow endpoint is served by MFT Node, external file repository connections and file transfers are executed by the Node instead of the Cloud. This ensures that files never reside in MFT Cloud, meeting security, compliance, and performance requirements for specific use cases.

note

If using Node Direct, ensure that external servers permit connections from the IP addresses where MFT Node is deployed.

Following installation onto a local device, the node is subsequently set up to establish communication with a specific instance of MFT.

Utilizing HTTPS with token-based authentication, the MFT Node establishes a connection to MFT Cloud. It's important to note that the connection is unidirectional, originating from the MFT Node and reaching out to the cloud. Consequently, no inbound ports need to be opened within a corporate firewall when the Node is deployed within an internal network environment.

Furthermore, the node enables seamless cross-folder delivery and facilitates local device exports. The management and configuration of this feature are carried out in MFT's Flow Studio and the Organization Endpoint within the cloud.

info

The Node retrieves Orchestration and Configurations through outbound polling over an HTTPS connection on port 443.