Guide to activating and configuring the Atoti FRTB UI SDK, including installation, server setup, settings overrides, and combining with other solution SDKs
Each UI project is designed as an extension of the Atoti UI “host application”. This section explains how you can easily combine these extensions into a running Atoti FRTB application.
The configuration parameter is the entry-point to configuring the Atoti UI “host application”. It is supplied to the activate function that modifies it to add the Atoti FRTB features. If you want to make changes like adding or removing a plugin, changing the application’s title or adding an HOC, you can modify the configuration object after invoking activate.For example:
const extension: ExtensionModule = { activate: async (configuration) => { // default application name configuration.applicationName = "AtotiUI"; ... // changes the application name to {productName} activate({configuration}); // Customized application name configuration.applicationName = "My {productName}"; },};
The activate function accepts a settings and a basSettings argument to let you configure the Atoti FRTB features and the BAS features respectively.
You can use the default values exported from the SDK as an override basis:
When the UI is connecting to several Atoti FRTB servers, you need to pass a settings object for each of the server keys that identifies each server like so: