Skip to main content
Version: v2026.0.0

This section describes the various FlowerDocs Core configurations to be defined in the application's core.properties file.

General

PropertyDescription
system.admin.usernameSystem account identifier
system.admin.passwordSystem account password, can be encrypted with a secret
token.keyToken shared between FlowerDocs Core, FlowerDocs GUI and ARender HMI
secretSecret used to encode password (optional)
core.contextApplication context

Logging

PropertyDescription
logging.file.nameLog file path and name
logging.level.rootLog level: WARN, ERROR, INFO, DEBUG

OpenSearch

PropertyDescription
opensearch.urisAddresses of the various OpenSearch nodes separated by a ,
opensearch.usernameUser name (optional)
opensearch.passwordUser password (optional)

Redis

PropertyDescription
redis.enabledEnables Redis, a prerequisite for high availability
spring.data.redis.hostHost name Redis
spring.data.redis.portRedis listening port

ARender

PropertyDescription
arender.rendition.nodesAddress of the ARender rendition or a Load Balancer

It is not recommended to modify ARender properties by setting parameters in the core.properties file. Properties that are not defined in the documentation are not qualified by FlowerDocs: the correct operation of the application is therefore not guaranteed with these modifications.

Connection pools and timeouts

The connection pools and timeouts of the main infrastructure components are configurable. Defaults are tuned for a typical load; adjust them per environment.

PropertyDescription
opensearch.pool.max.total / opensearch.pool.max.per.routeOpenSearch HTTP connection pool size (default 200)
opensearch.connect.timeout / opensearch.socket.timeoutOpenSearch connect / read timeout (default 5000 / 60000 ms)
rest.oh.connect.timeout / rest.oh.read.timeoutREST OperationHandler callback timeouts (default 5000 / 30000 ms)
rest.oh.pool.max.total / rest.oh.pool.max.per.routeREST OperationHandler client pool (default 200 / 100)

Security headers

The GUI sends a Content-Security-Policy and browser security headers. Override these only if you embed FlowerDocs, serve assets from a custom CDN, or run a companion application on a non-default port: content.security.policy, content.security.policy.directives, hsts.max.age, referrer.policy, permissions.policy, cross.origin.opener.policy, cross.origin.resource.policy.