Acrolinx comes installed with a reporting database for testing the Analytics functionality. In previous server versions, Acrolinx installed an Apache Derby database for that purpose. In version 4.0, Acrolinx changed that default database to H2. If you use the default database, this new database format improves the database performance. However, you should still only use the default database for testing and demonstration purposes. Acrolinx supports different external databases that are more suited for production environments.
If you have previously used the default Apache Derby database, you must migrate the existing reporting data to the H2 database. During the migration, you must back up the old Derby database and restore that backup to the new H2 database. This procedure is only necessary if you use the default Apache Derby database. If you have configured Acrolinx to connect to an external database, you can ignore this procedure.
To migrate your reporting data from a Derby database to an H2 database, follow these steps:
Upgrade your Acrolinx installation to version 4.0.
You find detailed information on upgrading in the Acrolinx Server Administration Guide .
- Stop all servers.
Open your overlay of the following file:
Update the reporting database properties so that they resemble the following example:
reporting.dbType=DERBY reporting.jdbcUser=admin reporting.jdbcPassword=k7hWFD2IJ4dIln35D reporting.jdbcUrl=jdbc:derby:reports;territory=de_DE
If you have never entered the connection details because you always used the default database, you might have to uncomment the existing lines first.
- Start the core server.
Log on to the Dashboard and backup the reporting database.
Create New Backup
When the backup process completes, the new backup is displayed in the Available Backups table.
The backup file is saved on the server computer at the following location:
If you prefer to store your backup somewhere other than the server computer, click Download in the Actions column.
To cancel the backup task, click the Cancel button next to the progress bar.
- Stop the core server.
- Open your overlay of the following file: persistence.properties
- Comment out the connection details you entered in step 4 and save the file.
- Start the core server.
Log on to the Dashboard and import the reporting database backup file.
Locate the backup in the
section, and in the
To restore a backup that is stored on your computer or at a network location, upload the backup file to your server first .
In the security dialog that appears, enter the word
Tip: This type of dialog is an extra precaution to prevent you from overwriting your reporting database unintentionally. When you restore a database backup, all reporting data is overwritten with the data from the backup.
Your data from the previous Derby database is now transferred to the new H2 database.
- Locate the backup in the Available Backups section, and in the Actions column, click Restore .
- Restart the core server.