> ## Documentation Index
> Fetch the complete documentation index at: https://docs.activeviam.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Activating and de-activating cubes

Cubes can be activated or de-activated from the configuration file [**application.yaml**](../../properties/property-files/application-yaml).

## Configuration

### Properties

<table><thead><tr><th>Key</th><th>Value</th><th>Description</th></tr></thead><tbody><tr><td>mr:</td><td /><td /></tr><tr><td> cubes:</td><td /><td>Subsection for Atoti Server cubes.</td></tr><tr><td> enable:</td><td /><td>Subsection for enabling and disabling individual cubes.</td></tr><tr><td> var:</td><td>true</td><td>Enable (<code>true</code>) or disable (<code>false</code>) the Var-ES cube.</td></tr><tr><td> var-summary:</td><td>true</td><td>Enable (<code>true</code>) or disable (<code>false</code>) the Var-ES Summary cube.</td></tr><tr><td> pnl:</td><td>true</td><td>Enable (<code>true</code>) or disable (<code>false</code>) the PnL cube.</td></tr><tr><td> pnl-summary:</td><td>true</td><td>Enable (<code>true</code>) or disable (<code>false</code>) the PnL Summary cube.</td></tr><tr><td> sensi:</td><td>true</td><td>Enable (<code>true</code>) or disable (<code>false</code>) the Sensi cube.</td></tr><tr><td> sensi-summary:</td><td>true</td><td>Enable (<code>true</code>) or disable (<code>false</code>) the Sensi Summary cube.</td></tr><tr><td> market:</td><td>true</td><td>Enable (<code>true</code>) or disable (<code>false</code>) the Market Data Cube.</td></tr><tr><td> common:</td><td>true</td><td>Enable (<code>true</code>) or disable (<code>false</code>) the MRCombinedCube.</td></tr><tr><td>starter:</td><td /><td>Subsection for Atoti Server instance configuration.</td></tr><tr><td> deployment:</td><td /><td>Subsection for customising the node instance.</td></tr><tr><td> type:</td><td>in-memory</td><td><code>in-memory</code> datastore, <code>direct-query</code> database or <code>query-node</code> only.</td></tr><tr><td> transport:</td><td>local</td><td><code>local</code>, <code>netty</code> or <code>none</code> bus.</td></tr></tbody></table>

`starter.deployment.type` could be:

* `in-memory`: Configures the instance to have data cubes that rely on in memory datastore
* `query-node`: Configures the instance to handle only the query cube, aka the common cube
* `direct-query`: Configures the instance to have data cubes that rely on directQuery database

`starter.deployment.transport` could be:

* `local`: The data cubes communication with the query cube uses the local bus.
* `netty`: The data cubes communication with the query cube uses the netty bus.
* `none`: The data cubes use no communication bus, in this case you can’t have any query cube.

(!) To activate or disable the query cube, you should use the property `mr.enable.cubes.common`:

* `true`: The instance will start a query cube (MRCombinedCube).
* `false`: The instance won’t start a query cube, assuming another one will start it.

## Datastore implication

De-activating a cube means that the unused stores will also be de-activated. The following matrix shows the mapping between store and cubes.

<Note>
  The MRCombinedCube does not require a store because it is a query cube.
</Note>

### Standard configuration

<table><thead><tr><th>Store</th><th>Var-ES cube</th><th>Sensi cube</th><th>PnL cube</th><th>Var-ES Summary cube</th><th>Sensi Summary cube</th><th>PnL Summary cube</th></tr></thead><tbody><tr><td><strong>FXRates</strong></td><td>X</td><td>X</td><td>X</td><td>X</td><td>X</td><td>X</td></tr><tr><td><strong>TradeAttributes</strong></td><td>X</td><td>X</td><td>X</td><td /><td /><td /></tr><tr><td><strong>BookParentChild</strong></td><td>X</td><td>X</td><td>X</td><td /><td /><td /></tr><tr><td><strong>BookHierarchy</strong></td><td>X</td><td>X</td><td>X</td><td /><td /><td /></tr><tr><td><strong>LegalEntityParentChild</strong></td><td>X</td><td>X</td><td>X</td><td /><td /><td /></tr><tr><td><strong>LegalEntityHierarchy</strong></td><td>X</td><td>X</td><td>X</td><td /><td /><td /></tr><tr><td><strong>CounterpartyParentChild</strong></td><td>X</td><td>X</td><td>X</td><td /><td /><td /></tr><tr><td><strong>CounterpartyHierarchy</strong></td><td>X</td><td>X</td><td>X</td><td /><td /><td /></tr><tr><td><strong>Counterparties</strong></td><td>X</td><td>X</td><td>X</td><td /><td /><td /></tr><tr><td><strong>Countries</strong></td><td>X</td><td>X</td><td>X</td><td /><td /><td /></tr><tr><td><strong>RiskFactorsCatalogue</strong></td><td>X</td><td>X</td><td>X</td><td /><td /><td /></tr><tr><td><strong>Scenarios</strong><sup id="fnref:1"><a class="footnote-ref" href="#fn:1" role="doc-noteref">1</a></sup></td><td>X</td><td>X</td><td /><td /><td /><td /></tr><tr><td><strong>PnL</strong></td><td /><td /><td>X</td><td /><td /><td /></tr><tr><td><strong>DynamicMaturities</strong></td><td /><td>X</td><td /><td /><td /><td /></tr><tr><td><strong>DynamicTenors</strong></td><td /><td>X</td><td /><td /><td /><td /></tr><tr><td><strong>DynamicMoneyness</strong></td><td /><td>X</td><td /><td /><td /><td /></tr><tr><td><strong>TradeSensitivities</strong></td><td /><td>X</td><td /><td /><td /><td /></tr><tr><td><strong>MarketData</strong></td><td /><td>X</td><td /><td /><td /><td /></tr><tr><td><strong>CorporateAction</strong></td><td /><td>X</td><td /><td /><td /><td /></tr><tr><td><strong>SensiLadders</strong></td><td /><td>X</td><td /><td /><td /><td /></tr><tr><td><strong>MarketShifts</strong></td><td /><td>X</td><td /><td /><td /><td /></tr><tr><td><strong>TradePnLs</strong></td><td>X</td><td /><td /><td /><td /><td /></tr><tr><td><strong>PnLBaseStore</strong></td><td /><td /><td /><td /><td /><td>X</td></tr><tr><td><strong>SensiBaseStore</strong></td><td /><td /><td /><td /><td>X</td><td /></tr><tr><td><strong>BaseStore</strong></td><td /><td /><td /><td>X</td><td /><td /></tr></tbody></table>

## Removing modules from your application

The default MR application includes all modules, with the full project code containing the Sensitivity, Market Data, PnL, VaR-ES, and MRCombined cubes (and Summary versions where applicable).

To remove a module completely, remove the dependency in the MR application `pom.xml` file and modify the `MarketRiskConfig` class to remove the imports of configuration classes.
All efforts have been made to minimize the amount of code changes required to achieve this removal, but some direct imports from the libraries might remain.

***

1. This store is active even if only the PnL cube is activated [↩︎](#fnref:1)