Testing the Log Database connection

The database connection information used by Log Server and other reporting tools can be updated on the Web > Settings > Reporting > Log Server page in the Forcepoint Security Manager.

The Log Database Connection section of the page includes a Test Connection button. When you click the button, Log Server performs the following tests:

  1. Log Server retrieves the updated database connection information from the Security Manager.

    If Log Server is stopped, or the network is down between the management server and the Log Server machine, this test fails. If the connection to Log Server fails, an IO exception error is likely to display.

  2. Log Server uses ODBC to create a data source name (DSN) for testing purposes.
  3. Log Server uses the DSN to establish a connection to the Log Database. Log Server checks to see that:
    • A database exists.
    • The database version is correct.
  4. Log Server verifies its database permissions.

    See Log Database Permissions for information about the required database roles and permissions.

  5. Log Server deletes the DSN it created for testing.
  6. Log Server notifies the Security Manager that its tests succeeded.

    If this return notification fails, an IO exception error is likely to display.

In addition, the Security Manager verifies that it can create a JDBC connection to the database. This test may pass even when a Log Server test fails.

The new database connection information is not used until you cache and save your changes. At that point:

  • The new database connection information is saved to the Policy Server configuration file.
  • Log Server creates a permanent DSN (reproducing the temporary DSN created during the connection test).

Restart the Websense TRITON - Web Security service to update reporting tools (like presentation reports) to use the new database connection.