Customizing Atoti Market Risk
This page describes the options available for customizing Atoti Market Risk to meet your requirements.
Customization Options
Clients may choose to use Atoti Market Risk “as is” by conforming to published data input file structures and data stores. Alternatively, clients may use Atoti Market Risk purely as a starting point for building a suitable system with additional functionality.
| Customization | Details |
|---|---|
| Adding Maven repositories and extracting the source code before installation, in order to build the entire project. This will build the executable JAR files for Atoti Server and an optimized version of the UI. |
Building & deploying Atoti Market Risk |
| Making changes at start-up to the following components: * Atoti Server * Atoti UI |
Guidelines for developing on Atoti Market Risk |
| Setting a Sign-off workflow, including policies for resolving conflicts | See the Sign-Off Module documentation |
| Managing workflow, security, and persistence settings for What-If simulations | Customizing What-If simulations |
| Exporting and importing bookmarks to and from a directory structure, using a utility called the Bookmark Tool, which is pre-configured in Atoti Market Risk. | Managing bookmarks with the Bookmark Tool |
| Customizing the Datastore outside the standard datastore config class, using the Datastore Helper, a library and API, pre-configured in Atoti Market Risk. | Customizing the Datastore with the Datastore Helper |
| Extending Atoti Market Risk | * Adding New Cube Hierarchies * Adding New KPIs * Adding New Data Loading or Unloading Topics * Configuring measures using Spring Beans * Configuring sources using Spring Beans |
Derivative Works and Clients’ IP
In the project, source code is delivered and IT users are free to make derivative works (which become the clients’ IP) to adapt to their data sources and requirements.