User Community Service Desk Downloads

MDM 15.2.0 Upgrade Notes

Due to backward compatibility issues in this version, we recommend upgrading to version 15.3 or higher instead.

Security improvements

Applies to self-managed deployments. We changed the authentication configuration for notifications. After the upgrade, add the following configuration settings to the MDM Web App application.properties file.

Notification configuration example
ataccama.one.platform.deployments.mdm.module=mdm
ataccama.one.platform.deployments.mdm.uri= <mdm-server.host>
ataccama.one.platform.deployments.mdm.security.jwt-keys.key1.fingerprint=<mdm-server.jwt-key.fingerprint>
ataccama.one.platform.deployments.mdm.security.jwt-keys.key1.content=<mdm-server.jwt-key.content | b64encode>
ataccama.one.platform.deployments.mdm.security.jwt-keys.key1.is-revoked=false
ataccama.one.platform.deployments.mdm.security.roles=IMPERSONATION
The property values should correspond to ataccama.authentication.internal.jwt.generator.key (see MDM Server Application Properties, section Service Private Key).

MDM configuration simplification

The following files are no longer defined in the nme-config.xml file (see MDM Engine Configuration File) and are used by default now:

  • nme-batch.gen.xml

  • nme-services.gen.xml

  • nme-executor.xml

  • nme-task.gen.xml

  • nme-stream.gen.xml

  • nme-security.xml

To define the necessary security roles and permissions, use the nme-security.xml file. See Security and Audit.

To disable security restrictions, use the empty nme-security.xml file:

<?xml version='1.0' encoding='UTF-8'?>
<security/>

New database for High Availability mode

The high availability (HA) mode now uses a separate database by default: ha_db instead of mdc_db. This helps avoid potential conflicts and ensure optimal performance and reliability for both single instance and HA modes.

Configuration changelog

This section provides the information about the changes in the configuration files that need to be taken into account when upgrading the solution. In certain cases, the newly introduced default is used or some configuration is required.

The following table lists the configuration files that were added, changed, or removed.

Added files Changed files Removed files

/

  • MDM Server application.properties

  • nme-config.xml

/

The following sections list the changes in the files: added, changed, and removed properties.

MDM Web App application.properties

Added properties

  • Notification configuration (see Security improvements)

    ataccama.one.platform.deployments.mdm.uri= <mdm-server.host>
    ataccama.one.platform.deployments.mdm.security.jwt-keys.key1.fingerprint=<mdm-server.jwt-key.fingerprint>
    ataccama.one.platform.deployments.mdm.security.jwt-keys.key1.content=<mdm-server.jwt-key.content \| b64encode>
    ataccama.one.platform.deployments.mdm.security.jwt-keys.key1.is-revoked=false
    ataccama.one.platform.deployments.mdm.security.roles=IMPERSONATION

MDM Server application.properties

Changed properties

  • ataccama.one.mdm.ha.db.name - the default value is now 'ha_db'.

nme-config.xml

Removed properties

  • Files definition (see MDM configuration simplification)

    <batchLayerDefinitionFile>nme-batch.gen.xml</batchLayerDefinitionFile>
    <serviceDefinitionFile>nme-services.gen.xml</serviceDefinitionFile>
    <taskExecutorConfigFile>nme-executor.xml</taskExecutorConfigFile>
    <taskConfigFile>nme-task.gen.xml</taskConfigFile>
    <streamDefinitionFile>nme-stream.gen.xml</streamDefinitionFile>
    <securityConfigFile>nme-security.xml</securityConfigFile>

Was this page useful?