Versions Compared

Old Version 14

changes.mady.by.user Deny Raatgever

Saved on

compared with

New Version Current

changes.mady.by.user Randy Anft

Saved on

Key

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

...

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

For the default DCM 2.0 Case-Modelling setup, use the start-DCM-stack.bat file. When using the new Blueriq DCM Dashboard service, use the start-DCM-dashboards-stack.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.

Accessing the DCM stack

For the default Case-Modelling setup you can visit the Runtime on http://localhost:30008/runtime.

For the new DCM Dashboard setup can visit the default preconfigured dashboard on http://localhost:30000/dashboard/default.

Stop the DCM stack

A at file stops all running components.

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

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

...

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

...

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 a PostgreSQL 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.

Warning

Note that QPid and H2 are is 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.

...

  • DCM Foundation: Aanvrager/Aanvrager and , Behandelaar/Behandelaar and Beheerder/Beheerder
  • PostgreSQL database: postgres/password!123H2 Console: h2/h2
  • Qpid management, Customerdata and DCM lists: blueriq/welcome
  • DCM Maintenance App: audit/a, guest/g, maintainer/m or owner/o
  • 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