What's new in IBM InfoSphere Master Data Management 14.0

The InfoSphere MDM 14.0.0 release includes several defect fixes.

• Installation fixes - The following installation issues are now resolved:
  • When installing deployments that use an Oracle database, running the Configure_MasterDataManagement madconfig target can result in a BUILD FAILED exception.
• MDM engine fixes - The following MDM engine issues are now resolved:
  • The CONSENT configuration table can trigger an SQL syntax error.
  • InfoSphere MDM can experience a slow web services connection to IBM InfoSphere QualityStage.
  • Address attributes do not get nullified as expected when going through IBM Change Data Capture.
  • Escape characters do not behave as expected during SOAP invocation.
  • The Performance Monitor timestamp format is incorrect.
  • An init() method is missing in the MDM Engine interface.
  • The default Compliance operation is not optimized.
• MDM Publisher fixes - The following IBM MDM Publisher issues are now resolved:
  • Need support for ConsentProcessPurposeLink and ConsentGiverRelationship with the Consent extension.
  • Need support for consent in Organization parties using MDM Publisher bulk load.
  • MDM Publisher fails to update sub-labels of ProcessingActivity in custommappingmodel.json.
  • Need to introduce an attribute_id field for attribute types.
  • Update code tables in MDM Publisher using custommappingmodel.json for the contact method type. When we group telephone, email, and social_media into one JSON file, only the last method type added gets loaded, while the rest are discarded.
  • Ongoing synchronization transformation issue affecting additions.
  • Ongoing synchronization transformation fails to get relationships during the transformation.
  • Ongoing synchronization workflow requirement to export the attribute_id of attribute entities to IBM Match 360.
  • Only a single consent record is returned in the transformed output, even when there are multiple consent records present in the request.
• IBM Stewardship Center fixes - The following IBM Stewardship Center issues are now resolved:
  • The Hierarchy view Orphan node view do not work with IBM Business Automation Workflow 23.0.2. Both views cause the application to crash and display an error message.
  • When there are multiple identifiers of same type, the Identifier history displays incorrect history details for the selected identifier.
  • Various security fixes.
• User interface fixes - A number of security vulnerabilities are now fixed in the Inspector, Web Reports, and Consent user interfaces.

• Operating systems
  • Microsoft Windows 10 Enterprise
  • Microsoft Windows 11 Enterprise
  • Microsoft Windows 2022 Data Center
  • Red Hat® Enterprise Linux® 8.9 (for InfoSphere MDM Standard Edition and Advanced Edition)
  • Red Hat Enterprise Linux 9.2 (for InfoSphere MDM Advanced Edition only)
  • Red Hat Enterprise Linux 8.9 on IBM Power Systems
  • AIX 7.3.x
  • Ubuntu 24.04
  • Ubuntu for POWER 20.04 LTS
  • SUSE Linux Enterprise 15.5
• Databases
  • IBM Db2 11.5.9
  • IBM Db2 13 for z/OS
  • Oracle Database 19C
  • Oracle Database 21C
  • Microsoft SQL Server 2019
  • Microsoft SQL Server 2022
• Application servers
  • IBM WebSphere Application Server 8.5.5.25
  • IBM WebSphere Application Server 9.0.5.19
• Browsers
  • Google Chrome 125.0.6422.112
  • Mozilla Firefox 126.0 (64-bit)
• Other supporting software and drivers
  • IBM MQ 9.1
  • IBM MQ 9.2
  • IBM MQ 9.3
  • IBM Business Automation Workflow 23.0.2
  • IBM Installation Manager 1.9.2.8
  • IBM Rational Application Developer 9.7.0 - Build ID: RADO97-I20181109_1539 (for the MDM Workbench platform)
  • Java™ SE 8.0.8.25
  • IBM Data Server Driver for JDBC and SQLJ 4.33.31 (db2jcc4.jar)
  • IBM Db2 JDBC Universal Driver Architecture 3.72.52 (db2jcc.jar)
  • SQL JDBC Driver 12.2, 12.4, or 12.6 (Supporting Java 8)
  • Oracle Driver: OJDBC8.jar
  • lodash 4.17.21 utility (in MDM Application Toolkit)