Installing and Configuring the Auditing and Reporting Module
Refer to Installing EFT Server, Administrator, and Modules for the procedure for installing ARM.
Refer to System Requirements before installing.
Installation and configuration of the module consists of:
-
Running the EFT Server installer. The Auditing and Reporting module is normally installed and configured when you install EFT Server. If you did not install it when you installed EFT Server, you can run the installer again, 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 Server needs full DB Owner access to the auditing database to set up the schema. During updates or upgrades, EFT Server needs full DB Owner access to update the schema. Once it is set up, EFT Server only needs to be able to read, write, and execute stored procedures.
|
-
Activating the software with a serial number that includes the ARM
-
Enabling EFT Server to record data
For the procedure for creating a user at a command prompt on SQL Express 2008, refer to Configuring EFT Server Permissions in SQL Server.
Refer to the following topic for more information about installing ARM:
-
For information about configuring an external SQL database to capture the auditing data, refer to Configuring SQL Server as the Auditing Database. This procedure is ONLY used if you did not configure ARM in the installer. All tables are installed regardless of version/features/modules (including the SAT module tables).
-
If you are upgrading from a previous version and are using an external database, you will have to update the table schema manually. This procedure is ONLY used if you did not configure ARM in the installer. All tables are installed regardless of version/features/modules (including the SAT module tables).
-
Refer to AS2 Information in the Database for details of AS2 tables.
Next Step: Configuring the Auditing and Reporting Module
How does EFT Server 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 Server 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 the following registry locations:
SQL 2005
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.<InstanceNumber>\MSSQLServer\SuperSocketNetLib\TCP\
SQL 2008
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: