Skip to main content
Feedback

MFT node minimum requirements

To connect to data locations on your local network, install Node on a computer within that network.

The following sections provide details on requirements for Node installation. Reviewing these requirements help prevent potential performance bottlenecks and ensure consistent integration process execution.

Requirements vary based on intended use and application.

Incorporating file processing options, such as encryption and compression, into flow configurations requires additional hardware resources.

Tested Operating Systems

For Windows

info
  • Make sure you're running the latest version of Windows.
  • Requires PowerShell 5.1 (or greater)
  • Requires Windows Task Scheduler

For Linux

  • Ubuntu 18.04 / 20.04 / 20.04.4

  • RedHat 7.9 / 8.6 / 9.2

  • Amazon Linux

  • SUSE Linux Enterprise Server (SLES) 10.200.1.4

Minimum hardware requirements

The following are the minimum hardware requirements to run the MFT Node:

  • Processor: You need a processor that's at least 1.8 GHz and 64-bit. If you're dealing with only a few tasks or small files, 2 CPU cores are enough. For heavier workloads or larger files, go for 4 CPU cores.
  • RAM: You should have at least 8 GB of RAM for basic tasks. If you're processing files (like encrypting, decrypting, compressing, or decompressing), aim for 16 GB.
  • Hard Disk Space: The amount of space you need depends on how you configure your file transfers. For local network transfers, aim for at least 100 GB. If you're dealing with a large number of files or particularly large ones, you may need up to 1 TB. Remember, if you're processing files, double the space you think you need. This includes space for storing archived files.
  • Internet Connection: You need to have a persistent high-speed internet connection, such as cable, DSL, or fiber optics, that supports outbound HTTPS. This allows the MFT Node to send and receive files securely. Make sure your network allows this connection to the MFTcloud and between your LAN devices. Check with your Network Administrator and Security Professional to make sure your setup meets these requirements.
  • Local Connections: You must have the appropriate LAN connectivity and security permissions to access the applications and data locations required for your particular integration scenarios.

Support:

  • It's crucial to adhere to these minimum requirements and allocate sufficient hard drive space for optimal MFT Node functionality. MFT Customer Success provides support within the context of meeting these specifications. If your MFT Node fails to meet the minimum requirements, additional assistance may not be available, and you may encounter performance issues or functionality limitations.

  • MFT Nodes offers integrated support for operating on machines configured with proxies.

caution

Antivirus and malware scanning are not included with the Node. You will need to set up your own solution on the machines where the Node is installed.

Resource requirements

For configuring an MFT node, the following are the resource requirements:

  • Compute capacity guidelines:

    When configuring an MFT node, it is critical to ensure sufficient computing capacity for optimal performance.

  • Dedicated computing resources:

    • The MFT node requires dedicated computing resources to maintain consistent and reliable performance

    • Minimum recommended allocation: 4 CPU cores when co-located with other applications

    • Avoid placing the MFT node on servers running resource-intensive applications such as:

      • Database servers
      • Enterprise resource planning (ERP) systems
      • Heavy data processing applications

  • Performance considerations:

    caution

    Sharing computational resources can significantly impact the integration process execution speed and reliability.

  • Recommended configuration:

    1. Ideally, deploy the MFT node on a dedicated server
    2. If co-located, ensure:
    • Minimum 4 CPU cores are exclusively available to the node
    • Sufficient memory allocation per existing minimum requirements
    • Limited concurrent resource-consuming processes

Best practices

  • Regularly monitor node performance
  • Conduct periodic resource utilization assessments
  • Adjust server configuration to maintain optimal integration performance
On this Page