This document covers the miscellaneous configuration properties used by Audit Services.
| Name | Description | Default |
|---|---|---|
|
Configuration controlling the behavior of ingestion of |
|
|
Configuration controlling the behavior for pruning of |
| Name | Description | Default |
|---|---|---|
|
Configuration related to the multithreaded processing of |
|
|
Config related to the |
|
|
Enable or disable the |
|
|
Tip
|
Most of the time, datasource related configuration is handled automatically by the Broadleaf starter architecture at runtime. |
These properties are for configuring the datasource.
This exposes all of the Spring DataSourceProperties under broadleaf.audit.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.audit.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.audit.jpa in addition to the Spring HibernateProperties under broadleaf.audit.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.audit.delegating.schema: The schema that borrowed connections should be initialized to in SchemaDelegatingDataSource.
broadleaf.audit.delegating.delegateRef: The back-reference to another section of configuration that fully describes the base datasource backing the SchemaDelegatingDataSource.