For information about Globalscape, visit www.globalscape.com.

Installing and Configuring the Auditing and Reporting Module

The Auditing and Reporting module is normally installed and configured when you install EFT. If you did not install it when you installed EFT, you can run the installer again, choose Modify, and then select the Auditing and Reporting check box. (Leave the EFT and EFT Admin Interface check boxes selected; clearing the check boxes will uninstall them.)

Refer to Installing EFT, Administrator, and Modules for the procedure for installing ARM using the EFT installer.

Auditing and Reporting Module (ARM) Requirements

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

• Microsoft .NET Framework 4.0, for ARM upgrades

• 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 is supported with the following SQL Server versions:

  • • SQL Server 2008 R2 Express

    • SQL Server 2008 R2

    • SQL Server 2012

  • Oracle is supported for use with EFT Enterprise only; 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 Enterprise is installed on a 64-bit operating system. EFT Enterprise is supported with the following Oracle versions:

  • • Oracle Database 11g Release 1: 11.1.0.6–11.1.0.7 (patchset as of September 2008)

    • Oracle Database 11g Release 2: 11.2.0.1–11.2.0.3 (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 database, refer to the MSDN article Creating Compressed Tables and Indexes.

  For EFT to connect to any database, the proper drivers need to be installed on the EFT computer. If the right client-side software (driver) is installed on the EFT computer, the Advanced Workflow Engine can make the database connection string to get to that database.

Installation and configuration of the module consists of:

1. Running the EFT installer. The Auditing and Reporting module is normally installed and configured when you install EFT. If you did not install it when you installed EFT, you can run the installer again and choose Modify. On the ARM page of the installer, click Configure Auditing and Reporting. (Follow the procedure in Installing the Server, Administrator, and Modules.)

   During installation, EFT needs full DB Owner access to the auditing database to set up the schema. During updates or upgrades, EFT needs full DB Owner access to update the schema. Once it is set up, EFT only needs to be able to read, write, and execute stored procedures. When upgrading to EFT v6.4.x, if you upgrade the ARM database with the installer, the default schema name is changed to dbo.

2. Activating the software with a serial number that includes ARM

3. Enabling EFT to record data

How does EFT know which TCP/IP port it should use to connect to SQL Server?

When the SQL Server browser service (installed with SQL Server) starts up, it searches the registry for any "named instances" of SQL Server and which TCP ports they're listening on. When a client wants to connect to a named instance, it asks the browser service (on UDP port 1434) on which TCP/IP port is that instance listening. This is how Microsoft implemented support for multiple instances of SQL Server on the same computer. The default instance listens on TCP port 1433. If you have a named instance, the TCP port is dynamically configured.

This is standard SQL Server functionality and doesn't require special port syntax in the EFT connection string or host name. It's all abstracted by the API used, which looks at the host string and figures out whether you're trying to connect to a named instance or a default instance (by determining whether host\instance or just host was specified).

The SQL Server TCP settings are stored in:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.<InstanceName>\MSSQLServer\SuperSocketNetLib\TCP\

For details of how to view/change the TCP information in the SQL Server Configuration Manager, refer to the following MSDN article: http://msdn.microsoft.com/en-us/library/ms177440%28SQL.90%29.aspx

Refer to the following Microsoft topics for more information:

• http://support.microsoft.com/kb/287932

• http://msdn.microsoft.com/en-us/library/ms175483.aspx

• http://msdn.microsoft.com/en-us/library/ms181087.aspx