Skip to main content
Version: Release 24.1

Archive database

Release stores completed releases in a database that is separate from the repository: the archived database. Besides the completed releases, metadata for reporting is stored in this database.

For more information about the archiving process, see How archiving works.

In the default setup, an embedded database is used and the data is stored in the XL_RELEASE_SERVER_HOME/archive/ directory.

You must configure the archive database before setting up the repository; that is, before starting Release for the first time. Release does not support automatic migration to a different location or vendor after the schema and data are present in the database.

Configure the archive database (Release 4.8.0 - 7.2.0)​

For Release versions 4.8.0 to 7.2.x, you can use the following products as archive database:

  • Apache Derby (embedded)
  • H2 (embedded)
  • Oracle 11
  • MySQL 4.6

To change the database, do the following before initializing the Release repository:

  1. Ensure that XL_RELEASE_SERVER_HOME/conf/xl-release.conf exists and contains the appropriate configuration. For example:
        xl {
          reporting {
            db-driver-classname = "com.mysql.jdbc.Driver"
            db-url = "jdbc:mysql://mysql-host.db:3306/archive?characterEncoding=UTF-8"
            db-username = "xlrelease"
            db-password = "s3cr3t"
          }
        }
  1. Ensure that the JDBC driver is available. Drivers of embedded databases (H2 and Apache Derby) are provided with Release. Usage of MySQL of Oracle requires appropriate JDBC driver to be added to XL_RELEASE_SERVER_HOME/plugins. You can obtain the driver from the website of the vendor.

Additional database configuration​

Increase maximum allowed packet size in MySQL​

Release supports attachments up to 100 MB. To store large attachments in the archive database, increase the max_allowed_packet configuration option in MySQL. Otherwise, the MySQL server may return "Packet Too Large" errors.

Use UTF-8 collation and charset in MySQL​

Release stores data in UTF-8. To enable the archive database to work with multibyte characters:

  • The MySQL server should be configured with the setting character_set_server=utf8, or
  • The JDBC connection URL should explicitly include the encoding as a URL parameter (characterEncoding=UTF-8)

For more information, refer to Character Sets and Collations in General.

Configure the archive database (Release 7.5.0 and later)​

For setting up the archive database in Release 7.5.0 and later, refer to Configure the Release SQL repository in a database.

Change the location of the embedded archive database​

You can move the Apache Derby database by changing the configuration in XL_RELEASE_SERVER_HOME/conf/xl-release.conf (if this file does not exist, create it). For example:

    xl {
      reporting {
        db-url = "jdbc:derby:/path/to/archive/db;create=true"
      }
    }

If you are already using the archive database, you must move it to the new location while Release is not running.