Oracle Commerce 11.3.0.

0
Support for 3rd Party Environments1,2,15,17,21

Vendor Version Notes

Oracle WebLogic (WLS) 12.2.1 12.1.3
Application Server3,19
IBM WebSphere (WAS) 9.0
JBoss 7.0 EAP

Vendor Version Notes

Oracle 22 Oracle Exadata5
Oracle 22 12cR2 (12.2.0.x)
Oracle 22 12cR2 RAC (12.2.0.x)
Oracle 22 12cR1 (12.1.0.x)
Database6 Oracle 22 12cR1 RAC (12.1.0.x)
Oracle 22 11gR2 (11.2.0.x)
Oracle 22 11gR2 RAC (11.2.0.x)
IBM DB24 10.5
MSSQL4,7 2014
MySQL8 (Dev Only) 5.7.x

Vendor Version Bit Support Processors Notes

Oracle Linux12 6.7, 7.2 64 bit Intel/AMD x86-64, Oracle Exalogic 5
Oracle Solaris 10, 11 64 bit SPARC10 Guided Search and Experience Manager components support Solaris 11 only
AIX9 7.1 64 bit POWER Not supported with Guided Search and Experience Manager components
Operating System6,16
Red Hat Linux 6.7, 7.2 64 bit Intel/AMD x86-64
Windows 2012 R2 Standard, Datacenter 64 bit Intel/AMD x86-64
Windows 7 (Dev Only) 64 bit Intel/AMD x86-64
Windows 8.1 (Dev Only) 64 bit Intel/AMD x86-64
Windows 10 (Dev Only) 64 bit Intel/AMD x86-64
SUSE 11 SP1 64 bit Intel/AMD x86-64 Deprecated: Guided Search and Experience Manager components only 18

Vendor Version Database App Server Notes

Oracle Thin 11.2.0.4, 12.1.x Oracle (all supported versions) JBoss, WLS, WAS ojdbc7.jar must be used with JDK 1.8
Driver version is dependent on DB2 Fixpack used. 3.67.26 relates to 10.5FP2.
DB2 Universal Driver 3.67.26 DB2 JBoss, embedded in platform for WAS
JDBC Driver11 See http://www-01.ibm.com/support/docview.wss?uid=swg21363866 for further info.
iNet Merlia 8.0.6 MSSQL JBoss, WLS
Microsoft SQL Server JDBC 4.1, 4.2 MSSQL JBoss, WLS
MySQL Connect (Dev Only) 5.1.38 MySQL Jboss, WLS

Vendor Version OS App Server Notes

JDK20
Oracle Java 1.8.0_121 (64-bit) RH Linux, Oracle Linux, Solaris, Windows JBoss, WLS RH Linux, Oracle Linux, Solaris, Windows
IBM SDK 8.0 (64-bit) AIX, RH Linux, Solaris, Windows WAS AIX, RH Linux, Solaris, Windows

Vendor Version Notes

VMWare ESXi 4.1
Virtualization13 OVM Server for x86 3.x
OVM Server for SPARC 3.x
Amazon EC2 Guided Search and Experience Manager components only
Solaris Zones (containers) Solaris 10, 11
Solaris LDOM Solaris 10, 11
Oracle Linux 6.7, 7.2, WebLogic Server 12.1.3, 12.2.1 Oracle DB (DBaaS) 11.2.0.x,
Oracle Public Cloud, Cloud Machine Compute, DBCS 12.1.x, Oracle JDBC Thin 11.2.0.4, 12.1.x, JDK1.8.0_121, Oracle BI 12.2.1.2 only.

Vendor Version Notes

Adobe Flash Player 24 and later
Firefox 45.x ESR
Browsers14 Internet Explorer 11
Microsoft Edge 38 and later
Chrome 57 and later
Safari 10 Guided Search and Experience Manager components only

Product Version Notes

External Caching8
Oracle Coherence 12.2.1, 12.1.3 Not supported with Guided Search and Experience Manager components
Oracle Coherence Web 12.2.1, 12.1.3 WebLogic only (for external session management)

Product Version Notes

Business Intelligence
Oracle Business Intelligence Enterprise Edition 12.2.1.2

Product Version Notes

WebCenter Sites
Oracle WebCenter Sites 11.1.1.8

Product Version Notes

Development Plugins
Eclipse 3.7 JEE Not supported with Guided Search, MDEX and Experience Manager components

Product Version Notes

Access Manager
Oracle Access Manager 11gR2

Product Version Notes

.NET Framework
2.0, 4.5 Guided Search and MDEX components only

General Information
1
This document reflects the best information available as of the date published. The information is subject to change.
2
The Oracle Commerce suite is comprised of several components. Except where explicitly noted, all components must be running on the same product version.
3
Oracle recommends use of an HTTP server supported by these app servers.
4
Oracle Commerce supports MSSQL and MySQL only in combination with either JBoss or WLS app servers. Oracle Commerce supports DB2 only in combination with WAS and JBoss app servers.
5
Oracle Commerce supports Oracle Exalogic X2-2 and higher, and Oracle Exadata versions X2-2, X2-8 and higher.
6
Customers may run databases on any operating system supported by the database vendor except for mainframe operating systems (including z/OS), which are not supported.
7
Oracle Commerce does not support Unicode or n type string columns with MSSQL at this time. Oracle Commerce supports all the code pages that MS SQL Server supports.
8
More information regarding Oracle Coherence compatibility with Oracle Commerce can be found in KM article 1549727.1
9
Customers installing on the AIX operating system may only run Oracle Commerce with the WAS application server.
10
SPARC support includes tradtional SPARC processors and SuperCluster.
11
Oracle Commerce requires XA drivers.
12
Oracle Linux is supported with both the Oracle Unbreakable Enterprise Kernel and the Red Hat Compatible Kernel.
13
Use of virtualization will require additional hardware to maintain throughput volumes relative to a non-virtualized environment. Application response times will be slower relative to a non-virtualized environment.
14
The Oracle Commerce Platform is a framework and can support any browser that applications built on top of it are designed to support. Browser support here refers to Oracle Commerce products, UIs and tools.
15
Oracle Commerce supports MDEX version 11.3.0
16
Support for the standalone ACC is limited to Windows, Red Hat Linux and Oracle Linux.
17
Oracle Commerce Customer Intelligence reports require Oracle Business Intelligence, which is certified on a different third party environments matrix.
18
SUSE is fully supported in Oracle Commerce 11.3 for Guided Search and Experience Manager components only. SUSE is considered deprecated and Oracle Commerce 11.3 may be the final release that includes SUSE support.
19
Application Servers do not apply to the Workbench component.
20
The Assembler, Presentation, and CAS client APIs are supported in JVMs running 1.6 and higher. The Assembler API includes the core search and navigation cartridges.
21
Point versions above than those stated here are automatically supported for certain products. For detailed information on this please see KM article 1555914.1
22
Oracle strongly encourages Enterprise Edition for customers with high availability requirements in order to access troubleshooting features which may help minimize delays in issue resolution.