Page History
...
The Case Engine currently is a Runtime with specific configuration. It is installed by deploying the Runtime WAR to a supported application server, see Installing Runtime. Alternatively you can use the DCM 2.0 beta installation [old] which includes the case engine with configuration.
...
Note |
---|
When using the DCM 2.0 beta installation [old] this configuration is included |
...
Code Block | ||||
---|---|---|---|---|
| ||||
#### Datasources H2 ### blueriq.datasource.process-sql-store.url=jdbc:h2:./h2db/dcm;AUTO_SERVER=TRUE blueriq.datasource.process-sql-store.username=sa blueriq.datasource.process-sql-store.password= blueriq.datasource.process-sql-store.driverClassName=org.h2.Driver blueriq.hibernate.process-sql-store.hbm2ddl.auto=update blueriq.hibernate.process-sql-store.dialect=org.hibernate.dialect.H2Dialect blueriq.hibernate.process-sql-store.criteria.literal_handling_mode=BIND blueriq.hibernate.process-sql-store.globally_quoted_identifiers=true blueriq.hibernate.process-sql-store.globally_quoted_identifiers_skip_column_definitions=true |
Info | ||
---|---|---|
| ||
When using a production database, please use 'validate' instead of 'update' in combination with the supplied database scripts. |
Code Block | ||||
---|---|---|---|---|
| ||||
# queue configuration from blueriq.default.rabbitmq can be overruled blueriq.dcm.lists-publisher.rabbitmq.exchangeName=dcmListsEvents |
...
Overview
Content Tools