System Requirements

Globalscape only offers support for EFT with the software/hardware on which we've tested EFT, as described below.

(See also EFT Specifications.)

EFT (Server Service) Requirements

EFT and its modules can be installed on a physical computer, virtualization software such as VMWare, and in the cloud. EFT Arcus is our SaaS offering, hosted on Microsoft Azure.

Max Latency (measured while not under load):

EFT Administration Interface Requirements

The administration interface must be installed on the same computer as EFT, but also can be installed on other computers for remote administration. (Refer to the ARM, AWE, and AS2 requirements below if you plan to use those modules remotely.)

Auditing and Reporting Module (ARM) Requirements

Provider=OraOLEDB.Oracle.1; Data Source=(DESCRIPTION =

(ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = {host value})(PORT = {port})))"

(CONNECT_DATA =(SERVICE_NAME = {database name})));

Persist Security Info=true;PLSQLRSet=1;PwdChgDlg=0;User Id={username};Password={password};

AS2 Module Requirements

Web Transfer Client (WTC) and Workspaces Requirements

The EFT installer is bundled with a compatible version of the WTC.

Advanced Security Module Requirements

Express Security Module Requirements

EFT Outlook Add-In Requirements

DMZ Gateway Requirements

Advanced Workflow Engine Requirements


Accelerate Module Requirements

The requirements for the Accelerate module include:

The Accelerate module/FAST protocol is not supported on Linux versions of DMZ Gateway.

Mobile Transfer Client (MTC) System Requirements

MTC is supported on:

Content Integrity Control Action Requirements

The Content Integrity Control (CIC) Action was tested with:

When using the CIC action, EFT needs to use POST in HTTP requests. Refer to knowledgebase article for information about enabling an advanced property.