Skip to main content
Version: 5.2.0.1

Messagestore

Group "Message Store"​

This group defines the storage configuration for mass data. It is primarily relevant for the Designer, which lacks a database for data storage. Mass data is handled by segmenting larger data sets into smaller units. This section outlines the configuration for storing these smaller units.

ParameterDescription
blob.sizeIf the size of a message (in KB) reaches this limit, it is automatically written to the temporary directory.
blob.tempDirectory serving as a temporary storage location for messages.
lockingDefines the locking method: DISABLED = no locking, QUEUE = only queued messages are locked, DEFAULT = default method, OPTIMIZED = reference counting used for locks when possible.
locking.optimized.orphancheck.reduced.pollingtimeDuration (in seconds) Orchestra waits between two orphan checks if orphans were identified in the previous run.
locking.optimized.orphancheck.standard.pollingtimeFrequency (in seconds) with which Orchestra checks for orphaned lock entries that must be released.
locking.optimized.unlock.queue.sizeMaximum number of unlock requests that can be queued in memory; beyond this, the orphan check handles unlocking.
message.encryptedEnables encryption of Orchestra messages.
message.encrypted.keyChangeTimeInterval (in hours) for generating a new encryption key. Valid range: 12–240 hours.
message.leasetimeDefault lease time (in minutes) a message remains in the message store unless referenced.
page.pathDirectory where Orchestra stores pages of mass data messages.
page.typeDefines whether mass data message pages are stored in the database or the filesystem.
skip.cdata.errorsIf true, invalid characters in a CDATA section are ignored.
temporary.message.folderDirectory where Orchestra can store temporary messages.
temporary.message.leasetimeDuration (in minutes) Orchestra retains temporary messages before removal.