This article describes the settings for storing information for Nexus Timestamp Server in a database. This is only done if audit is required or for other reason, for example, to keep track of amount of requests.
...
| Expand |
|---|
|
Consider these prerequisites: - You shall add database storage of timestamps to the filter chains, since this is not added to the filter chains of the sample configuration. This is necessary to enable database storage. Read more under heading “timestamp.StorageFilter” in Description of filters in Nexus Timestamp Server.
- The Derby database is embedded in Nexus Timestamp server.
- If you use JDBC drivers other than Derby, that is, if you use an external database, place the .jar file containing the JDBC driver in the lib folder of the installation.
- If you use an external database, set up the database schemas beforehand. The tables will be created automatically when the server receives requests.
|
...
| Expand |
|---|
| title | Set database parameters |
|---|
|
- Set these database parameters in timestamp.properties:
| Insert excerpt |
|---|
| Description of filters in Nexus Timestamp Server |
|---|
| Description of filters in Nexus Timestamp Server |
|---|
| nopanel | true |
|---|
|
|
Examples
| Expand |
|---|
| title | Derby (embedded mode) |
|---|
|
| Code Block |
|---|
| title | Example: Derby (embedded mode) |
|---|
| [shared]
# Derby (embedded mode) settings
storage.database.jdbcDriver=org.apache.derby.jdbc.EmbeddedDriver
storage.database.jdbcUrl=jdbc:derby:var/${Service};create=false
storage.database.jdbcUser=app |
|
...
