Loading...

XML

Word

Printable

Verification:

Hide

Create a PostgreSQL database for the AlarmServiceDatabases, and change the ReferenceSettings to refer to this database to the following:
<AlarmServiceDatabaseUrl>jdbc:derby:path-to-database</AlarmServiceDatabaseUrl>
<AlarmDatabaseSpecifics>org.bitrepository.common.database.PostgreSQLConnector</AlarmDatabaseSpecifics>

Start the database and the AlarmService.
Then send an AlarmMessage to the AlarmService, and validate that it is properly inserted into the database.
Also validate that it is possible to extract again from the database, e.g. through the web-interface.

Show
Create a PostgreSQL database for the AlarmServiceDatabases, and change the ReferenceSettings to refer to this database to the following: <AlarmServiceDatabaseUrl>jdbc:derby:path-to-database</AlarmServiceDatabaseUrl> <AlarmDatabaseSpecifics>org.bitrepository.common.database.PostgreSQLConnector</AlarmDatabaseSpecifics> Start the database and the AlarmService. Then send an AlarmMessage to the AlarmService, and validate that it is properly inserted into the database. Also validate that it is possible to extract again from the database, e.g. through the web-interface.

We need to move to support a PosgreSQL database for production usage, instead of the current Derby database.

This will also enable the operation guys to use there normal database tools, including the standard backup.

Note that Netarkivet.dk has just made this switch because of stability and performance issues with Derby.