I propose to change the Database solution used in the integrity plugin from Derby to MapDB
PROs:

• MapDB is well known for it's performance and successfully used in several Jenkins plugins.
• The original approach of "one database per job" would still be usable. This includes the handling of different credentials on Job-level
• it is independent of the targeted Integrity-Server version