MDM 15.2.0 Upgrade Notes
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.
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/>History plugin refactoring issue
The history plugin (see History Plugin) has been refactored, and all settings are now managed in the MDM Server application.properties file.
Due to the broken compatibility (see Ataccama 15.2.0 Release Notes, section Known Issues), the history plugin configuration defined in the nme-config.xml file is ignored in the current version.
The issue will be resolved in 15.3.0.
To ensure the plugin is enabled, make sure the following properties are defined with the specified values in the application.properties file:
ataccama.one.mdm.config.historyConfigFile=nme-history.gen.xml
ataccama.one.mdm.nme.history.persistence.class=com.ataccama.nme.persistence.vldb.VldbPersistenceFactory
ataccama.one.mdm.nme.history.storage-directory=../storage/history
ataccama.one.mdm.nme.history.persistence.dataSource=mdc_db
ataccama.one.mdm.nme.history.persistence.prefix=H_
If you skip this step, no new historical data will be saved until the properties are defined in the application.properties file.
|
To change the default configuration, add the relevant properties to the application.properties file and specify the values.
To know more, see MDM Server Application Properties, section History plugin configuration.
To disable the history plugin, add the property ataccama.one.mdm.config.historyConfigFile with an empty value:
ataccama.one.mdm.config.historyConfigFile=
It is not possible to disable the history plugin using the checkbox in ONE.
The MDM Server fails to start with the empty nme-history.gen.xml file.
|
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 |
|---|---|---|
/ |
|
/ |
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
Added properties
-
History plugin configuration (see History plugin refactoring issue)
ataccama.one.mdm.config.historyConfigFile=nme-history.gen.xml ataccama.one.mdm.nme.history.persistence.class=com.ataccama.nme.persistence.vldb.VldbPersistenceFactory ataccama.one.mdm.nme.history.storage-directory=../storage/history ataccama.one.mdm.nme.history.persistence.dataSource=mdc_db ataccama.one.mdm.nme.history.persistence.prefix=H_
nme-config.xml
Removed properties
-
History plugin configuration (see History plugin refactoring issue)
The following properties in the history plugin configuration will be ignored in the current version.
<plugin class="com.ataccama.nme.history.NmeHistoryPlugin"> <persistenceLayer class="com.ataccama.nme.persistence.vldb.VldbPersistenceFactory"> <dataSource>mdc_db</dataSource> <prefix>H_</prefix> </persistenceLayer> <configFile>nme-history.gen.xml</configFile> <storageDirectory>../storage/history</storageDirectory> </plugin> -
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?