Blueprint Developer Manual / 4.2.5.1 In-Memory configuration for Studio Server

Blueprint Developer Manual / Version 2412.0

4.2.5.1 In-Memory configuration for Studio Server

The recommended way to enable the in-memory configuration for CoreMedia Studio Server, is to activate the in-memory Spring profile. This will load the in-memory properties from the application-in-memory.properties. For details, see the official Spring Boot documentation.

For starting the Studio Server locally via an IDE or the Spring Boot Maven plugin, the Spring profiles to be activated are most likely dev,local,in-memory in that order.

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 (zero), 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.11. Studio Configuration Properties for In-Memory Store

Search Results

Table Of Contents

Filter

Blueprint Developer Manual / Version 2412.0

4.2.5.1 In-Memory configuration for Studio Server

Search Results