Configuring the Auditing and Reporting Module (ARM)

To use Auditing and Reporting with EFT Server, you have to enable the Auditing and Reporting Module (ARM), specify the Host/Instance Name, Database Name, and login information, then specify the action to take in case of database error. The procedure below describes how to configure ARM.

To configure ARM

  1. In EFT Administrator, connect to EFT Server and click the Server tab.

  2. In the left pane, click the Server you want to configure.

  3. In the right pane, click the Auditing tab.

  4. Under Database Audit Settings, select the Enable Auditing and Reporting check box.

  5. In the Host[\Instance Name] box, type the host and instance name in the format host\instance name.

  6. If you are using SQL Server as the Auditing Database, \InstanceName corresponds to SQL Server's notion of named instances, a feature that allows a given computer to run multiple instances of the SQL Server Database Service. For more information, see http://msdn2.microsoft.com/en-us/library/ms165614.aspx .

  7. In the User Name and Password boxes, type the username and password used to connect to the database.

  8. In the Database Name box, type the name of the database to which you are connecting.

  9. Optionally, click Apply and then click Test Connection to test the connection to the database. (You must apply your changes first.)

  10. In the In case of database error area, specify an action for EFT Server to take if there is an error with the database.

  11. Type a Failure notification e-mail address for EFT Server to provide a connection error notification. You can add as many e-mail addresses as needed; separate the addresses with a comma or semicolon. EFT Server uses its global SMTP e-mail settings for SMTP Configuration to send the e-mails, so make sure that those settings are correct.

  12. Database error e-mails contain the following information:

  13. Click Apply to save the changes on EFT Server.

  14. If you are using Windows 2000 for your server installation, you must update MDAC prior to installation. You can find the latest update at:
    http://msdn.microsoft.com/data/ref/mdac/downloads/

    This does not apply to Windows XP or Windows 2003, as they come with a newer version of MDAC that is compliant.