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 5 Next »

Unable to render {include} The included page could not be found.

The DCM Installation zip, which can be downloaded from the Customer section, contains a ready-to-run DCM 2.0 beta installation.

This installation's purpose is to provide an quick way to start a DCM 2.0 stack, for demo and playground purposes.
Don't use it in production, because it is not properly hardened nor sized and is uses some low impact drop-in replacements for some 3rd party components.

Deploy the DCM 2.0 stack

Extract the ZIP file mentioned above to a location on your hard disk. The path where the ZIP file is extracted should not contain any whitespace.

The only thing you need to do before running is placing a license file in the conf\runtime and conf\case-engine folders. When using the new Blueriq DCM Dashboard service, the license file needs to be placed in the conf\runtime-dashboards and conf\case-engine-dashboards folders.

Also note that you need a license where the 'case engine' feature is enabled. The DCM Foundation also relies on the 'external flow' license. Please contact support when licenses are needed.

Start the DCM 2.0 stack

A bat file starts all different components in the DCM 2.0 setup. Each component is started in a CMD window which is minimized.

For the default DCM 2.0 setup, use the start.bat file. When using the new Blueriq DCM Dashboard service, use the start-dashboards.bat file.

After every component is started, the landing page is launched in your browser. Please allow some time for all components to have properly started before accessing the runtime.

Stop the DCM 2.0 stack

A at file stops all running components.

For the default DCM 2.0 setup, use the stop.bat file. When using the new Blueriq DCM Dashboard service, use the stop-dashboards.bat file.

Note that the CMD windows are not closed when it is done. You should do this yourself.

Studio connection

The DCM stack contains a Studio connection based on the assumption that Studio is installed with the default port. If Studio runs on another port, change it in conf\runtime\application-development-tools.properties and conf\case-engine\application-development-tools.properties. When change it in conf\runtime\application-development-tools.properties and conf\case-engine\application-development-tools.properties, change it in conf\runtime-dashboards\application-development-tools.properties and conf\case-engine-dashboards\application-development-tools.properties

The stack is set up to work with the DCM Foundation models. Either using the model exports in the beta installer, or using the Studio environment. The latest foundation models can be found at DCM 2.0 Foundation (new architecture). When the project is imported, the shortcuts might have to be updated at the runtime.

System requirements

The DCM stack will only run on the Windows operation system.

The DCM stack consists of 5 Tomcat instances, including instances for MongoDB (document database), Qpid (queue) and the document renderer. Components that need relational storage (SQL) use an embedded H2 database. When using the new Blueriq DCM Dashboard service, the stack additionally contains an extra tomcat instance for the Dashboard service, Nginx, Keycloak and a gateway service that runs as a standalone jar.

The stack requires at least 3 GB of free disk space and 4 GB of (free) memory, or 6GB of (free) memory when using the new Blueriq DCM Dashboard service. Also, all the components start at once, so starting puts a heavy load on the processor. Other than that, any modern computer running Windows 10 or later should be able to run this.

Note that QPid and H2 are provided as low impact replacements for RabbitMQ and MSSQL/OracleDB. They are suitable for demo/development scenarios.

In production scenarios, we expect RabbitMQ and MSSQL/Oracle to be used.

Users and passwords

  • DCM Foundation: Aanvrager/Aanvrager and Behandelaar/Behandelaar
  • H2 Console: h2/h2
  • Qpid management, Customerdata, DCM lists and Maintenance app: blueriq/welcome
  • MongoDB: no authentication set up by default
    • You can use any MongoDB client to connect to inspect MongoDB content. MongoDB itself offers Compass as a visual client.
    • Connection String: mongodb://localhost:30012/ 
  • Keycloak (when using the new Blueriq DCM Dashboard service): admin/admin
  • No labels

Didn't find the answer you were looking for? Try the advanced search!