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).
These configuration files include timestamp service configuration:
filters.properties – Includes global timestamp service settings, such as filters that shall be used by all timestamp services and not configured separately per timestamp service. Located in <conf>/services.
service.properties – Includes definition of filters that are uniquely configured for each timestamp service. Also includes configuration of all polices and chains for the timestamp service. Located in <conf>/services/<service identifier>.