This article shows an overview of the Nexus Timestamp Server. Read more in this article: Nexus Timestamp Server.

This is an illustration of a Nexus Timestamp Server system. It consists of two major components: one or more HTTP frontends and one backend.

Timestamp services

Nexus Timestamp Server can contain multiple timestamp services. Such a timestamp service consists of one HTTP frontend, together with its configuration in the backend. A timestamp service has a policy which dispatches to filter chains composed by filters. Read more about this here Description of filters in Nexus Timestamp Server and Filter chains used in Nexus Timestamp Server.

HTTP frontend

The HTTP frontend is accessed by the end-users (requesters). There may be any number of HTTP frontends in a Nexus Timestamp Server system. One frontend, together with its configuration in the backend, represents one timestamp service.

Backend

The backend is the main component of Nexus Timestamp Server. The backend is where all timestamp requests are processed and timestamp responses are generated, according to the configuration per timestamp service. The requests and responses can be stored in a database for audit reasons.

Web interface

Nexus Timestamp Server includes a web interface with access to:

• timestamp service administration
• timestamp services

The web interfaces are addressed using URLs. Each functionality resides in a web application archive (“war”) file, located in the <install>/webapps directory.

Hardware Security Module

See these articles:

• Initialize Hardware Security Module in Timestamp Server

Example scenario