Every Red Hat Fuse release is tested and supported on a variety of market-leading operating systems, Java™ Virtual Machines (JVMs), and database combinations. Red Hat provides both production and development support for supported configurations and tested integrations according to your subscription agreement in both physical and virtual environments.[1]

Red Hat Fuse 7.1

Red Hat Fuse 7.1 on OpenShift

OpenShift Deployment

In order to be running in a supported configuration, Fuse on OpenShift must be running on a supported version of OpenShift Container Platform (OCP). The following versions of OCP were tested against Red Hat Fuse 7.1 on OpenShift at the time of the relevant OCP GA release:

OpenShift Product	Versions
OpenShift Container Platform (OCP)	3.9 3.10

When newer versions of OCP become available, users should plan to upgrade as soon as possible to incorporate critical fixes and take advantage of new enhancements. For more information, please contact support.

Standalone Spring Boot Deployment

Standalone Spring Boot deployment (Jar file running on a supported JVM) is supported by Red Hat, provided your application uses the dependencies from the Spring Boot BOM (Apache Maven Bill of Materials) file for Spring Boot. For limitations on Spring Boot support, see section Spring Boot Support below.

Spring Boot Support

Red Hat Fuse 7.1 on OpenShift is reliant on the Spring Boot Community version and as a such, Red Hat's support for Spring Boot is limited to its intended use as documented in the quickstarts and templates. We will offer a commercially reasonable effort to support Spring Boot, however, we may not be able to provide or influence timely patches.

For more details, see Spring Boot Support.

Red Hat Fuse 7.1 Supported Configurations

Red Hat provides both production and development support for supported configurations according to your subscription agreement in both physical and virtual environments [1].

Note: Red Hat Fuse 7.1 includes an entitlement to Red Hat AMQ, and an entitlement to JBoss Enterprise Application Platform (possibly, more than one version of each). Supported versions of AMQ and JBoss EAP are shown in the tables below.

Supported Java Versions

In order to be running in a supported configuration, Red Hat Fuse 7.1 must be running in one of the following JVM versions and on one of the operating systems supported by that JVM.

Java Virtual Machine	Version
OpenJDK [2]	1.8
Oracle JDK	1.8
IBM JDK	1.8
HP JVM	1.8

Supported JBoss EAP Versions

For Fuse on EAP installations, the following versions of JBoss Enterprise Application Platform (EAP) are supported:

Java EE Container	Version
JBoss Enterprise Application Platform	7.1

Note: We recommend installing the latest patch for JBoss EAP.

Red Hat Fuse 7.1 Tested Configurations

Red Hat has performed the full range of platform tests on the following tested configurations:

Operating System	Chipset Architecture	Java Virtual Machine
Red Hat Enterprise Linux 7 (latest update) [3]	x86_64	Oracle JDK 1.8.x IBM JDK 1.8.x OpenJDK 1.8.x
Microsoft Windows Server 2016	x86_64	Oracle JDK 1.8.x
Oracle Solaris 11 [4]	SPARC64	Oracle JDK 1.8.x
IBM AIX 7.2	Power ISA	IBM JDK 1.8.x
HP-UX 11i	IA64	HP JVM 1.8.x

Red Hat Fuse 7.1 Tested Integrations

Tested Integrations are a defined set of specifically tested integrating technologies that represent the most common combinations that Enterprise Middleware customers are using. For these integrations, Red Hat has directly, or through certified partners, exercised our full range of platform tests as part of the product release process. Issues identified as part of this testing process are highlighted in release notes for each Fuse release. This list of tested integrations will expand over time.

Red Hat provides both production and development support for the tested integrations in the same major version family at or above the tested version according to your subscription agreement. Earlier versions of a tested integration in the same major version family are supported on a commercially reasonable basis.

Supported Database Integrations

The following databases and database drivers were tested as part of the latest Red Hat Fuse 7 release.

Databases	JDBC Driver
Oracle 12c	Oracle JDBC Driver v12
Oracle 12c RAC	Oracle JDBC Driver v12
MySQL 5.7	MySQL Connector/J 5
Microsoft SQL Server 2014	MS SQL Server JDBC Driver 6.0
Microsoft SQL Server 2016	MS SQL Server JDBC Driver 6.0
PostgreSQL 9.3.5	JDBC 4.2 Postgresql Driver, Version 9
PostgreSQL 9.6	JDBC 4.2 Postgresql Driver, Version 9
PostgreSQL 10.1	JDBC 4.2 Postgresql Driver, Version 9
IBM DB2 9.7	IBM DB2 JDBC Universal Driver Architecture 4.14
IBM DB2 10.5	IBM DB2 JDBC Universal Driver Architecture 4.19

Supported Messaging Providers

Since Fuse 7.0, only remote brokers are supported.

Broker	Version	Target Containers
JBoss A-MQ	6.3	Apache Karaf JBoss EAP Spring Boot
AMQ	7.1	Apache Karaf JBoss EAP Spring Boot
Websphere MQ¹	8.0	Apache Karaf JBoss EAP Spring Boot
Websphere MQ¹	9.0	Apache Karaf Spring Boot

1 We test against the latest available micro version of the Websphere MQ client each time a JBoss Fuse patch is released for the associated container. The Websphere MQ certification is client only and not a specific broker certification. Please refer to the IBM documentation regarding supported client and broker combinations.

Supported Messaging Clients

The following messaging clients and JCA adapters have been tested for Red Hat Fuse 7.0.

The following messaging components are supported on Apache Karaf:

Apache Karaf
Broker	Version	Client	Camel components
JBoss A-MQ	6.3	`activemq-client`	`camel-activemq`
AMQ	7.1	`artemis-jms-client`	`camel-jms` `camel-sjms` `camel-sjms2`
AMQ	7.1	`qpid-jms-client`	`camel-amqp`
WebSphere MQ	8.0	Client v8	`camel-jms` (not testedI)
WebSphere MQ	9.0	Client v9	JMS API from Java code

Messaging on the JBoss EAP container is supported using JCA apapters, see JBoss EAP 7.1 Supported Configurations. The following messaging components are supported on JBoss EAP 7.1:

JBoss EAP
Broker	Version	Adapter	Camel components
JBoss A-MQ	6.3	AMQ JCA Adapter v5.11.0	`camel-activemq`
AMQ	7.1	AMQ JCA Adapater which is integrated in JBoss EAP 7.1	`camel-jms` `camel-sjms`
WebSphere MQ	8.0	WebSphereMQ MCA adapter	`camel-jms`

The following messaging components are supported on Spring Boot:

Spring Boot
Broker	Version	Client	Camel components
JBoss A-MQ	6.3	`activemq-client`	`camel-activemq`
AMQ	7.1	`artemis-jms-client`	`camel-jms` `camel-sjms` `camel-sjms2`
AMQ	7.1	`qpid-jms-client`	`camel-amqp`
WebSphere MQ	8.0	Client v8	`camel-jms` (not testedI)
WebSphere MQ	9.0	Client v9	`camel-jms`

In the case of the ActiveMQ client connection factory (OpenWire), the client version corresponds to the version that is packaged with each of the containers in Red Hat Fuse 7.0 (Apache Karaf, JBoss EAP, and Spring Boot, respectively).

Supported Web Server Integrations

Certain components of the Fuse distribution are supported on a Web server, when deployed in a WAR file as a dependency to your application. Components that are supported on other containers are provided in a separate download from the customer portal.

Fuse Component	Version	Container	Version
Camel	2.21.0.fuse-710018-redhat-00001	JWS	5.0

Red Hat Fuse 7.1 Supported Browsers for use with the Hawt.io console

In general, we recommend that you use the latest available version of each browser type (to ensure that you have the latest security updates and so on). We have tested each of the browsers listed below using the latest version available at the time of the Red Hat Fuse 7.1 release.

Browser
Mozilla Firefox
Google Chrome
Microsoft Edge

Red Hat Fuse 7.0

Red Hat Fuse 7.0 on OpenShift

OpenShift Deployment

In order to be running in a supported configuration, Fuse on OpenShift must be running on a supported version of OpenShift Container Platform (OCP). The following versions of OCP were tested against Red Hat Fuse 7.0 on OpenShift at the time of the relevant OCP GA release:

OpenShift Product	Versions
OpenShift Container Platform (OCP)	3.9

Standalone Spring Boot Deployment

Spring Boot Support

Red Hat Fuse 7.0 on OpenShift is reliant on the Spring Boot Community version and as a such, Red Hat's support for Spring Boot is limited to its intended use as documented in the quickstarts and templates. We will offer a commercially reasonable effort to support Spring Boot, however, we may not be able to provide or influence timely patches.

For more details, see Spring Boot Support.

Red Hat Fuse 7.0 Supported Configurations

Red Hat provides both production and development support for supported configurations according to your subscription agreement in both physical and virtual environments [1].

Note: Red Hat Fuse 7.0 includes an entitlement to Red Hat AMQ, and an entitlement to JBoss Enterprise Application Platform (possibly, more than one version of each). Supported versions of AMQ and JBoss EAP are shown in the tables below.

Supported Java Versions

In order to be running in a supported configuration, Red Hat Fuse must be running in one of the following JVM versions and on one of the operating systems supported by that JVM.

Java Virtual Machine	Version
OpenJDK [2]	1.8
Oracle JDK	1.8
IBM JDK	1.8
HP JVM	1.8

Supported JBoss EAP Versions

For Fuse on EAP installations, the following versions of JBoss Enterprise Application Platform (EAP) are supported:

Java EE Container	Version
JBoss Enterprise Application Platform	7.1

Note: We recommend installing the latest patch for JBoss EAP.

Red Hat Fuse 7.0 Tested Configurations

Red Hat has performed the full range of platform tests on the following tested configurations:

Operating System	Chipset Architecture	Java Virtual Machine
Red Hat Enterprise Linux 7 (latest update) [3]	x86_64	Oracle JDK 1.8.x IBM JDK 1.8.x OpenJDK 1.8.x
Microsoft Windows Server 2016	x86_64	Oracle JDK 1.8.x
Oracle Solaris 11 [4]	SPARC64	Oracle JDK 1.8.x
IBM AIX 7.2	Power ISA	IBM JDK 1.8.x
* HP-UX 11i	IA64	HP JVM 1.8.x

*Note that there is an issue on HP-UX which affects launching the Apache Karaf container. For details, see the _Known Issues_ section of the Red Hat Fuse 7.0 "Release Notes". This issue is fixed in the Red Hat Fuse 7.0.1 release.

Red Hat Fuse 7.0 Tested Integrations

Tested Integrations are a defined set of specifically tested integrating technologies that represent the most common combinations that JBoss Enterprise Middleware customers are using. For these integrations, Red Hat has directly, or through certified partners, exercised our full range of platform tests as part of the product release process. Issues identified as part of this testing process are highlighted in release notes for each Fuse release. This list of tested integrations will expand over time.

Supported Database Integrations

The following databases and database drivers were tested as part of the latest Red Hat Fuse 7 release.

Databases	JDBC Driver
Oracle 12c	Oracle JDBC Driver v12
Oracle 12c RAC	Oracle JDBC Driver v12
MySQL 5.7	MySQL Connector/J 5
Microsoft SQL Server 2014	MS SQL Server JDBC Driver 6.0
Microsoft SQL Server 2016	MS SQL Server JDBC Driver 6.0
PostgreSQL 9.3.5	JDBC 4.2 Postgresql Driver, Version 9
IBM DB2 9.7	IBM DB2 JDBC Universal Driver Architecture 4.14
IBM DB2 10.5	IBM DB2 JDBC Universal Driver Architecture 4.19

Supported Messaging Providers

Since Fuse 7.0, only remote brokers are supported.

Broker	Version	Target Containers
JBoss A-MQ	6.3	Apache Karaf JBoss EAP Spring Boot
AMQ	7.1	Apache Karaf JBoss EAP Spring Boot
Websphere MQ¹	8.0	Apache Karaf JBoss EAP Spring Boot
Websphere MQ¹	9.0	Apache Karaf Spring Boot

Supported Messaging Clients

The following messaging clients and JCA adapters have been tested for Red Hat Fuse 7.0.

The following messaging components are supported on Apache Karaf:

Apache Karaf
Broker	Version	Client	Camel components
JBoss A-MQ	6.3	`activemq-client`	`camel-activemq`
AMQ	7.1	`artemis-jms-client`	`camel-jms` `camel-sjms` `camel-sjms2`
AMQ	7.1	`qpid-jms-client`	`camel-amqp`
WebSphere MQ	8.0	Client v8	`camel-jms` (not testedI)
WebSphere MQ	9.0	Client v9	JMS API from Java code

Messaging on the JBoss EAP container is supported using JCA apapters, see JBoss EAP 7.1 Supported Configurations. The following messaging components are supported on JBoss EAP 7.1:

JBoss EAP
Broker	Version	Adapter	Camel components
JBoss A-MQ	6.3	AMQ JCA Adapter v5.11.0	`camel-activemq`
AMQ	7.1	AMQ JCA Adapater which is integrated in JBoss EAP 7.1	`camel-jms` `camel-sjms`
WebSphere MQ	8.0	WebSphereMQ MCA adapter	`camel-jms`

The following messaging components are supported on Spring Boot:

Spring Boot
Broker	Version	Client	Camel components
JBoss A-MQ	6.3	`activemq-client`	`camel-activemq`
AMQ	7.1	`artemis-jms-client`	`camel-jms` `camel-sjms` `camel-sjms2`
AMQ	7.1	`qpid-jms-client`	`camel-amqp`
WebSphere MQ	8.0	Client v8	`camel-jms` (not testedI)
WebSphere MQ	9.0	Client v9	`camel-jms`

Supported Web Server Integrations

Fuse Component	Version	Container	Version
Camel	2.21.0.fuse-000077-redhat-1	JWS	5.0

Red Hat Fuse 7.0 Supported Browsers for use with the Hawt.io console

Browser
Mozilla Firefox
Google Chrome
Microsoft Edge

Red Hat JBoss Fuse 6.3

JBoss Fuse Integration Services for JBoss Fuse 6.3

OpenShift Deployment

In order to be running in a supported configuration, Fuse Integration Services (FIS) 2.0 must be running on a supported version of OpenShift Container Platform (OCP). The following versions of OCP were tested against FIS 2.0 at the time of the relevant OCP GA release:

OpenShift Product	Versions
OpenShift Container Platform (OCP)	3.3 (deprecated) 3.4 (deprecated) 3.5 (deprecated) 3.6 (deprecated) 3.7 3.9

Standalone Spring Boot Deployment

Standalone Spring Boot deployment (Jar file running on a supported JVM) is supported by Red Hat, provided your application uses the dependencies from the FIS 2.0 BOM (Apache Maven Bill of Materials) file for Spring Boot. For limitations on Spring Boot support, see section Spring Boot Support below.

Supported Camel Versions

In this release, the supported version of Apache Camel depends on which container image you are using, as follows:

Container Type	Image	Camel Version
Spring Boot	`fis-java-openshift`	Camel 2.18.1
Apache Karaf	`fis-karaf-openshift`	Camel 2.17

NOTE: Only the productized distributions of Camel 2.18.1 and Camel 2.17 are supported.
For the exact version numbers (which have a build number embedded in them), see the dependencies declared in the pom.xml files of the FIS 2.0 quickstarts and archetypes.

Spring Boot Support

Fuse Integration Services v2.0 is reliant on the Spring Boot Community version and as a such, Red Hat's support for Spring Boot is limited to its intended use as documented in the quickstarts and templates. We will offer a commercially reasonable effort to support Spring Boot, however, we may not be able to provide or influence timely patches.

JBoss Fuse 6.3 Supported Configurations

Red Hat provides both production and development support for supported configurations according to your subscription agreement in both physical and virtual environments [1].

Note: JBoss Fuse 6.3 includes an entitlement to JBoss A-MQ, and an entitlement to JBoss Enterprise Application Platform (possibly, more than one version of each). Supported versions of JBoss A-MQ and JBoss EAP are shown in the tables below.

Supported Java Versions

In order to be running in a supported configuration, JBoss Fuse must be running in one of the following JVM versions and on one of the operating systems supported by that JVM.

Java Virtual Machine	Version
OpenJDK [2]	1.7 1.8
Oracle JDK	1.7 1.8
IBM JDK	1.7 1.8
HP JVM	1.7 1.8

Supported JBoss EAP Versions

For JBoss Fuse on EAP installations, the following versions of JBoss Enterprise Application Platform (EAP) are supported:

Java EE Container	Version
JBoss Enterprise Application Platform	6.4

Note: We recommend installing the latest patch for JBoss EAP.

JBoss Fuse 6.3 Tested Configurations

Red Hat has performed the full range of platform tests on the following tested configurations:

Operating System	Chipset Architecture	Java Virtual Machine
Red Hat Enterprise Linux 7 (latest update) [3]	x86_64	Oracle JDK 1.7.x Oracle JDK 1.8.x IBM JDK 1.7.x IBM JDK 1.8.x OpenJDK 1.7.x OpenJDK 1.8.x
Red Hat Enterprise Linux 6 (latest update) [3]	x86	Oracle JDK 1.7.x Oracle JDK 1.8.x OpenJDK 1.7.x OpenJDK 1.8.x
Red Hat Enterprise Linux 6 (latest update) [3]	x86_64	Oracle JDK 1.7.x Oracle JDK 1.8.x IBM JDK 1.7.x IBM JDK 1.8.x OpenJDK 1.7.x OpenJDK 1.8.x
Microsoft Windows Server 2012 R2	x86_64	Oracle JDK 1.7.x Oracle JDK 1.8.x
Oracle Solaris 10 [4]	x86 x86_64 SPARC64	Oracle JDK 1.7.x Oracle JDK 1.8.x
Oracle Solaris 11 [4]	x86 x86_64 SPARC64	Oracle JDK 1.7.x Oracle JDK 1.8.x
IBM AIX 7.1	Power ISA v.2.06	IBM JDK 1.7.x IBM JDK 1.8.x
HP-UX 11i	IA64	HP JVM 1.7.x HP JVM 1.8.x

JBoss Fuse 6.3 Tested Integrations

Tested Integrations are a defined set of specifically tested integrating technologies that represent the most common combinations that JBoss Enterprise Middleware customers are using. For these integrations, Red Hat has directly, or through certified partners, exercised our full range of platform tests as part of the product release process. Issues identified as part of this testing process are highlighted in release notes for each JBoss Fuse release. This list of tested integrations will expand over time.

Supported Database Integrations

The following databases and database drivers were tested as part of the latest JBoss Fuse 6 release.

Databases	JDBC Driver
Oracle 12c	Oracle JDBC Driver v12
Oracle RAC	Oracle JDBC Driver v12
MySQL 5.6	MySQL Connector/J 5
Microsoft SQL Server 2008	MS SQL Server JDBC Driver 3
Microsoft SQL Server 2012	MS SQL Server JDBC Driver 4
Microsoft SQL Server 2014	MS SQL Server JDBC Driver 4
PostgreSQL 9.3.5	JDBC 4 Postgresql Driver, Version 9
IBM DB2 9.7	IBM DB2 JDBC Universal Driver Architecture 4.9.78

Supported Messaging Providers

The following messaging providers are supported:

Messaging Provider	Version	Target Container	Integration Type
JBoss A-MQ	6.3	Apache Karaf	Remote Broker and Embedded Broker
	6.3	JBoss EAP	Remote Broker
	6.3	Spring Boot	Remote Broker
JBoss AMQ	7.x	Apache Karaf	Remote Broker
	7.x	JBoss EAP	Remote Broker
	7.x	Spring Boot	Remote Broker
Websphere MQ client¹	7.5.x 8.0.x	Apache Karaf	Remote Broker

¹ We test against the latest available micro version of the Websphere MQ client each time a JBoss Fuse patch is released. The Websphere MQ certification is client only and not a specific broker certification. Please refer to the IBM documentation regarding supported client and broker combinations.

Where Remote Broker implies that the messaging client (which includes Websphere MQ clients, and Camel messaging components, such as camel-jms) can connect to the remotely deployed broker; and Embedded Broker implies that the broker can be embedded inside an Apache Karaf container.

JBoss Fuse 6.3 with JBoss AMQ 7.0 Certification

The following messaging clients deployed in a JBoss Fuse 6.3 container have been tested against the AMQ 7.0 broker.

		Container Type
Camel component	Client	Apache Karaf	JBoss EAP	Spring Boot
`camel-amqp`	Qpid JMS client 0.9.0 connection factory (AMQP 1.0)	Yes	X	Yes
`camel-amqp`	Qpid JMS client 0.9.0 connection factory (AMQP 1.0) connected to Interconnect Router	Yes*	X	X
`camel-jms`	Qpid JMS client 0.9.0 connection factory (AMQP 1.0)	Yes	X	X
`camel-jms`	Artemis client connection factory (version `2.0.0.amq-700011-redhat-1`)	X	X	Yes
`camel-jms`	ActiveMQ client connection factory (OpenWire)	Yes	Yes	Yes
`camel-jms` with XA	ActiveMQ client connection factory (OpenWire)	Yes	X	X
`camel-activemq`	ActiveMQ client connection factory (OpenWire)	Yes	Yes	Yes
`camel-mqtt`		Yes	Yes	Yes

Where X = not tested.

In the case of the ActiveMQ client connection factory (OpenWire), the tested client version corresponds to the version that is packaged with each of the containers in JBoss Fuse 6.3 (Apache Karaf, JBoss EAP, and Spring Boot, respectively).

Note: For information about using JMS client selectors with the Interconnect Router, see ENTMQIC-1941.

Supported Web Server Integrations

Certain components of the JBoss Fuse distribution are supported on a Web server, when deployed in a WAR file as a dependency to your application. Components that are supported on other containers are provided in the /extras directory of the JBoss Fuse distribution for your convenience.

Fuse Component	Version	JBoss Container	Version
Camel	2.17.0.redhat-630262	JWS	3.0

Supported BPM Suite and BRMS Integrations

A JBoss Fuse subscription includes a limited entitlement to use BPM Suite and BRMS in embedded form in SwitchYard (in the SwitchYard BPM component and in the SwitchYard Rules component). All other uses require a separate BPM Suite or BRMS subscription.

Note: Fuse Service Works (FSW) subscriptions included an entitlement for use of embedded rules (BRMS) and BPM when used with SwitchYard. When JBoss Fuse and FSW merged, the entitlement was carried forward, but only for use with SwitchYard. All other uses (for example, from Camel) require a separate BPM Suite or BRMS subscription.

JBoss Fuse 6.3 Supported Browsers for use with the Hawt.io console

Browser
Windows Edge
Microsoft IE
Chrome
Firefox

JBoss Fuse 6.3 Platform Restrictions for SAP Tooling

The SAP tooling and the Camel SAP component in JBoss Fuse depend on the JCo 3.0.11 library from SAP (licenced separately), which is subject to additional platform restrictions. In particular, note that the following configurations are NOT supported by the JCo library:

Operating System	Java Version	Supported?
Red Hat Enterprise Linux 5 (deprecated)	Java 8	No
Red Hat Enterprise Linux 7	Java 7	No
Oracle Solaris 10 [4]	Java 7 or 8	No
IBM AIX 7.1	Java 8	No

This is not an exhaustive list. For more details of the JCo 3.0 library's supported configurations, please contact SAP support.

Red Hat JBoss Fuse 6.2

JBoss Fuse 6.2 and 6.2.1 Supported Configurations

Red Hat provides both production and development support for supported configurations according to your subscription agreement in both physical and virtual environments.[1] In order to be running in a supported configuration, JBoss Fuse must be running in one of the following JVM versions and on one of the operating systems supported by that JVM.

Java Virtual Machine	Version
OpenJDK [2]	1.7 1.8
Oracle JDK	1.7 1.8
IBM JDK	1.7 1.8
HP JVM	1.7

Note: JBoss Fuse 6.2 and JBoss Fuse 6.2.1 include an entitlement to JBoss A-MQ, and JBoss Fuse 6.2.1 includes an entitlement to JBoss Enterprise Application Platform. JBoss Fuse 6.2 and JBoss Fuse 6.2.1 have been certified to work with JBoss A-MQ 6.2, and JBoss Fuse 6.2.1 has been certified to work with JBoss EAP 6.4.

JBoss Fuse 6.2 and 6.2.1 Tested Configurations

Red Hat has performed the full range of platform tests on the following tested configurations:

Operating System	Chipset Architecture	Java Virtual Machine
Red Hat Enterprise Linux 7 (latest update) [3]	x86_64	Oracle JDK 1.7.x Oracle JDK 1.8.x IBM JDK 1.7.x IBM JDK 1.8.x OpenJDK 1.7.x OpenJDK 1.8.x
Red Hat Enterprise Linux 6 (latest update) [3]	x86	Oracle JDK 1.7.x Oracle JDK 1.8.x OpenJDK 1.7.x OpenJDK 1.8.x
Red Hat Enterprise Linux 6 (latest update) [3]	x86_64	Oracle JDK 1.7.x Oracle JDK 1.8.x IBM JDK 1.7.x IBM JDK 1.8.x OpenJDK 1.7.x OpenJDK 1.8.x
Red Hat Enterprise Linux 5 (latest update) [3] (deprecated)	x86 x86_64	Oracle JDK 1.7.x Oracle JDK 1.8.x OpenJDK 1.7.x
Microsoft Windows Server 2012 R2	x86_64	Oracle JDK 1.7.x Oracle JDK 1.8.x
Oracle Solaris 10 [4]	x86 x86_64 SPARC64	Oracle JDK 1.7.x Oracle JDK 1.8.x
Oracle Solaris 11 [4]	x86 x86_64 SPARC64	Oracle JDK 1.7.x Oracle JDK 1.8.x
IBM AIX 7.1	Power ISA v.2.06	IBM JDK 1.7.x IBM JDK 1.8.x
HP-UX 11i	IA64	HP JVM 1.7.x

JBoss Fuse 6.2 and 6.2.1 Tested Integrations

Tested Integrations are a defined set of specifically tested integrating technologies that represent the most common combinations that JBoss Enterprise Middleware customers are using. For these integrations, Red Hat has directly, or through certified partners, exercised our full range of platform tests as part of the product release process. Issues identified as part of this testing process are highlighted in release notes for each JBoss Fuse release. This list of tested integrations will expand over time.

The following databases and database drivers were tested as part of the latest JBoss Fuse 6 release.

Databases	JDBC Driver
Oracle 12c	Oracle JDBC Driver v12
Oracle RAC	Oracle JDBC Driver v12
MySQL 5.6	MySQL Connector/J 5
Microsoft SQL Server 2008	MS SQL Server JDBC Driver 3
Microsoft SQL Server 2012	MS SQL Server JDBC Driver 4
PostgreSQL 9.3.5	JDBC 4 Postgresql Driver, Version 9
IBM DB2 9.7	IBM DB2 JDBC Universal Driver Architecture 4.9.78

JBoss Fuse 6.2 and 6.2.1 Supported Browsers for use with the Hawt.io console

Browser	Version
Microsoft IE	10, 11
Chrome	36
Firefox	31

JBoss Fuse 6.2 and 6.2.1 Platform Restrictions for SAP Tooling

Operating System	Java Version	Supported?
Red Hat Enterprise Linux 5 (deprecated)	Java 8	No
Red Hat Enterprise Linux 7	Java 7	No
Oracle Solaris 10 [4]	Java 7 or 8	No
IBM AIX 7.1	Java 8	No

This is not an exhaustive list. For more details of the JCo 3.0 library's supported configurations, please contact SAP support.

JBoss Fuse 6.2 and 6.2.1 Application Container Interoperability

Certain components of the JBoss Fuse distribution are supported on other JBoss containers when deployed in a WAR file as a dependency to your application. Components that are supported on other containers are provided in the /extras directory of the JBoss Fuse distribution for your convenience.

Fuse Component	Version	JBoss Container	Version
Camel	2.15.1.redhat-620117	EAP	6.4
Camel	2.15.1.redhat-620117	JWS	3.0

Red Hat JBoss Fuse 6.1

JBoss Fuse 6.1 Supported Configurations

Java Virtual Machine	Version
OpenJDK [2]	1.7 1.6 (deprecated)
Oracle JDK	1.7 1.6 (deprecated)
IBM JDK	1.7 1.6 (deprecated)

Note: JBoss Fuse 6.1 includes an entitlement to JBoss A-MQ. JBoss Fuse 6.1 has been certified to work with JBoss A-MQ 6.1.

JBoss Fuse 6.1 Tested Configurations

Red Hat has performed the full range of platform tests on the following tested configurations:

Operating System	Chipset Architecture	Java Virtual Machine
Red Hat Enterprise Linux 6 (latest update) [3]	x86 x86_64	Oracle JDK 1.7.x Oracle JDK 1.6.x (deprecated) IBM JDK 1.7.x IBM JDK 1.6.x (deprecated) OpenJDK 1.7.x OpenJDK 1.6.x (deprecated)
Red Hat Enterprise Linux 5 (latest update) [3] (deprecated)	x86 x86_64	Oracle JDK 1.7.x Oracle JDK 1.6.x (deprecated) IBM JDK 1.7.x IBM JDK 1.6.x (deprecated) OpenJDK 1.7.x OpenJDK 1.6.x (deprecated)
Microsoft Windows 2008 Server R2 (deprecated)	x86_64	Oracle JDK 1.7.x Oracle JDK 1.6.x (deprecated)
Oracle Solaris 10 [4]	x86 x86_64 SPARC64	Oracle JDK 1.7.x Oracle JDK 1.6.x (deprecated)
Oracle Solaris 11 [4]	x86 x86_64 SPARC64	Oracle JDK 1.7.x Oracle JDK 1.6.x (deprecated)
IBM AIX 7.1	Power ISA v.2.06	IBM JDK 1.7.x IBM JDK 1.6.x (deprecated)

JBoss Fuse 6.1 Tested Integrations

Tested Integrations are a defined set of specifically tested integrating technologies that represent the most common combinations that JBoss Enterprise Middleware customers are using. For these integrations, Red Hat has directly, or through certified partners, exercised our full range of platform tests as part of the product release process. Issues identified as part of this testing process are highlighted in release notes for each JBoss Fuse release. This list of tested integrations will expand over time.

The following databases and database drivers were tested as part of the latest JBoss Fuse 6 release.

Databases	JDBC Driver
Oracle 11g	Oracle JDBC Driver v11
MySQL 5.1	MySQL Connector/J 5
MySQL 5.5	MySQL Connector/J 5
Microsoft SQL Server 2008	Microsoft SQL Server JDBC Driver 3
PostgreSQL 8.4	JDBC4 Postgresql Driver, Version 8
PostgreSQL 9.1	JDBC4 Postgresql Driver, Version 9

JBoss Fuse 6.1 Supported Browsers for use with the hawit.io console

Browser	Version
Microsoft IE	10, 11
Chrome	31
Firefox	27

JBoss Fuse 6.1 Container Interoperability

Certain components of the JBoss Fuse distribution are supported on other JBoss containers when deployed in a WAR file as a dependency to your application. Components that are supported on other containers are provided in the "/extras" directory of the JBoss Fuse distribution for your convenience.
Note: For these configurations to be supported a subscription to JBoss Fuse and a supported container is required.

Fuse Component	Version	JBoss Container	Version
Camel	2.12.0.redhat-610379	EAP	6.2
Camel	2.12.0.redhat-610379	JWS	2.0.1

Red Hat JBoss Fuse 6.0

JBoss Fuse 6.0 Supported Configurations

Java Virtual Machine	Version
OpenJDK [2]	1.7 1.6 (deprecated)
Oracle JDK	1.7 1.6 (deprecated)
IBM JDK	1.7 1.6 (deprecated)

Note: JBoss Fuse 6.0 includes an entitlement to JBoss A-MQ. JBoss Fuse 6.0 has been certified to work with JBoss A-MQ 6.0.

JBoss Fuse 6.0 Tested Configurations

Red Hat has performed the full range of platform tests on the following tested configurations:

Operating System	Chipset Architecture	Java Virtual Machine
Red Hat Enterprise Linux 6 (latest update) [3]	x86 x86_64	Oracle JDK 1.7.x Oracle JDK 1.6.x (deprecated) IBM JDK 1.7.x IBM JDK 1.6.x (deprecated) OpenJDK 1.7.x OpenJDK 1.6.x (deprecated)
Red Hat Enterprise Linux 5 (latest update) [3] (deprecated)	x86 x86_64	Oracle JDK 1.7.x Oracle JDK 1.6.x (deprecated) IBM JDK 1.7.x IBM JDK 1.6.x (deprecated) OpenJDK 1.7.x OpenJDK 1.6.x (deprecated)
Microsoft Windows 2008 Server R2 (deprecated)	x86_64	Oracle JDK 1.7.x Oracle JDK 1.6.x (deprecated)
Oracle Solaris 10 [4]	SPARC64	Oracle JDK 1.7.x Oracle JDK 1.6.x (deprecated)
IBM AIX 7.1	Power ISA v.2.06	IBM JDK 1.7.x IBM JDK 1.6.x (deprecated)

JBoss Fuse 6.0 Container Interoperability

Certain components of the JBoss Fuse distribution are supported on other JBoss containers when deployed in a WAR file as a dependency to your application. Components that are supported on other containers are provided in the "/extras" directory of the JBoss Fuse distribution for your convenience. Note: For these configurations to be supported a subscription to JBoss Fuse and a supported container is required.

Fuse Component	Version	JBoss Container	Version
Camel	2.10.0.redhat-60024	EAP	6.1.1
Camel	2.10.0.redhat-60024	JWS	2.0.1

[1] Red Hat 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, Red Hat may be limited in its ability to provide support and may require you to reproduce the issue in a supported environment for continued assistance.

[2] Red Hat limits support of OpenJDK to Red Hat Enterprise Linux.

[3] For each supported major version of Red Hat Enterprise Linux (5, 6, or 7), JBoss Fuse is tested against the corresponding latest minor version (5.x, 6.x, or 7.x) available at the time of the JBoss Fuse GA release. In addition, subsequent minor versions of Red Hat Enterprise Linux (released after JBoss Fuse GA) are also supported.

[4] Solaris Zones are not considered a supported environment, only physical Solaris systems are supported.