Skip to content

CRIS system integration

This section details the integration configuration options you can pass when deploying the backend.

DAMAP has the following built-in CRIS integrations:

You can also develop your own integration.

Person database

Environment variable Example Value Description
DAMAP_TENANT_AWARE_PERSON_SERVICES_0__DISPLAY_TEXT University Text shown in the frontend to allow users to switch between person services.
DAMAP_TENANT_AWARE_PERSON_SERVICES_0__QUERY_VALUE UNIVERSITY Should uniquely identify the service.
DAMAP_TENANT_AWARE_PERSON_SERVICES_0__CLASS_NAME org.damap.base.integration.university.service Which java class should be used for the service implementation.

Possible values for DAMAP_TENANT_AWARE_PERSON_SERVICES_0__CLASS_NAME are:

_0__ structure in variables

The _0__ in the environment variables is on purpose and cannot be omitted - yes even the double underscore __. They are necessary due to how the application process environment variables which get converted into lists.

Adding more than one person service

If you want to add a second person service, use the same variables but increment the number, like in this example: DAMAP_TENANT_AWARE_PERSON_SERVICES_1__DISPLAY_TEXT. DAMAP enforces at least one person service to be configured.

Projects database

Environment variable Example Value Description
DAMAP_TENANT_AWARE_PROJECT_SERVICE default Name of the projects service to consult for a project list.

The projects service value defaults to default. This is a fallback from older DAMAP integrations that did not have an explicit configuration. Instead, an explicit qualifier should be preferred.

Possible values are: