The size of the main disk cache of the UAPI

The minimum size of streamed blobs

The number of streaming threads

The server's domain name

The size of the main memory cache of the UAPI

The Content Server's IOR URL

Role mappings are used to replace group names in a process definition file by other group names without having to actually modify the textual definition

The maximum size of cached blobs

Whether to enable navigate through cache of the UAPI. This cache is used for computing read rights on folders in case no explicit read rights are defined and read rights on subfolders force read rights on folders on the path to these folders. Because these computations are expensive and sometimes unnecessary, this flag allows you to ignore navigate-through rights in the Workflow Server.

Define a password for the connection with the Content Management Server.

Pool queue limit.

Pool thread max limit.

Pool thread min limit.

The directory service adapter.

The persistence adapter.

Whether to allow connecting to a live Content Server

Persistence option where archived workflow processes are stored. By default, Elastic Core is used for storage in MongoDB or in its in-memory replacement. Set this to "sql" to store archived processes in the Workflow Server's relational database.

List of exception classes that indicate temporary problems when archiving a workflow process. If one of these exceptions is thrown directly or as cause of another exception in com.coremedia.workflow.common.actions.ArchiveProcessFinalAction, then the Workflow Server will retry archiving with some delay as configured in properties workflow.server.retry-final-actions.*.

This flag allows you to enable the workflow converter while starting Workflow Server

The maximum number of threads executing FinalActions of finished processes. This setting can be changed at runtime with the JMX attribute 'FinalActionsMax'.

The remote action handler.

The initial time interval to wait before retrying the execution of a workflow final action after it failed for the first time. The value must be >= 1 millisecond. The initial interval is multiplied with the configured multiplier for each retry attempt (exponential back-off) until the configured maximum has been reached. This setting is ignored if the exception provides a different value in method RetryableActionException#getDelayBeforeRetry.

The maximum time to wait before retrying a failed execution of a workflow final action. The duration must be larger or equal to the specified initial time to wait. This setting is ignored if the exception provides a different value in method RetryableActionException#getDelayBeforeRetry.

Multiplier for exponential back-off. The value must be >= 1.0. This setting is ignored if the exception provides a different value in method RetryableActionException#getDelayBeforeRetry.

Factor to randomize the effective delay. The value must be >= 0.0 and < 1.0. Use 0.0 for no randomization. For example, a value of 0.1 creates effective delays in the range of plus/minus 10 percent of the computed delay. This also means that the actual delay can be up to 10 percent above the configured max value. This setting is ignored if the exception provides a different value in method RetryableActionException#getDelayBeforeRetry.

Whether the execution of workflow final actions will be retried if a com.coremedia.cap.workflow.plugin.RetryableActionException was thrown. If set to false, retries after these exceptions are disabled completely and this cannot be overridden in the implementation of the RetryableActionException. This setting can be changed at runtime with the JMX attribute 'FinalActionsRetryEnabled'.

The maximum number of retry attempts, after a final action has failed with a com.coremedia.cap.workflow.plugin.RetryableActionException for a finished process instance. When the maximum number of retry attempts is reached, then the action will be skipped and the process instance will be deleted without successful execution of the failed final action. A value of -1 means unlimited retries. A value of 0 disables retries. This setting is ignored if the exception provides a different value in method RetryableActionException#getMaxRetries.

The interval of the session reaper checks.

The timeout until an inactive session is closed.

Possible values: 'true'|'false'|'embedded'

The concurrent sweep mode.

The sweep delay.

Timeout for waiting on running threads on shutdown

Transaction handler idle timeout.

Limits the maximum number of database connections.

If 'true', will retry failed transactions due to a database connection failure. Before retrying, the DB connection will be renewed. This can also be useful in clustered databases to cope with failover switch.

Time to wait before a new attempt is made after a transaction failed due to database connection failure. Must be larger than zero.

If 'true', will retry failed transactions due to a read-only database. Before retrying, the DB connection will be renewed. This can be useful when running on a clustered database (e.g., Amazon Aurora) that dynamically assigns writer and reader instances to cope with failover switch. This is currently only supported on MySQL.

Time to wait before a new attempt is made after a transaction failed due to a read-only DB. Must be larger than zero.

The delay in seconds the Workflow Server waits between retries to connect to the Content Server when starting.

The maximum number of idle sessions to keep in the Content Server session pool.

The time in milliseconds after which an idle session of the Content Server session pool should be closed.

The maximum number of sessions to hold at any time (busy + idle) in the Content Server session pool.

The server's service indicator

Define a user for the connection with the Content Management Server.

Working directory of the workflow-server used to handle custom classes uploaded to the server. Path can be absolute or relative to user.dir system-property.

Configures whether an old but backwards-compatible merge algorithm for merging list properties should be used. This also applies to struct lists. If true, merge conflicts are reported if there are any changes in overlapping regions of list values. This also includes changes in nested property values, for example if there are changes in translatable properties and those properties aren't excluded with workflow.localization.auto-merge.translatable=false, or if the AutoMergeStructListMapKeyFactory is configured to merge a struct list as map, and some non-key properties have changed. An example for the latter would be a conflict caused by removing a link in a master content and a changed annotation property for that link in the derived content. If false, an improved merge algorithm is used for list values, which tries to avoid merge conflicts in more cases.

Configures if translatable properties are automatically merged in translation workflows. If true, changes of translatable properties in a master content are also merged to derived content items by translation workflows, if there are no conflicting changes and the properties haven't been excluded otherwise. Opposed to non-translatable properties, merge conflicts for translatable properties are typically resolved silently in favor of the derived content and do not generate a warning for the user. There are some exceptions, especially when using the legacy list merge algorithm (see property workflow.localization.auto-merge.legacy-list-merge). Even if set to true, translatable properties can still be excluded from auto-merge, for example with extensions:automerge="false" in the document type definition or with a custom implementation of com.coremedia.translate.workflow.AutoMergePredicateFactory.

Endpoint of the process archive in the in-memory setup.

Password to use for process archiving at the endpoint in the in-memory setup.

Username to use for process archiving at the endpoint in the in-memory setup.