The Globalscape Quality Assurance (QA) team tested EFT Server and EFT Server Enterprise with a variety of operating systems, software, and hardware. It is possible for EFT Server to function with other software and hardware than those listed below, but is approved for use only with the software/hardware listed below.
EFT Server is supported on the following operating systems:
Windows Server 2003 R2
Windows Server 2008 R2 (Standard, Enterprise, and Datacenter editions)
Windows Server 2012
1 GB RAM (More RAM could be required for high-density, non-EDI file transfers over the AS2 protocol. AS2 transfers can use up to 40% of the Server's RAM for concurrent file transfers.)
EFT Server and DMZ Gateway must be installed on separate computers (For details of DMZ Gateway system requirements, refer to "System Requirements for DMZ Gateway" in the DMZ Gateway help documentation.)
If EFT Server will be monitoring Samba network shares, version 3.0.25 of Samba is required.
Make sure the Windows Firewall on the EFT Server computer is not blocking Web access. In most Windows operating systems, the Windows Firewall is turned on by default.
The EFT Server service runs under a user account, which must have full administrative rights to the folder in which you install EFT Server. With administrative rights, the service can save all of your settings. If the service does not have administrative rights, you will lose settings and user accounts whenever you restart the EFT Server service, and you will need to reset permissions on the computer on which the EFT Server service is running.
The administration interface must be installed on the same computer as EFT Server, 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.)
Windows XP Professional, Windows Server 2003, Windows Server 2008 R1&2 (Standard, Enterprise, and Datacenter editions) x86-64, and Windows 7
50 MB of free RAM, minimum
1024x768 resolution or higher display
Microsoft® ActiveX Data Objects (ADO)
Microsoft SQL Server 2008 R2 Native Client is installed automatically, regardless of whether SQL Server will be used (so that ADO will work with IPv6).
3GB minimum hard drive space for the initial database size. Space requirements for transactions depend on estimated EFT Server activity, number of users, installed modules. A general estimate is 3MB to 5 MB per 1000 files uploaded.
PDF-viewing software (such as Adobe Reader) to view PDFs of reports.
Access to a SQL Server or an Oracle database.
The installer includes SQL Server 2008 R2 Express for both 32- and 64-bit operating systems (intended for evaluation purposes only). For SQL Server system requirements, refer to http://www.microsoft.com/sqlserver/en/us/learning-center/resources.aspx. EFT Server is supported with the following SQL Server versions:
SQL Server 2008 R2 Express
SQL Server 2008 R2
Oracle requires EFT Server Enterprise; refer to Oracle's documentation regarding Oracle system requirements. Be sure to reboot after you install the Oracle Data Access Components (ODAC). You need to use the 32-bit ODAC, even if EFT Server Enterprise is installed on a 64-bit operating system. EFT Server Enterprise is supported with the following Oracle versions:
Oracle Database 10g Release 2: 10.2.0.1–10.2.0.5 (patchset as of April 2010)
Oracle Database 11g Release 1: 126.96.36.199–188.8.131.52 (patchset as of September 2008)
Oracle Database 11g Release 2: 184.108.40.206–220.127.116.11 (patchset as of September 2011)
A good database maintenance plan is important to keeping space requirements to a minimum (aging/archiving/warehousing/truncating old data).
For better database performance, follow the standard SQL/Oracle tuning guidelines in their user documentation. See also Purging Data from the Database.
If you are using SQL Server 2008 Developer and Enterprise editions for your EFT Server database, refer to the MSDN article Creating Compressed Tables and Indexes.
For EFT Server to connect to any database, the proper drivers need to be installed on the EFT Server computer. If the right client-side software (driver) is installed on the EFT Server computer, the Advanced Workflow Engine can make the database connection string to get to that database.
Microsoft .NET Framework 4.0 or greater
More RAM could be required for high-density, non-EDI file transfers. AS2 transfers can use up to 40% of the Server's RAM for concurrent file transfers.
Microsoft .NET Framework 4.0
Refer to the System Requirements in the DMZ Gateway documentation.
Refer to the System Requirements in the Secure Ad Hoc Transfer module documentation.
For information regarding system requirements for the Web Transfer Client, refer to System Requirements for Web Transfer Client.