Runtime Parameters in MDM
In addition to the project-specific runtime configuration allowing you to define connections to remote servers, data sources, or specific resources, you can also configure runtime parameters. Runtime parameters help control and finetune data processing, performance, and computing resources used during the different phases of the MDM process, as well as different storage persistence options.
In the context of MDM, we differentiate between MDM-specific runtime parameters and general runtime properties.
| See also Performance Tuning. |
MDM-specific runtime parameters
MDM-specific runtime parameters use the nme. prefix.
These parameters are stored in the Application Configuration and updated through the MDM Web App Admin Center.
They are loaded to the database automatically on the initial server startup, or manually, for example, after an external configuration change or after resetting your environment. For details about how and when to run the migration manually, see MDM Web App Admin Center > Server Dashboard.
Some parameters require restarting the MDM Server for the changes to take effect. If required, this is mentioned in the parameter description and indicated in the MDM Web App Admin Center.
For a full list of runtime parameters that can be used in MDM, see Runtime Parameters.
General runtime properties
General runtime parameters, such as those configuring hardware resources available to the MDM Server, are provided to the JVM when starting the MDM Server (for example, -Dnme.copyColumns.skipUnchanged=true) or included in the runtime.properties file.
By default, the file is located in <ataccama.one.mdm.config.config-folder>/etc (alternatively, the file is found in <ataccama.one.mdm.config.runtime-folder>).
To verify the actual location, check the values of the ataccama.one.mdm.config.config-folder and ataccama.one.mdm.config.runtime-folder application properties.
Runtime parameters values set during engine startup are available in ONE Runtime Server Admin.
nme.matching properties
Even though they start with the nme. prefix, nme.matching.* properties are configured and managed the same way as general runtime parameters: through the runtime.properties file.
This way, you can configure them separately for each instance instead of having a shared configuration for all matching steps.
Edit permissions for runtime parameters
MDM-specific runtime parameters are edited from the MDM Web App Admin Center > Runtime Parameters screen. For details, see MDM Web App Admin Center.
To edit runtime parameters, you need to be assigned a role defined in the ataccama.one.mdm.admin-center.manager.required-roles application property.
By default, this is the MDM_server_admin role.
To learn more about the relevant application properties, see MDM Admin Center Permissions.
Was this page useful?