6 docs tagged with "reporting"

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.

See Configure Release and Trigger Settings.

This topic explains how to create a JDBC export hook in Release, allowing you to export data from the release system to a JDBC-compliant database. For more information, see Release export hooks.

You can use the export hook feature to configure Release to run a Jython script for every release that is about to be archived.

Archiving in Digital.ai Release is a two-stage process that manages completed and aborted releases:

This topic covers the setup of a production environment in Digital.ai Release using an external clustered database for operational and archived data. It also includes configuring PostgreSQL in a hot-standby setup for high availability with standby servers ready to take over if the primary server fails.