Application Configuration

ONE MDM Server configuration is located primarily in the application.properties file.

In cloud deployments, configuration is provided using templates tailored to the specific tier your enviroment is running in. These parameters are configured as part of the platform deployment process.

If this is your use case, skip ahead to Database schemas.

In self-managed deployments, it’s up to you to customize your instance of ONE MDM. In addition to application.properties file, see the following resources:

HTTP Server Configuration - Set up an HTTP server.
MDM Server Application Properties - Define an internal database for essential data in MDM. We strongly recommend using a PostgreSQL database for that purpose.
Project-Specific Configuration - Specify resources to be used in a particular MDM project.
Runtime Parameters in MDM - Customize performance, computing resources, and storage persistence options.

Database schemas

The MDM Server uses several dedicated database schemas. These schemas are defined in the application.properties file.

If you’re looking to configure a project-specific data source instead, see Project-Specific Configuration > Data Sources.

These settings are defined only once and in only one location: either in application.properties or in mdm.runtimeConfig file.

In case you use the external database schema, we recommend migrating it to the orchestration schema.

The following table lists the necessary database schemas along with their descriptions.

Name Name in the application.properties file Description

Name	Name in the application.properties file	Description
`mdc`	`mdc_db`	Persistent storage for master and instance records, matching data, tasks and drafts data, history data. See MDM Storage.
`eh`	`eh_db`	Persistent storage of data for event handlers (referenced in the `nme-event_handler.gen.xml`), automated tasks, and history plugin.
`orchestration`	`orchestration_db`	Persistent storage of data for the orchestration workflow (EWF), scheduler, and custom orchestration tables. Referenced in the `mdm.serverConfig` file.
`ai_matching`	`/`	Storage of data related to AI Matching processes.

mdc

mdc_db

Persistent storage for master and instance records, matching data, tasks and drafts data, history data. See MDM Storage.

eh

eh_db

Persistent storage of data for event handlers (referenced in the nme-event_handler.gen.xml), automated tasks, and history plugin.

orchestration

orchestration_db

Persistent storage of data for the orchestration workflow (EWF), scheduler, and custom orchestration tables. Referenced in the mdm.serverConfig file.

ai_matching

/

Storage of data related to AI Matching processes.

Was this page useful?