Skip to main content
The Atoti FRTB uses Spring Boot to manage some configuration properties. Typically these are properties that may change between environments and deployments, for example, development, CI, QA/UAT, and production. The properties are spread over several files, they are located in the folder frtb-application/src/main/resources, and loaded from the classpath:
  • application.yaml
  • application.properties
  • frtb-cloud.properties
  • jwt.properties
  • frtb-config.properties
While application.yaml and application.properties are automatically included as part of Spring Boot, the other files are specified using the @PropertySource annotation. See frtb-config.properties for the list of properties defined in that file.
For details on the external configuration in Spring Boot, including how properties may be changed for different environments, see the Spring Boot documentation.

Web server

Deployment

Datastore partitioning

Config files

CSV loading

FX rates service

Content server

For details on the Content Server in Atoti Server, see Content Server.

FRTB parameter retriever selection

Maturity converter

Discovery requests

Data Load Controller

Data Extraction Engine

Required properties

Additional properties

Feature selection properties

Spring Boot actuator properties

User Detail Service properties

Sign-Off

What-If Engine

What-If File Upload

What-If Datastore

Cloud storage properties

JWT properties

Distribution properties

DirectQuery

DirectQuery’s startup properties can be found in the dedicated DirectQuery Configuration Properties page.

Summing Duplicate Sensitivities

For example, the following will sum sensitivities and PVs for the SASensitivities store, making sure that the currency and a few other fields are the same.

Tracing

The accelerator reports its own spans under the atoti.frtb OpenTelemetry instrumentation scope, distinct from the platform’s atoti.server scope. A client can substitute its own scope or version by declaring an FrtbTracing bean of its own. The accelerator’s own bean is annotated @ConditionalOnMissingBean, so the client bean replaces it.

Virtual hierarchies

Regulatory Book

The following properties can be used to fine-tune the behavior of this feature. See Regulatory Book for details on their purpose.

EBA reporting templates

The following properties can be used to fine-tune the behavior of this feature. See EBA Reporting Templates for details on their purpose.

Additional configuration properties

For Atoti FRTB configuration properties that are not described above — including DirectQuery and other advanced options — see the Additional configuration properties reference.