You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

DCM 2.0. has several components that use Document databases (MongoDB).

This section will explain in which components MongoDB is used, which configurations are needed for it and what needs to be considered when installing the databases.

Overview


As you can see in the image above, the components: Case-Engine, Dcm-Lists and the maintenance app use one or more document databases. When using these components, it is needed to create the following four databases in mongoDB:

  • caseEngine: the database where cases are stored for the case engine
  • locks: the database where case locks are stored and thus enabling case consistency
  • tasks: the database where the tasks for the dcm-lists component are stored
  • messages: the database where all (failed/delayed) messages are stored for the dcm-maintenance app

instructions about how a database can be created can be found here: https://www.mongodb.com/docs/manual/core/databases-and-collections/


When the databases are created it is necessary to configure all applications in a way that they can communicate with the databases.


Configuration

Case Engine:

In the application-case-engine.properties file add the following lines to enable the case engine to communicate with the caseEngine and locks databases:

application-case-engine.properties
#mongoDB - case engine
blueriq.case.engine.data.mongodb.host=<url-of-the-database-server>
blueriq.case.engine.data.mongodb.port=<port-of-the-database>
blueriq.case.engine.data.mongodb.database=caseEngine

#mongoDB - locks
blueriq.locking.mongodb.host=<url-of-the-database-server>
blueriq.locking.mongodb.port=<port-of-the-database>
 blueriq.locking.mongodb.database=locks

Replace the strings with < and > with the needed values of your specific setup.

Dcm-lists:

In the Blueriq-dcm-lists.yml file add the following lines to enable the dcm-lists component to communicate with the tasks database:

blueriq-dcm-lists.yml
spring:
  data:
    mongodb:
      host: <url-of-the-database-server>
      port: <port-of-the-database>
      database: tasks

Replace the strings with < and > with the needed values of your specific setup.


Dcm-Maintenance-app

In the Blueriq-dcm-maintenacne-app.yml file add the following lines to enable the dcm-maintenance-app to communicate with the messages database:

blueriq-dcm-maintenacne-app.yml
blueriq:
  dcm:
    maintenance:
      app:       
        mongodb:                
		  host: <url-of-the-database-server>
      	  port: <port-of-the-database>
          database: messages

Replace the strings with < and > with the needed values of your specific setup.

Installing MongoDB:

MongoDB can be downloaded and installed via https://www.mongodb.com/ .

For most use cases the free community edition should suffice. There are also some cloud providers that provide mongoDB on their platforms.

For production scenarios, please refer to the recommended MongoDB setup on https://docs.mongodb.com/manual/administration/production-notes


Considerations

MongoDB is a scalable document based NoSQL database solution that is used in multiple components of DCM 2.0. Before installing and using MongoDB it is recommended to consider the following:

  • MongoDB can be run in the cloud or on premise. If MongoDB supports your desired platform can be read here.
  • MongoDB is designed specifically with commodity hardware in mind and has few hardware requirements or limitations. Read about the hardware considerations here.
  • For redundancy and availability considerations please read replication.
  • for other considerations please read the mongoDB docs

BQ-14448 - Getting issue details... STATUS


  • No labels