Skip to main content
The extension points introduced in version 4.0.0 allow cube schema selections to be customized through Spring Beans without modifying the core application.

Concept

Within Atoti Server, a cube is built on a set of fields defined by a schema selection from a datastore. Most schema selections are configured by default to select all fields in the base store. Therefore, fields added to those stores don’t require a customization to the schema selection. The extension points are intended to support use cases where the default behavior is inappropriate:
  • a field is added to the store for direct queries only, and shouldn’t be included in the cube
  • a key field is added to multiple stores and the references between them, and shouldn’t be selected multiple times
  • the selection of the common stores (e.g. Trade Attributes, BookHierarchy) needs to be changed
  • the selection for an entire datastore needs to be modified
For a custom configuration, all schema selections are configurable through the following beans:
The T class used in the table above is an extension of the Atoti Server core CanUseOtherReference and CanBuild interfaces.

Customizations

The customization Beans are annotated with a @Qualifier, explicitly defining the datastore to which the customization applies. All @Qualifier constants are defined in the SpringConstants class. The following qualifiers are available for the cubes in Atoti Market Risk: For example, to easily add an extra schema selection for the VaR-ES Cube, define a bean as follows:

Suggested Further Reading