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 has been tested and approved for use only with the software/hardware listed below.
Windows XP Professional, Windows Server 2003 Windows Server 2008 R2 (Standard, Enterprise, and Datacenter editions) x86-64
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.
An Administrator 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 (Standard, Enterprise, and Datacenter editions) x86-64
50 MB of free RAM, minimum
1024x768 resolution or higher display
Microsoft® ActiveX Data Objects (ADO)
SQL Server Express, SQL Server, or Oracle. The installer includes SQL Express 2005 SP2 for both 32- and 64-bit operating systems. (Oracle requires EFT Server Enterprise; see also System Requirements for Using an Oracle Database for detailed Oracle system requirements.)
For SQL Server Express system requirements, refer to http://www.microsoft.com/Sqlserver/2005/en/us/system-requirements.aspx.
For SQL Server 2005 system requirements, refer to http://www.microsoft.com/Sqlserver/2005/en/us/system-requirements.aspx.
For SQL Server 2008 system requirements, refer to http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=66ab3dbb-bf3e-4f46-9559-ccc6a4f9dc19.
EFT Server and EFT Server Enterprise have been tested with SQL Server 2005 and 2008.
EFT Server Enterprise has been tested with Oracle 10g and 11g, but 11g is recommended. (See System Requirements for Using an Oracle Database below.)
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.
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.
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.
Also refer to the help topics Purging Data from the Database and The ARMImporter Tool.
Microsoft .NET Framework 2.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 2.0 or greater
For information regarding system requirements for DMZ Gateway, refer to System Requirements for DMZ Gateway in the DMZ Gateway documentation.
For information regarding system requirements for the Secure Ad Hoc Transfer module, refer to Secure Ad Hoc Transfer Module System Requirements in the SAT documentation.
For information regarding system requirements for the Web Transfer Client, refer to System Requirements for the Web Transfer Client in the WTC documentation.
(Oracle connectivity available in EFT Server Enterprise) EFT Server Enterprise uses the Oracle OLE DB provider to access an Oracle database. The 11g versions (which support Oracle 9.2 and greater) were used in development and testing. For more information, refer to the following Oracle links:
http://www.oracle.com/technology/tech/windows/ole_db/index.html
http://www.oracle.com/technology/docs/tech/windows/ole_db/index.html
The following items are required on a system to use Oracle Provider for OLE DB:
Access to an Oracle Database (Oracle 9.2 or later)
Oracle Client release 11.1 or later and Oracle Net Services (included with Oracle Provider for OLE DB installation).
Redistributable files provided with Microsoft Data Access Components (MDAC) 2.1 or higher are required by the provider. These files are available at the Microsoft Web site: http://www.microsoft.com/data/
Oracle Services for Microsoft Transaction Server release 11.1 or higher. This is required for consumers using Microsoft Transaction Server (MTS) or COM+.
There are 8i and 9 OLE DB providers that should work, but avoid the 10g version. Provider was changed from OraOLEDB.Oracle.1 to MSDAORA.1 due to Oracle Bug #4518457. For more information, refer to http://forums.oracle.com/forums/thread.jspa?messageID=1499744.