Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

If Blueriq is installed with the installer with the DCM Lists feature enabled, a message broker has already been installed and all necessary queues and exchanges have already been configured. Otherwise, please install a supported message broker. More information on how to install a supported message broker can be found on the Queue page. For instructions on how to configure the message broker for DCM 2.0, please refer to the Configuration for the Case Engine [deprecated] page.

Set up MongoDB

If Blueriq is installed with the installer with the DCM Lists feature enabled, MongoDB has already been installed. Otherwise, please install a supported version of MongoDB and add a user and a database for the Case Engine. More information on how to install MongoDB can be found on the Document database MongoDB page.

Runtime configuration

...

Code Block
titleapplication-case-engine.properties
,# RabbitMQ - Case Engine
blueriq.case.engine.rabbitmq.host=localhost
blueriq.case.engine.rabbitmq.port=13089
blueriq.case.engine.rabbitmq.username=blueriq
blueriq.case.engine.rabbitmq.password=welcome
blueriq.case.engine.rabbitmq.virtualHost=blueriq
blueriq.case.engine.rabbitmq.queueNames=dcmEventsQueue

# MongoDB - Case Engine
blueriq.case.engine.data.mongodb.host=localhost
blueriq.case.engine.data.mongodb.port=13088
blueriq.case.engine.data.mongodb.database=caseEngine
blueriq.case.engine.data.mongodb.username=blueriq
blueriq.case.engine.data.mongodb.password=welcome
blueriq.case.engine.data.mongodb.authenticationDatabase=caseEngine

# RabbitMQ - Process Engine
blueriq.process.engine.v2.rabbitmq.host=localhost
blueriq.process.engine.v2.rabbitmq.port=13089
blueriq.process.engine.v2.rabbitmq.username=blueriq
blueriq.process.engine.v2.rabbitmq.password=welcome
blueriq.process.engine.v2.rabbitmq.virtualHost=blueriq
blueriq.process.engine.v2.rabbitmq.exchangeName=dcmTasksEvents

# RabbitMQ - Case Engine Scheduler
blueriq.case.engine.scheduler.rabbitmq.host=localhost
blueriq.case.engine.scheduler.rabbitmq.port=13089
blueriq.case.engine.scheduler.rabbitmq.username=blueriq
blueriq.case.engine.scheduler.rabbitmq.password=welcome
blueriq.case.engine.scheduler.rabbitmq.virtualHost=/
blueriq.case.engine.scheduler.rabbitmq.ssl.enabled=false
blueriq.case.engine.scheduler.rabbitmq.exchangeName=dcmScheduledEvents

# MongoDB - Caselocking
blueriq.locking.mongodb.host=localhost
blueriq.locking.mongodb.port=13088
blueriq.locking.mongodb.database=caseEngineLocks
blueriq.locking.mongodb.username=blueriq
blueriq.locking.mongodb.password=welcome
blueriq.locking.mongodb.authenticationDatabase=caseEngine

...

DCM 2.0 comes with a set of new services and containers that communicate with the case engine. These services and containers have the DCM_  prefix. You can find them in the Container types and Service call types, or see the DCM library. You need to use these in your DCM 2.0 project. For more information, please contact support.

Other resources

Case Engine 
Case Engine Client Component - under development