Manual Configuration

This section walks you through integrating Atoti Limits with the Atoti Server Java API.

Configurations in the module

In application.yml, configure the following properties:

Atoti Server Instance parameters

Some parameters are needed in order to allow Atoti Limits to discover and communicate with the connected Atoti Server Instance.

Solution Authentication

The encoded authentication is needed for Atoti Limits to be able to communicate with the connected Solution. This encoded string can easily be created using Java’s java.util.Base64 utility. The format of the encoded authentication is “user:password”. This encoded string will be used in the REST request header when communicating between different components remotely.

Here’s an example of how to generate the string using Java:

String encodedAuth = Base64.getEncoder().encodeToString(("user:password").getBytes())
// Value of encoded auth:
encodedAuth = "dXNlcjpwYXNzd29yZA=="

Here’s an example snippet of what these properties look like in the application.yml file:

limits:
    connected-server:
        url:
            map:
                MRA: 'http://localhost:10010/risk-activepivot/activeviam/pivot/rest/v8/cube'
                FRTB: 'http://localhost:8080/frtb-starter/activeviam/pivot/rest/v8/cube'
        kpi-path:
            map:
                FRTB: 'properties/property-files/kpis'
        as-of-date:
            map:
                MRA: 'AsOfDate@Date@Dates', 'FRTB': 'AsOfDate@Date@Dates'
        auth:
            map:
                MRA: `dXNlcjpwYXNzd29yZA==`, 'FRTB': `dXNlcjpwYXNzd29yZA==`
    rest-url: http://localhost:3090/limits/rest/v2/
    auth: dXNlcjpwYXNzd29yZA==

content:
    server:
        url: http://localhost:8080/frtb-starter/activeviam/content/rest/v7
        auth: dXNlcjpwYXNzd29yZA==

Path to the incident directory

limits.incident.output-data-dir=${input.data.root.dir.path}/data
limits.task-scheduler.thread-pool-size=4

Intraday Observation Frequency

Alert task is automatically scheduled based on the following setting:

• limits.alert-task.sample-rate-cron=0 */5 * * * *

Parent-Child hierarchies

For Scopes of Parent-Child hierarchies, the hierarchy name can optionally be provided. However, if there are multiple hierarchies that contain the same level name, then the hierarchy will need to be specified with the level name. The format for this is: @=. Example: Level 5@BookHierarchy=IR_TRADING.

Testing properties

Target directory for Export

limit_export.target_dir=extractionOutput

Test file’s path for Upload

limit_upload.file_path=limits_approve_uploadTest.csv

Reference Data

• limits_approve_mra.csv is for Atoti Market Risk. By default, it is located under limits-starter/src/test/resources/data-samples/data/2018-09-28 and loaded during startup.
• limits_approve_frtb.csv is for Atoti FRTB, located in limits-starter/src/test/resources/data-samples/data/. Please relocate it to the “date” folder if you run Atoti Limits with FRTB.

Changes in Atoti Server

In order for Atoti Server to work with the module, Solutions need to add the following:

Include the dependencies in the pom.xml

For the LevelPath restful endpoint:

<dependency>
         <groupId>com.activeviam.apps</groupId>
         <artifactId>services</artifactId>
         <version>1.15.0-AS6.0</version>
   </dependency>

LookupPostProcessor:

Depending on your Atoti Server version, import the appropriate artifact according. For 5.11 and 6.0:

       <dependency>
            <groupId>com.activeviam.limits</groupId>
            <artifactId>lookup-post-processor-ap511</artifactId>
            <version>{LIMIT MODULE VERSION}</version>
        </dependency>

       <dependency>
            <groupId>com.activeviam.limits</groupId>
            <artifactId>lookup-post-processor-ap60</artifactId>
            <version>{LIMIT MODULE VERSION}</version>
        </dependency>

Register the LookUpPostProcessor

The LookUpPostProcessor needs to be registered within Atoti Server for Atoti Server to be able to use it. You can register the LookUpPostProcessor statically anywhere in your Atoti Server configuration with the following:

      LookUpPostProcessor.addMeasureToRegistry();

Add the LevelPathRestServiceConfig

import com.activeviam.services.levelpath.LevelPathRestServiceConfig;

@Configuration
@Import(value = {
LevelPathRestServiceConfig.class
}

If your AP is running with AP 6.0, the LevelPath config should look like this:

import com.activeviam.services.levelpath.LevelPathRestService;
@Configuration
@Import(value = {
        LevelPathRestService.class
}

contextValueManager.setActivePivotContentService(this.apCSConfig.activePivotContentService());

Startup Sequence Matters

As Atoti Limits creates the KPI in the business cubes automatically, it is important to start up the business Atoti Server instances fully before starting up Atoti Limits.