The application.yml file configures the workflow database settings, including initial load, schema, conflicts, and domains.
Location: limits-starter\src\main\resources.
File values
Property
Value
Description
server.port
3090
Port used by the limits server application.
schema.printer
true
management.endpoints.web.exposure.include
“*”
List of the Spring Boot Actuator endpoint exposed in the application.
servlet.session.cookie: name
LIM_JSESSIONID
The cookie name. You can set a unique cookie name here when connecting multiple accelerators.
max-age
PT12H
The maximum expiration time. Must match the value defined in qfs.expiration
Section: content.hibernate
This section configures the Content Service database and connections to the Content Server.
Property
Value
Description
content.hibernate.connection.url
“jdbc:h2:mem:content_service;DB_CLOSE_DELAY=-1”
URL of the Hibernate connection to the content server.
content.hibernate.connection.driver_class
org.h2.Driver
Driver used for the Hibernate connection to the content server.
content.hibernate.dialect
“org.hibernate.dialect.H2Dialect”
SQL dialect used for the Hibernate connection to the content server.
content.hibernate.show_sql
false
Flag used to set up the printing of the SQL queries in the Hibernate logs.
content.hibernate.format_sql
false
Flag used to set up the formatting of the SQL queries in the Hibernate logs.
content.hibernate.hbm2ddl.auto
update
Hibernate DDL generation setup to run on startup against the content server database. NOTE: Remove this line once the table is created.
content.hibernate.hikari.connectionTimeout
30000
Maximum time (in milliseconds) that a client will wait for a connection from the pool (connection to the content server).
content.hibernate.hikari.idleTimeout
60000
Maximum time (in milliseconds) that a connection is allowed to sit idle in the pool (connection to the content server).
content.hibernate.hikari.minimumIdle
1
Minimum number of idle connections that HikariCP tries to maintain in the pool (connection to the content server)
content.hibernate.hikari.maximumPoolSize
10
Maximum size that the pool is allowed to reach, including both idle and in-use connections (connection to the content server).
content.hibernate.hikari.poolName
“content”
User-defined name for the connection pool. Displayed mainly in logging and JMX management consoles to identify pools
Section: JWT configuration
This section configures the JWT parameters used for authentication
Property
Value
Description
activeviam.qfs.jwt.key.public
The RSA key public key encoded in Base64, used to verify the integrity of the tokens.
activeviam.qfs.jwt.key.private
The RSA key private key encoded in Base64, used to sign the tokens.
activeviam.qfs.expiration
43200
The lifetime of the tokens in seconds.
Section: Content Server security configuration
This section configures the Content Service entitlements
Property
Value
Description
contentServer.security.calculatedMemberRole
ROLE_USER
The role users must have to create calculated members in the content server
contentServer.security.kpiRole
ROLE_USER
The role users must have to create KPIs in the content server
contentServer.security.cache.entitlementsTTL
3600
The time to live of the entitlement cache
Section: Activiti History
This section configures the use of the Activiti History. See Activity user guide for details about the Activiti History: https://www.activiti.org/userguide/
Property
Value
Description
spring.activiti.dbHistoryUsed
true
Flag used to enable/disable the Activiti History
spring.activiti.historyLevel
full
Activity History level
Section: Activiti database
This section configures the Activiti database and the connection to the Activiti database.
If true then Hibernate will escape reserved SQL keywords when generating SQL for the Audit Log database
audit-log.datasource.hikari.connectionTimeout
30000
Maximum time (in milliseconds) that a client will wait for a connection from the pool (connection to the Audit Log database).
audit-log.datasource.hikari.idleTimeout
60000
Maximum time (in milliseconds) that a connection is allowed to sit idle in the pool (connection to the Audit Log database).
audit-log.datasource.hikari.minimumIdle
1
Minimum number of idle connections that HikariCP tries to maintain in the pool (connection to the Audit Log database).
audit-log.datasource.hikari.maximumPoolSize
10
Maximum size that the pool is allowed to reach, including both idle and in-use connections (connection to the Audit Log database).
audit-log.datasource.hikari.poolName
“audit-log”
User-defined name for the connection pool. Displayed mainly in logging and JMX management consoles to identify pools
Section: Limit workflow
This section defines properties relating to the workflows.
Property
Value
Description
limits.workflow-types.StraightThrough
limit-process-instance.straight-through
Maps the ‘StraightThrough’ workflow type used for the creation of limit tasks to the ‘limit-process-instance.straight-through’ workflow.
limits.workflow-types.FourEyes
limit-process-instance.four-eyes
Maps the ‘four-eyes’ workflow type used for the creation of approval tasks to the ‘limit-process-instance.four-eyes’ workflow.
limits.workflow-types.SixEyes
limit-process-instance.six-eyes-kpi
Maps the ‘six-eyes-kpi’ workflow type used for the creation of limit tasks to the ‘limit-process-instance.six-eyes-kpi’ workflow. This property is required for Limits to start. You can use the reference limit-process-instance.straight-through provided in limits-starter/src/main/resources/processes/ as a default implementation.
limits.workflow-types.Deletion
limit-process-instance.deletion
Maps the ‘deletion’ workflow type used for deleting a limit definition to the ‘limit-process-instance.deletion’ workflow. This applies to every limit definition deletion from the Limits Inventory.
limits.workflow-types.Exception
limit-process-instance.exception
Maps the ‘exception’ workflow type used for breaches/warnings to the ‘limit-process-instance.exception’ workflow.
Determines the type of file loading for limits. Values are separate or accumulate. Not recommended to change, as the accumulate mode is the legacy format, and will be removed in future versions.
limit.evaluation.include-passes
false
If true, Atoti Limits stores passes (i.e. evaluations that do not result in a breach or warning) in the datastore during limit evaluation. The default value of false prevents a large number of passes from polluting the Limit Status screen.
limit.evaluation.error.include-stacktrace
false
true if the stack trace should be available in the evaluation response to the UI.