Page History
Include Page
...
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 Blueriq DCM Development Installation which includes the case engine with configuration.
...
These properties are divided into three files:
: common properties that concern security, logging and the connection to the customer dataInclude Page _PropertiesFileJava _PropertiesFileJava
: properties for several queues, MongoDB and QuartzInclude Page _PropertiesCaseEngine _PropertiesCaseEngine
: properties that enable the Case Engine to communicate with the Process SQL StoreInclude Page _PropertiesExternalDatasources _PropertiesExternalDatasources
Create the files in the additional config location of the case engine and copy and paste the corresponding properties into each file.
Note |
---|
When using the DCM 2.0 beta installation Blueriq DCM Development Installation this configuration is included |
...
Code Block | ||||
---|---|---|---|---|
| ||||
# queue configuration from blueriq.default.rabbitmq and can be overruled blueriq.case.engine.rabbitmq.queueNames=dcmEventsQueue blueriq.case.engine.rabbitmq.exchangeName=dcmEvents # queue configuration from blueriq.default.rabbitmq can be overruled blueriq.process.engine.v2.automatic-task.rabbitmq.exchangeName=dcmTasksEvents # queue configuration from blueriq.default.rabbitmq can be overruled blueriq.process.engine.v2.process-finished.rabbitmq.exchangeName=dcmEvents # queue configuration from blueriq.default.rabbitmq can be overruled blueriq.case.engine.scheduler.rabbitmq.exchangeName=dcmScheduledEvents # queue configuration from blueriq.default.rabbitmq can be overruled blueriq.case.engine.maintenance.rabbitmq.exchangeName=dcmMaintenanceEvents blueriq.case.engine.concurrency.concurrent-consumers=1 blueriq.case.engine.concurrency.max-concurrent-consumers=1 blueriq.case.engine.data.mongodb.host=localhost blueriq.case.engine.data.mongodb.port=30012 blueriq.case.engine.data.mongodb.database=caseEngine blueriq.locking.mongodb.host=localhost blueriq.locking.mongodb.port=30012 blueriq.locking.mongodb.database=locks spring.quartz.job-store-type=memory spring.quartz.properties.org.quartz.threadPool.class=org.quartz.simpl.SimpleThreadPool spring.quartz.properties.org.quartz.threadPool.threadCount=2 |
...
Code Block | ||||
---|---|---|---|---|
| ||||
#### Datasources H2PostgreSQL ### blueriq.datasource.process-sql-store.url=jdbc:h2postgresql:./h2db/dcm;AUTO_SERVER=TRUE//bq-postgres:5432/blueriq blueriq.datasource.process-sql-store.username=sablueriq blueriq.datasource.process-sql-store.password=welcome blueriq.datasource.process-sql-store.driverClassName=org.h2postgresql.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 validate |
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 |
...
If you are using a different authentication provider, like LDAP, you can create a user in that provider instead of users.properties
, as long as it has the proper role.
Event logging
It is possible to enable logging for events sent to the Case Engine. A line is logged when the Case Engine starts processing the event and when it is finished.
Events list
- AbortTaskService
- AbortTaskWithoutUnlocking
- AssignTask
- CompleteTask
- CreateCase
- DemuxedThrowMessageEvent
- GetCaseInfo
- GetTaskInfo
- RemoveCase
- ScheduledEvent
- StartTask
- ThrowMessage
How to enable
By default, the events are logged on INFO level. To specifically enable logging for the events only, configure the following package on INFO level:
Code Block | ||
---|---|---|
| ||
logging.level.com.blueriq.dcm.caseengine.service=INFO |
Example output
StartTask event logline:
2024-04-25 13:43:09.100 INFO c.b.d.c.c.CaseEngineRestController httpSessionId="43C5CF48C812F97E301843659A09A04A" runtimeSessionId="" userId="caseengine" projectName="" projectVersion="" currentPageName="" tenantName="" [trace=662a41cd99970f5e778c9835294b1413,span=be8f45537809ead6] - [startTask] Starting transaction - task ID: '6' case ID: '662a41c4fcab766683cab7c5'
Finishing a case
Whenever the process for a case finishes, the case will be closed. This means that the following persistent parts of a case will be removed:
- The process and its tasks and data in the process-sql-store
- The case and its manual tasks in the DCM Lists Service's MongoDB database
- The case document in MongoDB
- Any remaining entries in the scheduler database
- The case aggregate and the case data aggregate
We are aware that it may not be desirable to remove the aggregates, for example if your process doesn't have steps for archival. Therefore, we introduced a property to control this behavior:
Code Block | ||||
---|---|---|---|---|
| ||||
blueriq.case.engine.data.general.remove-aggregates-on-case-close = false |
The default value for this property is true
.