Offer use of archive database

Current Situation

• The Order History, Task History and File Transfer History are available from the JOC Cockpit's database. Related tables are cleaned-up based on the settings for the Cleanup Service.
• Users are fine with limiting the size of the database for the benefit of performant transactions.
• Some users feel the need to access history entries and logs for a longer period.

Desired Behavior

• JOC Cockpit offers use of an archive database.
  • The database connection is specified by a second connection (hibernate configuration file) "reporting database".
  • Use of different DBMS products for reporting database and archive database is allowed.
  • The archive database is used in read-only mode.
  • No relationship between reporting database and archive database is assumed.
  • No availability of the archive database is required: if it is not available then the GUI will notify the user who can switch to using the JOC Cockpit database.
• The History view and File Transfer view offer to switch between reporting database and archive database.
  • Transactions in the reporting database are executed with unchanged speed.
  • Transactions in the archive database can take more time depending on the number of records included.
• The Cleanup Service
  • is extended to optionally move records from the reporting database to the archive database.
  • can be configured to delete records from the archive database from individual settings specifying the retention period for the archive database.