Page History
...
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, Behandelaar/Behandelaar and Beheerder/Beheerder
- H2 ConsolePostgreSQL database: h2postgres/h2password!123
- 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