|database||Simplified option for repository setup. Possible values are h2, mysql, oracle, sqlserver, postgresql. This option will set defaults for other options, for example embedded, hibernateHbm2ddl, hibernateDialect and driverClassName based on selected database. These defaults can be overridden by specifying custom values in configuration.||h2|
Drops database files if they exist during start. Useful for tests.
Directory where H2 files will be saved if we're running in embedded mode.
current folder "."
Database filename. Name for H2 files if we're running in embedded mode.
Embedded H2 mode.
This option can be used if we're running in H2 embedded mode. If the server mode is turned on, H2 runs with TCP server. Other applications/services can connect to H2 server. If false, H2 runs in file mode.
Embedded H2 server mode SSL.
Embedded H2 server mode port.
Automatically validates or exports schema DDL to the database when the SessionFactory is created. E.g.
For production environments,
SQL dialect based on choosen DB Supported hibernate dialects.
Uses JNDI DataSource loading, when this option is defined in configuration, then jdbcUsername, jdbcPassword, jdbcUrl and driverClassName don't need to be present. E.g. <dataSource>java:comp/env/jdbc/midpoint</dataSource>
Username for JDBC connection.
sa (if embedded=true), null (otherwise)
Password for JDBC connection.
empty string (if embedded=true), null (otherwise)
URL for JDBC connection.
if embedded=true url is computed from previous parameters
Driver class name for JDBC connection.
org.h2.Driver (if embedded=true)
|useZip||Property provides optional compression for full XML column.falsecolumn storing serialized object representation (m_object.fullObject).||false|
|useZipAudit||(Since 4.0.3, 4.1.1, 4.2.1, 4.3.) Property controlling whether serialized delta and its operation result in audit is compressed (m_audit_delta.delta/fullResult).|
Important: Because this was on by default since 3.8 and the option was introduced much later, its default (true) reflects the situation in 3.8 and later.
If separate audit repository is used, this option must be used there. If single repository is used (by default), it must be used in main repository configuration.
|minPoolSize||Minimal # of connections in connection pool, if connection pool is not provided through dataSource.||8|
|maxPoolSize||Maximum # of connections in connection pool, if connection pool is not provided through dataSource.||20|
|cacheMaxTTL||Option which can enable caching of selected object types (ConnectorType, ObjectTemplateType, SecurityPolicyType, SystemConfigurationType and ValuePolicyType). Objects are cached and reloaded only if object version doesn't match. Version check happens only after time to live (TTL) period has passed. Value in seconds.||0|
|initializationFailTimeout||Hikari pool initialization failure timeout, in milliseconds. It is there to allow midPoint to wait until the repository is up and running and therefore to avoid failing prematurely. Introduced in midPoint 3.9.||1 ms (effectively keeping the behavior as it was before midPoint 3.9)|