Server Configuration

The following table lists the server configuration details that can be configured using the wizard.

Server Configuration Properties
Field Name Property in spm-config.

properties

Mandat

ory

Default Value Description
Schema Store Location rta.schema.store No SPM_HOME/config Location on the file system where the server loads the schema files.
L1 Cache Size rta.l1.cache.size No 10000 Size of the L1 cache used to store metric nodes. L1 cache ensures that frequently used data is cached inside the JVM and hence not loaded from the database. The L1 cache uses an LRU algorithm.
Select Advanced Options to configure advanced threadpool options.
Note: If you do not select Advanced Options, the advanced properties take default values. However, if you use Advanced Options, the properties take the last configured values.
Server Configuration Advanced Properties
Field Name Property in spm-config.properties Mandat

ory

Default Value Description
Server Batch Size rta.server.batch.size No 100 Client batches further are batched on the server for processing, for enhanced performance. This property specifies the batch size to use on the server.
Server Batch Size Flush Period (ms) rta.server.batch.flush.period No 5000 Time interval in milliseconds to wait for a server batch to complete. Incomplete batch is still processed at this interval.
Rule Metric Node Cache Size rta.l1.cache.size.rule.metric.nodes No 10000 Size of the L1 cache used to store rule/action state nodes. Larger cache with appropriately large JVM heap (-Xmx setting ) results in better performance.
Session Heartbeat Threshold (ms) rta.config.session.heartbeat.threshold No 60000 Maximum time in milliseconds that a named session can be kept alive, since the last heart beat from client is received.
Snapshot Query Timeout rta.snapshot.query.timeout No 300000 Defines timeout in milliseconds for expiration of snapshot query. If the query is not accessed for the specified duration, it expires after the specified period.
Rules Actions Scan Frequency rta.rules.actions.scan.frequency No 5000 Specifies in milliseconds how often to scan for scheduled actions,