System Requirements

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 Requirements

• Windows XP Professional SP3, Windows Server 2003, Windows Server 2008 R1&2 (Standard, Enterprise, and Datacenter editions) x86-64, and Windows 7

• • RSA SecurID® in EFT Server is supported on Windows 2003 and later only

• 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.

EFT Server Administration Interface Requirements

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

Auditing and Reporting Module (ARM) Requirements

• Microsoft® ActiveX Data Objects (ADO)

• 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 or an Oracle database.

• • The installer includes SQL Server Express for both 32- and 64-bit operating systems (intended for evaluation purposes only).

  • 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). EFT Server Enterprise has been tested with Oracle 10g and 11g, but 11g is recommended. You need to use the 32-bit ODAC, even if EFT Server Enterprise is installed on a 64-bit operating system.

  • 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 on and is supported on SQL Server 2008 R1&2.

  • 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.

AS2 Module Requirements

• 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.

Advanced Workflow Engine (AWE) Module Requirements

• Microsoft .NET Framework 4.0

DMZ Gateway Requirements

Refer to the System RequirementsSystem Requirements in the DMZ Gateway documentation.

Secure Ad Hoc Transfer (SAT) Module

Refer to the System RequirementsSystem Requirements in the Secure Ad Hoc Transfer module documentation.

Web Transfer Client (WTC) Requirements

For information regarding system requirements for the Web Transfer Client, refer to System Requirements for Web Transfer Client.