Lead your team forward
OCT 24 / 9AM ET Register nowMDM Server Application Properties
This article is intended to serve as a reference point for MDM server configuration.
As such, it provides an overview of the available properties and, when applicable, refers users to more comprehensive sources.
The properties described here are defined in the mdm-server/etc/application.properties
file.
For each property, you will find information about the required data type, its default value, and a short description.
The Mandatory column specifies whether a property is required for the application to run and function as expected.
MDM Solution Configuration
The following properties point to files containing additional MDM settings.
The paths are relative to the mdm.serverConfig
file.
Name | Data Type | Default Value | Mandatory | Description |
---|---|---|---|---|
|
String |
|
Yes |
The path to the MDM Web App configuration file (see mdm-web-app-backend-component.adoc). |
|
String |
|
Yes |
The path to the MDM Engine configuration file (see MDM Engine Configuration File). |
|
String |
|
Yes |
The path to the DQIT configuration file. |
User Settings Configuration
You can configure how and where MDM Web App user settings are stored. User settings include, for example, which columns users have chosen not to display, filter settings, column width settings, and others.
Name | Data Type | Default Value | Mandatory | Description | ||
---|---|---|---|---|---|---|
|
String |
|
Yes |
|
||
|
String |
|
Yes |
The name of the database. |
||
|
String |
|
Yes |
The tables created by the server have this prefix to distinguish them from other tables in the database. |
MDM Features
Use these properties to configure specific MDM features and specify links to other applications.
Name | Data Type | Default Value | Mandatory | Description |
---|---|---|---|---|
|
Boolean |
|
No |
Enables AI Matching in MDM Web App. |
|
String |
|
No |
The IP address or the hostname of the server where AI Matching microservices are running. |
|
String |
|
No |
The number of the AI Matching gRPC port. |
|
Boolean |
|
No |
Enables the communication between MDM and Metadata Management Module (MMM).
If set to |
|
String |
No |
The URL for MMM ( |
|
|
String |
No |
The URL to the ONE Web Application (accessible from the left navigation panel). |
|
|
String |
|
No |
Defines how often the MMM node structure is updated.
Accepted units: |
|
Number |
|
No |
The URL shown as the RDM link in the MDM Web App navigation. |
|
Boolean |
|
No |
Enables MDM notifications. |
`ataccama.one.mdm.dqit.enabled ` |
Boolean |
|
No |
Enables DQIT. |
Keycloak Configuration
The following properties configure Keycloak. See 13.6.x@one-runtime-server:ROOT:encrypting-passwords.adoc for information about how to encrypt passwords.
Name | Data type | Default Value | Mandatory | Description | ||
---|---|---|---|---|---|---|
|
String |
|
Yes |
The name of the Keycloak realm. |
||
|
String |
Yes |
The Keycloak base URL.
|
|||
|
String |
|
Yes |
The URL of the server where Keycloak is running. |
||
|
String |
|
Yes |
The client identifier used to verify the admin user authorization token. |
||
|
String |
|
Yes |
The secret key of the client identifier for the admin account.
Secret keys can be generated using Keycloak.
Used by |
||
|
String |
|
Yes |
The client identifier. Used to verify a user authorization token and to log in a user. |
||
|
String |
|
Yes |
The secret key of the client.
Secret keys can be generated using Keycloak.
Used by |
||
|
String |
|
Yes |
Specifies the issuer of the JWT token. Typically, Keycloak uses the URL of the realm as the token issuer. |
SSL
Use these properties to set up SSL.
Name | Data Type | Default Value | Mandatory | Description |
---|---|---|---|---|
|
Boolean |
|
No |
Enables SSL. |
|
String |
/ |
No |
The full path to the keystore. |
|
String |
/ |
No The password for decrypting the keystore. Used if the keystore is encrypted (recommended). |
|
String |
/ |
No |
The password for the private key. Used if the private key is encrypted. |
|
String |
/ |
No |
The full path to the truststore. |
|
Endpoints for Monitoring
To set up monitoring for MDM, specify the following properties. For more information, see 13.6.x@one:ROOT:configuring-monitoring.adoc.
Name | Data Type | Default Value | Mandatory | Description |
---|---|---|---|---|
|
Boolean |
|
No |
Enables all actuator endpoints.
If set to |
|
Boolean |
|
No |
Enables`/info` monitoring endpoint. |
|
Boolean |
|
No |
Enables |
|
Boolean |
|
No |
Enables |
|
String |
|
No |
A comma-separated list of exposed actuator endpoints that should provide information about the application. These endpoints track the following:
|
|
String |
|
No |
Specifies how much information is provided by the
|
|
String |
|
No |
Specifies how much detail the
|
|
String |
|
No |
A comma-separated list that determines how the |
|
String |
|
No |
Configures how much information the |
|
Boolean |
|
No |
Enables |
|
String |
|
No |
Defines which components are covered by the liveness probe.
These components are a subset of |
|
String |
|
No |
Defines which components are covered by the readiness probe.
These components are a subset of |
|
String |
/ |
No |
Specifies restricted endpoints that cannot be accessed. Accepts a list of URL patterns as a value. |
|
String |
|
No |
Specifies public endpoints that are excluded from authentication.
Accepts a list of URL patterns as a value.
The |
|
String |
|
No |
Specifies ACL-secured endpoints.
Accepts a list of URL strings (not patterns) as a value.
The |
|
String |
|
No |
A comma-separated list of user roles allowed to access the ACL-secured endpoints.
The |
|
Boolean |
|
No |
Enables timing metrics to all Spring endpoints. |
MDM HTTP Server
The following properties configure the MDM HTTP server.
Name | Data Type | Default Value | Mandatory | Description |
---|---|---|---|---|
|
Number |
|
Yes |
The number of the default server port. |
|
String |
/ |
No |
Specifies the paths that are not available on the defined listener port. |
|
String |
/ |
No |
Specifies the paths available on the defined port (for example, HA Admin Console, see ha-admin-console.adoc, or REST API, see REST API). |
|
Number |
/ |
No |
Defines the port for other added custom listener. |
MDM Auditing
Use the following properties to configure auditing.
Name | Data Type | Default Value | Mandatory | Description |
---|---|---|---|---|
|
Boolean |
|
No |
Enables the event log. |
|
String |
|
No |
A comma-separated list of audit writers.
Permitted values are |
|
String |
|
No |
The name of the event log table.
It is prefixed with the |
|
String |
|
No |
The name of the ID generator sequence. |
|
String |
|
No |
The name of the event log entry ID field. It is generated automatically. |
|
String |
|
No |
The name of the event log |
|
String |
|
No |
The name of the event log |
|
String |
|
No |
The name of the event log |
|
String |
|
No |
The name of the event log |
|
String |
|
No |
The name of the event log |
|
String |
|
No |
The name of the event log |
|
String |
|
No |
The name of the event log |
-
Default value used if no
mapping
properties are defined.
HA Configuration
To enable high availability (HA) mode, specify the following properties. For more information about HA, see mdm-high-availability-overview.adoc.
Name | Data Type | Default Value | Mandatory | Description |
---|---|---|---|---|
|
String |
|
No |
The HA implementation setting.
The default value selects the database locking.
Setting the value to |
|
String |
|
No |
Specifies the timeout in the case of disconnection from the cloud.
Can be used only if the |
|
String |
|
No |
Defines the maximum time interval that the safety watchdog waits for switching from active to passive state of |
|
Number |
|
No |
The number of the port where the HA load balancer is running. |
|
String |
|
No |
The name of the server where the MDM server instance is running. |
|
String |
|
No |
The name of the port where the MDM server instance is running. |
|
String |
|
No |
The name of the server where the MDM server instance is running. |
|
Boolean |
|
No |
Enables the Disconnect button in the HA console. |
|
String |
|
No |
The IP address of the server where HA load balancer is running. |
|
String |
|
No |
Visible in the HA console.
Overrides the |
|
String |
|
No |
The name of the HA database. |
|
String |
|
No |
The table prefix for Lock and HA node. |
|
String |
|
No |
The key for the HA leader instance. |
|
Number |
|
No |
Specifies how often the HA tables are updated.
Accepted units: |
|
Number |
|
No |
Defines the time interval after which expired entries are removed from the HA tables.
Accepted units: |
|
Number |
|
No |
Defines the time interval after which entries are marked as expired.
Accepted units: |
|
Number |
|
No |
Defines the time interval after which the leadership election workflow is called.
Accepted units: |
|
String |
|
No |
Specifies the start delay of the leadership election workflow.
Expressed in |
|
Number |
|
No |
Specifies the additional delay in the case of switching from passive mode to active.
The whole delay is |
|
Number |
|
No |
Specifies the delay before HA is closed.
Accepted units: |
AI Core setup
Name | Data Type | Default Value | Mandatory | Description |
---|---|---|---|---|
|
String |
|
Yes |
The number of the port where AI Matching microservices are running. |
|
String |
|
||
|
String |
|
Yes |
The name of the module type. |
|
String |
|
Yes |
The name of the environment. |
|
String |
|
Yes |
The name of the public key. |
|
String |
/ |
Yes |
The key identifier ( |
|
String |
/ |
Yes |
The value of the public key. Must use JSON syntax and be provided on a single line. |
|
Boolean |
|
Yes |
Specifies if the public key is valid.
If set to |
|
String |
|
Yes |
The user role used to create the service identity during authentication. |
DPM Setup
If your product suite includes ONE, configure DPM using the following properties.
The JWT secret and the accompanying properties for DPM that are used for communication with ONE can be found in the /opt/ataccama/one/mmm-backend/etc/application.properties
configuration file.
If you want to generate a new key for the connection between DPM and MDM, follow the instructions in 13.6.x@one:ROOT:generate-jwt-keys.adoc.
Name | Data Type | Default Value | Mandatory | Description |
---|---|---|---|---|
|
String |
No |
The number of the port where DPM is running. |
|
|
String |
|
||
|
String |
|
No |
The name of the module type. |
|
String |
|
No |
The name of the environment. |
|
String |
|
No |
The name of the public key. |
|
String |
/ |
No |
The key identifier ( |
|
String |
/ |
No |
The value of the public key. The value must use JSON syntax and be provided on a single line. |
|
Boolean |
|
No |
Specifies if the public key is valid. If set to |
|
String |
|
No |
The user role used to create the service identity during authentication. |
MDM gRPC Server
The following property configures the MDM gRPC server.
Name | Data Type | Default Value | Mandatory | Description |
---|---|---|---|---|
|
Number |
|
Yes |
The number of the port where the gRPC server is running. Authentication depends on the Keycloak configuration. |
Configuration Service
The following property sets whether the Configuration Service is used.
Name | Data Type | Default Value | Mandatory | Description |
---|---|---|---|---|
|
String |
|
Yes |
Enables using the Configuration Service.
Valid values: |
Service Private Key
Provide the service private key for MDM using the following property. The key must be set if your instance uses any of the following modules: Configuration Service, AI Matching, ONE Platform.
Name | Data Type | Default Value | Mandatory | Description |
---|---|---|---|---|
|
String |
/ |
No |
The key generated for internal JWT authentication. |
Was this page useful?