Configure log databases

Log databases store session information for the runtimes. You can connect these databases to monitor sessions from Semarchy xDI Analytics.

Configure a log database

To configure a log database:

  1. In the Analytics toolbar, in the user menu, select Administration.

  2. In the Administration editor, select the Log Databases tab.

  3. Click the Add button.

  4. Specify the Name of your log database.

  5. Configure the connection:

    • Select Standard if you want xDI Analytics to open its own JDBC Connection to the database, and provide the JDBC Driver class, the connection URL as well as the User and Password to connect.

    • Select Datasource if you want xDI Analytics to use a datasource defined in the application server hosting Analytics and provide the Datasource Name

  6. Specify the Schema name, and if needed, the tables Prefix.

  7. Test the connection.

  8. Select Show in logs selection to have this log database appear in the profile selector.

  9. Save the Editor

ana parameters log database

Make sure to configure your network to allow the Analytics server to access the database host and port.

You can automatically fill-in the log database information by connecting to a runtime using the database.

Click the Autoinit button and specify the runtime host, port and credentials to retreive that runtime’s log database configuration.

Make sure to add the JDBC driver required for the log database in the /jdbc subdirectory of the folder defined in the XDI_ANALYTICS_WEBAPP_HOME variable. See Add JDBC drivers.

Add JDBC drivers

The connection to the log databases goes through JDBC drivers. You have to add the JDBC driver corresponding to the log database provider inside xDI Analytics. If you are using the built-in database, add the related HSQL JDBC driver.

Add the JDBC drivers in the /jdbc subdirectory of the folder defined in the XDI_ANALYTICS_WEBAPP_HOME.

Semarchy xDI Runtime versions prior to 2023.4.0 used a built-in H2 database to store the session log. If you have one of those databases, add the H2 JDBC driver version 1.2.140, and move the data to a different database provider such as HSQL as soon as possible.