Ataccama ONE Agentic ONE Desktop ONE DQ&C ONE MDM ONE RDM ONE Runtime Server
latest (17.1.0) 17.0.0 16.3.x 16.2.0 16.1.0 16.0.0 15.4.0 15.3.0 15.2.0 15.1.0 14.5.x 13.9.x 13.8.x 13.7.x 13.6.x 13.5.0 13.4.x 13.3.x 13.2.x
Downloads

MDM Configuration

This article provides an overview of different configuration options for MDM Server.

Before you start, we recommend getting familiar with the solution architecture. See MDM Architecture.

MDM Server configuration

The bulk of configuration is defined in the MDM Server application.properties file. In addition, a number of configuration files is used for specific components, as mapped out in the following table.

Component Configuration file Notes

MDM Server

application.properties

MDM Server Manager

server-manager.properties

Used for management functionalities within MDM Server, specifically configuring the Server Dashboard in the MDM Web App Admin Center.

History plugin

nme-history.gen.xml

Must be referenced from application.properties.

MDM Engine (name in the code: nme)

nme-config.xml

Must be referenced from nme-config.xml.

This is also where persistent storage is configured. Tables and columns including pseudocolumns.

MDM Model

nme-model.gen.xml

Must be referenced from nme-config.xml.

Datasets

nme-datasets.gen.xml

Must be referenced from nme-config.xml.

Event handlers

nme-event_handler.gen.xml

Must be referenced from nme-config.xml.

Operation plans

nme-consolidation-plan.xml

Must be referenced from nme-config.xml.

Version check

mdm-version.gen.xml

Must be referenced from nme-config.xml.

Batch interface

nme-batch.gen.xml

The default file name must not be modified.

Native services

nme-services.gen.xml

The default file name must not be modified.

Executor

nme-executor.xml

The default file name must not be modified.

Task configuration

nme-task.gen.xml

The default file name must not be modified.

Streaming interface

nme-stream.gen.xml

The default file name must not be modified. Must be referenced from the application.properties file.

Security and audit

nme-security.xml

The default file name must not be modified. Must be referenced from the application.properties file.

Embedded Runtime Server configuration

mdm.serverConfig

Available only in self-managed deployments. See Server Setup.

In cloud deployments, only some elements are available for configuration, as described in MDM Custom Ataccama Cloud Deployment and MDM Project Local Server Configuration Testing.

mdm.runtimeConfig

Project-specific runtime settings, such as path variables, connections to data sources and servers. See Project-Specific Configuration.
In addition to application.properties and server-manager.properties files, the MDM Server package also contains application.properties.j2. This is a template for ONE Installer and not used for MDM configuration.

Default ports

The following table lists the ports on which MDM components listen by default, the property that changes each port, and the file where the property is set.

Component Used for Default port Property Configuration file

MDM Server

HTTP: MDM Admin Center backend, GraphQL, REST API, SOAP and native services, HA Admin Console

8051

server.port, or ataccama.server.http.default.port, which server.port uses as its default

MDM Server application.properties

MDM Server

Actuator endpoints (/actuator): health checks and metrics

8056

management.server.port

MDM Server application.properties

MDM Server

gRPC: MDM Web App backend and data provisioning to ONE

8551

ataccama.server.grpc.port

MDM Server application.properties

MDM Server

Internal communication of the MDM Server runtime (remote calls and file transfer)

7777

ataccama.server.service.port

MDM Server application.properties

MDM Server HA load balancer

Entry point for clients in high availability mode. Started only when ataccama.one.mdm.ha.implementation is set.

8058

ataccama.one.mdm.ha.load-balancer.port

MDM Server application.properties

MDM Server Manager

Server Dashboard GraphQL endpoint (/manager/graphql)

8057

server.port

server-manager.properties

MDM Server Manager

Actuator endpoints (/actuator), including the liveness check called by MDM Web App

8058

management.server.port

server-manager.properties

MDM Web App

HTTP: MDM Web App user interface

8050

server.port

MDM Web App application.properties

MDM Web App

Actuator endpoints (/actuator)

8055

management.server.port

MDM Web App application.properties

Running multiple MDM instances on one host

Each instance needs its own set of ports. For every additional instance, change the following properties before starting it:

  • MDM Server application.properties:

    • server.port

    • management.server.port

    • ataccama.server.grpc.port

    • ataccama.server.service.port

    • ataccama.one.mdm.ha.load-balancer.port, if high availability is enabled

  • MDM Server server-manager.properties:

    • server.port

    • management.server.port

  • MDM Web App application.properties:

    • server.port

    • management.server.port

    • ataccama.one.mda.server.url, ataccama.one.mda.server.manager.url, and ataccama.one.mda.server.health.url, which must point to the ports of the MDM Server instance that the web application belongs to (see MDM Web App Application Properties)

MDM Web App configuration

Refer to MDM Web Application Configuration and Server Configuration for MDM Web App.

Additional configuration

ONE MDM Server also uses MDM model project templates, which are definitions written in Advanced Metadata Editor (AME). This is represented in the Model Explorer in ONE Desktop.

MDM model project templates consist of:

  • Sample projects suitable for the matching engine.

    • General CDI project. A sample project including a small data set.

    • Blank general MDM project. Project structure without content.

Was this page useful?