Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
This article and its sub-articles describe how to configure Nexus Timestamp Server.
There may be multiple timestamp services defined in a Nexus Timestamp Server installation. Each timestamp service is contained in its own sub directory. This makes it possible for a single Nexus Timestamp Server instance to serve multiple timestamp services with different requirements on the Nexus Timestamp Server configuration. Each timestamp service has a service identifier which is the same as the name of the directory that the system uses to map this timestamp service. The service identifier is also used as a part of the URL for the HTTP frontend. Policies, filter chains and filters are all defined in the scope of a timestamp service. Read more here: Policies used in Nexus Timestamp Server.
The Nexus Timestamp Server distribution contains two sample timestamp services, located in the <conf>/services/sample and <conf>/services/sample2 directories.
The properties and behaviour of Nexus Timestamp Server are managed through configuration files. All configuration files are located in <conf> (or a sub directory).
| Expand | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
For more information see System configuration in Nexus Timestamp Server. |
| Expand | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
For more information see Service configuration in Nexus Timestamp Server. |
| Expand | ||
|---|---|---|
| ||
For more information, see Logical timestamp servers in Nexus Timestamp Server. |
Nexus Timestamp Server test client
See Use Nexus Timestamp Server test client.
Hardware Security Module
See Initialize Hardware Security Module in Timestamp Server.
Related information
| Child pages (Children Display) |
|---|