KEY

N
 KEY

Certified i.e. product has been tested on this specific platform combination
Content in parenthesis specifies specific certified platforms

“Supported but not certified”. This means that even though a customer will be running on a non-certified platform, In
contract. This commitment can only be given by the Product Management team in consultation with Engineering and
(Certified platforms are the platforms on which QA completed acceptance testing.)
Content in parenthesis specifies specific supported platforms.

Not Applicable/Not Available/Not Supported

 Product Availability Matrix
All versions not explicitly shown as "C" (certified) or "S" (supported) in this document are unsupported, including any hardware and software not listed in this document.
"C" (certified) or "S" (supported) indicates the level of testing we have done within Informatica. Informatica will equally support all supported platforms whether its certified or supported.
Informatica expects that customers will remain on a supported environment. In the event that a JVM, operating system, database, etc., or its version is no longer supported by its vendor, or a combination of DBMS and operating system is no longer supported by the DBMS vendor, or a
combination of application server and operating system is no longer supported by the application server vendor, then Informatica may be limited in its ability to provide support and may require you to reproduce the issue in a supported environment for continued assistance.
This Product Availability Matrix is a living document. Always check the Informatica customer support portal for the latest published version of this document.

1
Informatica Multidomain MDM, Release 10.4 HF3

MDM Hub Store (Database Server) Database Versions 2

Oracle 10 DB2 SQL Server 11 12 13 14

Operating System Supported Versions Chip Set Amazon RDS for Oracle 10.5 2012 SP4 2014 SP3 2016 SP2 2017 2019
19C, 18C, 12.2.0.1, Fix Pack 11.1 11.5 Enterprise Enterprise Enterprise Enterprise Enterprise
12.1.0.2 50 12.2.0.1 50 18C 50 19C
Fix Pack 4 Fix Pack 6
15 50 50
12.1.0.2 10 Edition 50 Edition 50 Edition 50 Edition Edition

Windows Server 2016 Standard x-64 50 x86-64 S S C C S C S S S C S S

Microsoft
Windows Server 2019 Standard x-64 x86-64 S S C C S S S S S S S S

Oracle Linux 6.x 50 x86-64 S S S S S S S

Oracle
Oracle Linux 7.1 MINIMUM x86-64 S S S S S S S

SUSE Linux Enterprise Server 12

x86-64 S S S S S S S
Service Pack 4 50
Novell
SUSE Linux Enterprise Server 15
x86-64 S S S S S S S
Service Pack 1 50

Enterprise Linux 6.8 MINIMUM 50 x86-64 S S S S S S S

Red Hat 16 Enterprise Linux 7.4 MINIMUM 50 x86-64 S S C C S S S

Enterprise Linux 8.0 MINIMUM x86-64 S S S S S S S

17 PPC-64 S S S S S S S
AIX 7.1 TL5
IBM
AIX 7.2 TL3 17 50 0 S S S S S S S

Amazon WebServices RDS N/A (Linux provisioned by Amazon) N/A S

MDM Server 3
Application Servers 4
MDM Process Server
Redhat JBoss WebLogic Server 30 WebSphere 18
Operating System Supported Versions Chip Set
9.0.0.10
EAP 7.4 EAP 7.3.6 29 EAP 7.2 EAP 7.1 50 12.2.1.4 12.2.1.3 9.0.5.3
9.0.5.2
 Windows Server 2016 Standard x-64 50 x86-64 C C C S S C C S
Microsoft
Windows Server 2019 Standard x-65 x86-64 C C C S S C C S

Oracle Linux 6.x 50 x86-64 S S S S S S

Oracle
Oracle Linux 7.1 MINIMUM x86-64 S S S S S S

SUSE Linux Enterprise Server 12

x86-64 S S S S S S S S
Service Pack 4 50
Novell 19
SUSE Linux Enterprise Server 15
x86-64 S S S S S S S S
Service Pack 1 50

Enterprise Linux 6.8 MINIMUM 50 x86-64 S C S S S S S S

RedHat 16 Enterprise Linux 7.4 MINIMUM 50 x86-64 S C C S S C S S

Enterprise Linux 8.0 MINIMUM x86-64 S C S S S S S S

17 PPC-64 20 20 20 20 S S
AIX 7.1 TL5 * * * *
IBM
AIX 7.2 TL3 17 50 PPC-64 * 20 * 20 * 20 * 20 S S

CentOS CentOS Linux 7.9.x S C C C

MDM Server 3 Java Development Kit (JDK)

MDM Process Server
Azul Zulu Oracle JRE IBM JRE

Application Server
64-bit JVM; 64-bit JVM;
JDK 1.8.x 21 50
1.8.x 50 1.8.x 22 50

Redhat JBOSS C S

WebLogic Server 23 C

WebSphere C

MDM Server 4 JDBC Driver Versions

MDM Process Server
Oracle DB2 SQL Server
Application Server
SQLJ
ojdbc7 ojdbc8 SQLJ 4.25.23 sqljdbc_4.2.8112.200 sqljdbc_6.0.8112.200
4.19.26

Redhat JBOSS C S C S C S

WebLogic Server S C S S
 WebSphere 24 S C C S S S

User Interfaces 5:
Informatica Data Director, Hub Console 6, Provisioning Tool Browsers 25 50 JRE

(Business Entity Configuration), IDD Config

Microsoft Edge Chromium-Based Edge Safari Google
Operating System Version
44 85
Firefox 80
14 Chrome 85 64-bit JRE 26

Microsoft Windows 10 C C C C C

macOS Sierra 10.12.6, macOS High Sierra 10.13.6, macOS Mojave 10.14.5, and
Apple S S S S S S
macOS Mojave 10.14.6

Integration with Informatica Intelligent Data Platform 7

Product Version

Embedded version: Name3 version 10.1 HF1

Informatica Name3 - Please contact GCS for the latest population files for use with the embedded
version of Name3

Informatica Data Quality (IDQ) Any version

Informatica PowerCenter Any version

Informatica Address Verification Address Verification 5.16

Informatica Dynamic Data Masking DDM 9.9.1

Informatica Business Process

Informatica BPM (ActiveVOS) 9.2.4.6
Management 27

6.2.3 6.8.22 6.8.6

Elasticsearch
S S C

Zero Downtime (ZDT) 8

Oracle Goldengate 12.3.0.1 with Oracle DBMS 12c
ZDT for Oracle database
Oracle Goldengate 18.1 with Oracle DBMS 18C

Oracle Goldengate 12.3.0.1.2 with DB2 11.1

ZDT for DB2 database
Oracle Goldengate 12.3.0.1.2 with DB2 10.5

Integration with External Tools 9

Trillium Trillium 14, Trillium 15

Common Warehouse Metamodel

CA ERwin Data Modeler 7
(CWM)
 D &B Direct for Informatica MDM is a product from Dunn and Bradstreet to
integrate Dunn & Bradstreet APIs and data with Informatica MDM. Information about
Dunn & Bradstreet this Dunn and Bradstreet product may be found at https://www.dnb.com/products/master-data/dnb-direct/dnb-direct-for-informatica-mdm.html
https://www.dnb.com/products/master-data/dnb-direct/dnb-direct-for-informatica-
mdm.html

Internet Protocol
Internet Protocol Internet Protocol Version 4 (IPv4)

Services & IDD Customization Development Tools

• SIF programming can be done via Java or via SOAP which is language independent. It is recommended that
customers use the RESTful Business Entity APIs that was introduced in MDM v10.

• IDD customizations for old-style IDD components (top level tabs, dashboard components, custom child tabs, custom
actions) require web application development. We have no requirements around development tools for these. However,
we recommend rather using the Entity360 framework, which simply requires XML configuration using the
Provisioning user interface introduced in v10.1.

• Localization requires a text editor that supports UTF-8 encoding.

NOTES
Virtual machines are supported - e.g. VMWare, Hyper-V, Citrix and Amazon AWS - provided that the MDM Server and MDM Process Server are deployed on a supported or certified platform configuration as defined in this product
availability matrix.

1 Note - In order to access Hub console from Citrix server:

1. Correct permission must be specified to allow download of MDM Jar file.
2. Correct permissions must be specified to allow the console logs to be created.
3. The Hub server and process server ports must be open for access on the Citrix server in case there is any firewall in between client and server.

This PAM might not have the latest information about which versions of which operating systems each DBMS supports - please refer to the DBMS's documentation for the final word on which specific versions of the operating systems listed
2
are compatible with the version of Oracle DBMS you are running.

When using Oracle as the data store, the Oracle client must be installed on every machine on which you wish to use Hub Server. This Oracle client requires Oracle Java utilities, so you must install these utilities on each machine on which
3 you have Hub Server as well. The Oracle Client and Oracle Java utilities are part of your Oracle distribution.
When using Oracle on UNIX systems, the user that starts the application erver for the system that hosts the Process Server must have Oracle in the path and Oracle home, base, and SID defined in the environment variables.

MDM can be deployed to application servers that are running in clustered mode, although MDM does not take advantage of cluster failover and session replication capabilities. See the MDM installation guide for details of how to deploy
MDM in a cluster.
(a) For Websphere in a cluster, Websphere ND (Network Deployment) is required and the supported version of WAS ND is the same as what is specified for regular Websphere in the PAM above.
4
(b) Exalogic is supported - the WebLogic version running on Exalogic must be same as WebLogic version specified in this PAM. Informatica reserves the right to request issue reproductions against WebLogic running on commodity
hardware if there is reason to believe that Exalogic is a contributing factor.

(c) You can install and run MDM in a JBOSS cluster. If you choose clustered JBOSS on install, then the EJBs will automatically be installed with clustering enabled.

5 Provisioning Tool and IDD application work best at a minimum resolution of 1920X1080.

6 Any client using MDM hub console is recommended have the same Java version as the application server. Recommended version is 1.8.x.

All of the Informatica products listed in this PAM have their own PAMs. In some cases, those other PAMs support older versions of software than MDM supports, for legacy reasons. In other cases, those other PAMs have additional, newer
7
versions of software than what MDM supports. In such cases, base your hardware and software decisions on the MDM PAM.

8 Zero Downtime (ZDT) is an add-on module for MDM that supports hardware and software upgrades in MDM database server or MDM process server with full uptime.

9 Integration with external tools is license file enabled - in order to use an MDM adapter for one of the specified tools, the MDM license key must enable that adapter.
 (a) The Enterprise Editions of the specified Oracle database versions are the main certified editions. Oracle Database Standard Edition is supported. However, Standard Edition is not recommended for high volume environments - the
reasons are the limits on partitioning, number of cores available and High Availability (limited archive modes) with Standard Edition. Customers wishing to use Oracle Standard Edition should contact Oracle to determine whether their
hardware configuration is supported.

(b) Oracle RAC is supported - For important information about installing MDM in a RAC environment see the Oracle RAC guidelines for MDM published in the How-To-Library (H2L) in Informatica's customer portal. MDM only uses the
JBDC thin driver so the TAF feature will not work.
10
(c) Oracle database running on Exadata or Oracle SuperCluster is supported - MDM guidelines for running on RAC should be followed for Exadata and SuperCluster too. Informatica reserves the right to request issue reproductions against
Oracle running on commodity hardware if there is reason to believe that Exadata or SuperCluster is a contributing factor.

(d) Follow Oracle documentation to configure PDB/CDB to support multi-tenant architecture

(e) Transparent Database Encryption (TDE) is supported for Oracle databases at the tablespace level.

Microsoft SQL Server is only supported on the specified Microsoft Windows versions however the application server can be implemented on any supported Linux server.
11
If you install the application server on UNIX and Linux, you need an ODBC driver for Microsoft SQL Server so that data sources can be created. More details can be found on the MDM Installation guide.

Recommendation is to use Enterprise Edition of SQL Server however the Standard Edition of SQL Server can be used for low volume or non-production environments. If performance issues are encountered that appear to be DBMS
12
related, GCS will recommend that the Enterprise Edition be used instead.

Limited statement of support for Azure:

Informatica MDM requires a supported or certified platform configuration as defined in its product availability matrix (PAM).

We will support MDM v10+ running on Azure Cloud, provided that the database, application server and operating system versions and editions are already specified in the MDM PAM.

13 We do not support MDM installed in Azure SQL Database, or in fact any multitenant implementations of SQLServer. If you want to use MDM in an Azure environment, then you have to use Azure as a virtual server where you install a
SQLServer edition that is in our PAM.

We do not support Azure Active Directory (Azure AD) with MDM. We have out of the box support for LDAP, on-premise Active Directory and Kerberos. However, Azure AD does not expose the same interfaces as on-premise Active
Directory, and it does not support LDAP or Kerberos, so you would not be able to use our out-of-the-box AD login provider. Customers wishing to use Azure AD for authentication will have to create their own custom login provider in order to
use Azure AD for authentication. Global Customer Support and the support portal (network.informatica.com) have more information on custom login providers.

14 Transparent Database Encryption (TDE) is supported for SQL Server databases at the database level.

15 Certified environment in Amazon Web Services runs the following combination: Oracle Amazon RDS, with JBOSS on both Windows and Linux operating systems.

16 Stated RHEL versions are minimum accepted versions. Later versions on the same major version (e.g., RHEL 7.4, 8.0) are acceptable versions.

ElasticSearch is not supported on AIX. If you plan to use Smart Search and your application server runs on AIX, you will need to deploy ElasticSearch on a separate server that is supported for ElasticSearch (see
17
https://www.elastic.co/support/matrix).
(a) IBM JVM is only supported on AIX or with WebSphere.
18 (b) Environments using the IBM JVM should use the same JVM version for the MDM Server, supporting Process Servers, and the embedded Informatica Platform. This JVM must be sourced from IBM.
(c) Regardless of the JVM source, MDM Server and the supporting Application Server must be executed using a separate JVM from the one which in which Informatica Platform executes.

19 Redhat JBOSS EAP's PAM does not include SUSE Linux as a supported version. Informatica does not recommend using the operating systems if the application server is JBOSS.

There are multiple issues with JBOSS 7.x running on AIX, and AIX is not one of Redhat's tested platforms for JBOSS 7.x (https://access.redhat.com/articles/2026253). Informatica will try in good faith to address these issues in 10.4 HF1, but
20
cannot guarantee that we will be able to do so. Please see MDM 10.4 HF1 Release Notes for details of the issues with this combination. Customers are recommended to avoid this combination of application server and operating system.

We will provide Azul Zulu JDK for JBOSS EAP 7.1, 7.2 and 7.3. Please contact Informatica Global Customer Support for Azul Zulu JDK 1.8.x.
21
We do not support other vendors of Open JDK or community versions for JBOSS.

22 ElasticSearch is not supported with IBM's JVM. If you plan to use Smart Search and your application server is Websphere, you will need to deploy ElasticSearch in a separate JVM using either Oracle JRE or Open JDK.

23 Recommended Oracle JRE version for WebLogic Application Server is 1.8.0_181+.

JDBC driver to be used with DB2 10.5 is 4.19.26.

24
JDBC driver to be used with DB2 11.1 is 4.25.23.
 64-bit versions of the browsers are supported.
25
Browser versions indicate what was used for QA testing.

26 Minimum recommended Java client version is 1.8.144 - lower versions of the client JRE will cause Hub Console to not work.

27 Patches for Informatica BPM (ActiveVOS) need to be downloaded and installed separately

Informatica highly recommends using EJBs via our api (SiperianClient class from siperia-api.jar) to avoid any issues in future if we need to change the way how EJBs are looked up however it is possible to use EJB 3.0 or EJB 3.1 to call
28
SIFs directly.

29 For JBoss 7.3 the mandatory patch level 6 (7.3.6) needs to be added to avoid memory leak.

Weblogic Enterprise Edition is recommended, and is the version that Informatica certifies on. Enterprise Edition includes clustering support which we recommend using for scalability and availability. If you choose to use Standard Edition,
30
you will not be able deploy MDM servers in a clustered architecture which will limit your ability to scale the solution.

50 PLATFORM DEPRECATION NOTICES

Windows Server 2016 MDM 10.4 is the last major release that will support Windows Server 2016.

Oracle Linux 6 MDM 10.4 is the last major release that will support Oracle Linux 6.

SUSE Linux Enterprise Server 15

MDM 10.4 is the last major release that will support SUSE Linux Enterprise Server 15 Service Pack 1.
Service Pack 1

SUSE Linux Enterprise Server 12

MDM 10.4 is the last major release that will support SUSE Linux Enterprise Server 12 Service Pack 4.
Service Pack 4

Redhat Enterprise Linux 6.x MDM 10.4 is the last major release that will support Redhat Enterprise Linux 6.x.

Redhat Enterprise Linux 7.x MDM 10.4 is the last major release that will support Redhat Enterprise Linux 7.x.

IBM AIX 7.2 with Technology Level

MDM 10.4 is the last major release that will support IBM AIX 7.2 with Technology Level 3.
3

Oracle 18c MDM 10.4 is the last major release that will support Oracle 18c.

Oracle 12.2.0.1 MDM 10.4 is the last major release that will support Oracle 12.2.0.1.

Oracle 12.1.0.2 MDM 10.4 is the last major release that will support Oracle 12.1.0.2.

DB2 10.5 MDM 10.4 is the last major release that will support DB2 10.5.

Microsoft SQL Server 2016 Service

MDM 10.4 is the last major release that will support Microsoft SQL Server 2016 Service Pack 2.
Pack 2

Microsoft SQL Server 2014 Service

MDM 10.4 is the last major release that will support Microsoft SQL Server 2014 Service Pack 3.
Pack 3

Microsoft SQL Server 2012 Service

MDM 10.4 is the last major release that will support Microsoft SQL Server 2012 Service Pack 4.
Pack 4

JBOSS 7.1 MDM 10.4 is the last major release that will support JBOSS 7.1.
 JRE 1.8 version MDM 10.4 is the last major release that will support JRE 1.8 version.

Firefox 80 and below MDM 10.4 is the last release that will support Firefox 80 (lower releases are already deprecated).

Chrome 85 and lower MDM 10.4 is the last release that will support Chrome 85 (lower releases are already deprecated)

Safari MDM 10.4 is the last release that will support Safari 14 (lower releases are already deprecated)

Microsoft Edge 44 and lower MDM 10.4 is the last release that will support Microsoft Edge 44 (lower releases are already deprecated)

These deprecation notices also apply to the equivalent versions of Customer 360 and Supplier 360
CHANGES SINCE PAM FOR MULTIDOMAIN MDM 10.4 HotFix 2
CHANGES SINCE PAM FOR MULTIDOMAIN MDM 10.4 HotFix 2
 PREVIOUSLY DEPRECAT

MDM Features Operating System

Subject Area
Red Hat Linux 5.x
Based IDD

Red Hat Linux 6.6 or earlier

SUSE Linux Enterprise Server 10 or earlier

SUSE Linux Enterprise Server 11 (SP1, SP2, SP3, SP4)
SUSE Linux Enterprise Server 12 (SP1, SP2, SP3)
SUSE Linux Enterprise Server 14 (SP1, SP2)
SUSE Linux Enterprise Server 16 (SP1)

Windows XP

Windows 2003 Server

Oracle Enterprise Linux 5.x

AIX 5.x, 6.x

Windows Vista

Windows 7

Windows 8.1
 PREVIOUSLY DEPRECATED OR SUPERSEDED VERSIONS

Application Servers Database Hub Server OR Client Java

Jboss 6.x or earlier Java 7 or earlier

WebLogic 10.3.6 or earlier Oracle 10g or earlier 32-bit JVM

SQL Server 2008 R2

WebSphere 8.5.5.2 or earlier
Enterprise Edition

HP-UX DB2 9.7

Solaris Oracle 11gR2

SIONS

External Tools Browsers Other

Fujitsu BPM Safari 11 or earlier DDM 9.6.0

GroupOne Chrome 71 or earlier HP PA-RISC hardware

Firefox 68 or earlier, Firefox 32-bit hardware, operating

Lombardi BPM
ESR 60.8 or earlier systems and JVMs

Trillium 13 or earlier Microsoft Edge v41 or earlier Goldengate 11

IBM ILOG charts 32-bit Browsers EJB2 protocol

AddressDoctor 5.10

Embedded version: Name3

version 10.0 HF1

Powercenter Adapter
(legacy; use Informatica
Platform with Vibe Data
Integration Engine rather)