Blueprint Developer Manual / Version 2310
Table Of Contents
The recommended way to enable the in-memory configuration for Studio,
is to create a Spring application configuration file, like application-<profileName>.properties, and start
the Studio with the corresponding Spring profile activated. See
Spring Boot Documentation
for further information.
The configuration file has to contain the following properties:
elastic.core.persistence=memory mongodb.models.create-indexes=false repository.caplist.connect=true repository.caplist.factory-class-name=com.coremedia.cotopaxi.list.memory.MemoryCapListConnectorFactory
Furthermore, you can configure your Studio server with the following properties so that the in-memory store is read / written from the given file upon application context startup / shutdown. To limit memory usage of the in-memory store, the size per collection map is configured. To be robust against data loss, the in-memory store can be persisted periodically in a given interval.
| Property | Default | Description |
|---|---|---|
|
repository.params[memory.collection.serialization.file] |
null |
In-memory store persistence file name. |
|
repository.params[memory.collection.size] |
5000 |
Number of in-memory map entries per collection. |
|
repository.params[memory.collection.serialization.interval] |
360000 |
Interval in ms in which the in-memory store is persisted periodically to the configured file. If 0, periodic persistence is disabled. |
|
repository.params[memory.collection.selfclearing.names] |
notifications |
A comma separated list of collection names, which will be periodically deleted and re-created, when memory.collection.size is reached. Fast growing collections, which do not contain critical data should be configured as self-clearing collections, for example, notifications. |
Table 4.5. Studio Configuration Properties for In-Memory Store
