This document covers the miscellaneous configuration properties used by Workflow Services.
| Name | Description | Default |
|---|---|---|
|
Properties describing the workflows that are available |
|
|
Properties describing the steps (activities) per workflow |
| Name | Description | Default |
|---|---|---|
|
The number of concurrent threads processing workflows on a given replica of WorkflowServices. |
|
|
Maximum amount of time (in milliseconds) that the system will wait to acquire a processor before giving up and rejecting the initiating message |
|
|
Side effects store state for the workflow. Side effects store a range of values that include history elements and initial configuration. When a workflow exceeds this count, it results in workflow failure |
|
|
Amount of time (in milliseconds) to wait before polling again when a message is nacked because there are currently no processing threads available |
|
|
Maximum interval (in milliseconds) between polling attempts for workflows |
|
|
Minimum interval (in milliseconds) between polling attempts for workflows |
|
|
Timeout (in milliseconds) for a workflow that appears to be non-active. A non-active workflow is one that is in |
|
|
The retention period (in milliseconds) for completed or failed workflows |
|
|
The type of binder used for messaging |
|
These properties are for configuring the datasource.
This exposes all of the Spring DataSourceProperties under broadleaf.workflow.datasource.
This is to allow the regular property structure to be restricted to a specific Broadleaf data route.
This exposes all of the Spring LiquibaseProperties under broadleaf.workflow.liquibase.
This is to allow the regular property structure to be restricted to a specific Broadleaf data route.
This exposes all of the Spring JpaProperties under broadleaf.workflow.jpa in addition to the Spring HibernateProperties under broadleaf.workflow.jpa.hibernate.
This is to allow the regular property structure to be restricted to a specific Broadleaf data route.
These are additional properties that define datasource configuration that employs SchemaDelegatingDataSource. This allows through configuration alone a setup that declares multiple datasources (each tied to a schema) backed by a common base datasource. This config is generally employed as part of a flex-package installation where multiple services run together in a single JVM.
broadleaf.workflow.delegating.schema: The schema that borrowed connections should be initialized to in SchemaDelegatingDataSource.
broadleaf.workflow.delegating.delegateRef: The back-reference to another section of configuration that fully describes the base datasource backing the SchemaDelegatingDataSource.