To install the DCM foundation project, follow these steps:
Download the correct version of the DCM foundation you want to use. The file can be downloaded here.
Step 3: Import DCM Foundation package
Open Blueriq studio and the branch of the DCM project you want to load the DCM foundation into.
Follow the steps listed in the guide import a package. When selecting the package to import, select the .zip package you have downloaded in step 1.
Import all projects suggested by studio.
Now we import the correct libraries. Import the AquimaLibraries.package
using the steps of the guide import a library project.
Some projects have to be transformed into libraries. This applies for all projects listed below:
Basis_Proces
Basis_Zaak
Basis_ZaakDomeinMetadata
Globals
AquimaTheme
(AquimaPresentationStyles)
For these projects, execute the steps in the guide create a library project.
Now we set up the shortcuts to our project in the runtime. To do this first follow the steps in the guide create a shortcut and select the flow Start
in the project ZaakType_A
name the shortcut ZaakType_A
.
blueriq.production.shortcuts-only=false blueriq.shortcut.MainDashboard.flow=Dashboard blueriq.shortcut.ZaakType_A.flow=Start |
blueriq.production.shortcuts-only=true blueriq.shortcut.MainDashboard.flow=Dashboard blueriq.shortcut.ZaakType_A.flow=Start |
To secure the shortcuts that are used within your application, please read Security: Shortcuts and AQ_GetRequestParameters carefully. |
When you start with the DCM Foundation two specific roles have already been taken into account for you. These roles are the Aanvrager
and Behandelaar
roles. These roles are introduced for specific authorization usage. The way to make use of this authorization is to have credentials for logging in as either one of these roles. You can add these in the runtime, as described on the dashboard settings page. Keep in mind that roles are case sensitive.
Now you can login with the credentials you just made.
The DCM Foundation requires database connections to store information that is created with the DCM Foundation project. Blueriq it self comes with an H2 database out of the box, however it is not recommended use an H2 database in production, therefor is recommended to configure the external datasources for you own databases. How to configure database can be found here.
#default h2 file based settings for external datasources profiles blueriq.datasource.comments-sql-store.url=jdbc:h2:./target/comments-sql-store;AUTO_SERVER=TRUE blueriq.datasource.customerdata-sql-store.url=jdbc:h2:./target/customerdata-sql-store;AUTO_SERVER=TRUE blueriq.datasource.dossier.url=jdbc:h2:./target/dossier;AUTO_SERVER=TRUE blueriq.datasource.process-sql-store.url=jdbc:h2:./target/process-sql-store;AUTO_SERVER=TRUE blueriq.datasource.trace-sql-store.url=jdbc:h2:./target/trace-sql-store;AUTO_SERVER=TRUE |
This DCM Foundation template uses the following components:
In order to use components, the component profile must be active. The following examples can be used to activate the components.
spring.profiles.active=native,externaldatasources,comments-sql-store,customerdata-client,dashboard,process-sql-store,trace-sql-store |
spring.profiles.active=native,externaldatasources,comments-sql-store,customerdata-client,dashboard,process-sql-store,trace-sql-store,development-tools |
More information on how to configure the application using Spring Profiles can be found here : Application configuration with Spring Profiles.
In order to use the Container type: AQ_File_Upload container a connection has to be defined in the application properties.
blueriq.connection.filesystemconnection.filesystem.path=C:/Blueriq/Uploads |
Everything is ready to start using the DCM foundation. To start the project in the runtime select the following parameters:
Main_Dashboard
in your repository,Trunk
,Dashboard
English
mvc
bootstrap3
Related articles appear here based on the labels you select. Click to edit the macro and add or change labels.
|