Red Hat Fuse Supported Configurations
For more information about supported configurations, see Supported Standards and Component Details.
Every Red Hat Fuse release is tested and supported on various market-leading operating systems, Java™ Virtual Machines (JVMs), and database combinations. Red Hat provides production and development support for supported configurations and tested integrations according to your subscription agreement in physical and virtual environments.
- Red Hat Fuse 7.13
- Red Hat Fuse 7.12
- Red Hat Fuse 7.11
- Red Hat Fuse 7.10
- Red Hat Fuse 7.9
- Red Hat Fuse 7.8
- Red Hat Fuse 7.7
- Red Hat Fuse 7.6
- Red Hat Fuse 7.5
- Red Hat Fuse 7.4
- Red Hat Fuse 7.3
- Red Hat Fuse 7.2
- Red Hat Fuse 7.1
- Red Hat Fuse 7.0
- Red Hat JBoss Fuse 6.3
- Red Hat JBoss Fuse 6.2
- Red Hat JBoss Fuse 6.1
- Red Hat JBoss Fuse 6.0
Red Hat Fuse 7.13
Red Hat Fuse 7.13 includes an entitlement to Red Hat AMQ, and an entitlement to JBoss Enterprise Application Platform (possibly, more than one version of each). See the tables below for supported versions of AMQ and JBoss EAP.
Red Hat Fuse 7.13 on OpenShift
You must run Fuse on OpenShift on a supported version of OpenShift. The following OpenShift versions were tested against Red Hat Fuse 7.13 on OpenShift at the time of the relevant OpenShift release:
OpenShift Product | Version | Chipset Architecture | Note |
---|---|---|---|
OpenShift Container Platform (OCP) | 4.12, 4.13, 4.14, 4.15, 4.16 | x86_64 s390x ppc64le |
Before upgrading OpenShift to version 4.10 or newer, you must upgrade Fuse to at least version 7.10. |
OpenShift Kubernetes Engine (OKE) | 4.12, 4.13, 4.14, 4.15 | x86_64 s390x ppc64le |
Before upgrading OpenShift to version 4.10 or newer, you must upgrade Fuse to at least version 7.10. |
NOTE: In Fuse 7.13, installing the Fuse on OpenShift image streams and templates on IBM Power Systems or IBM Z, it is not supported
Fuse is supported on Red Hat OpenShift Service on AWS (ROSA) on the same versions of OpenShift as Fuse on the x86_64 architecture
Red Hat Fuse 7.13 without OpenShift on a Cloud Platform
If you deploy Fuse without OpenShift directly on any cloud platform — for example, MS Azure or Amazon Web Services (AWS) — Red Hat support extends to the Fuse components, but not to the underlying cloud platform. Red Hat does not provide any documentation on installing and configuring Fuse without OpenShift on cloud platforms. Consult your cloud provider's documentation to learn how to configure your application deployments in the cloud.
For more information, see Support Guidelines for Red Hat Middleware Products Deployed in 3rd-party Environments.
Red Hat Fuse 7.13 Supported Java Runtimes
For the configuration to be supported you must run Red Hat Fuse 7.12 in one of the following Java runtimes and on one of the operating systems supported by that runtime:
Java Virtual Machine | Version |
---|---|
OpenJDK | 1.8, 11, 17 |
OpenJDK (FIPS Enabled) | 1.8, 11, 17 |
Oracle JDK | 1.8, 11 |
IBM JDK | 1.8, 11, 17 |
HP JVM | 1.8 |
Adoptium JDK | 1.8, 11, 17 |
NOTE: Red Hat limits support of OpenJDK to the Red Hat builds of OpenJDK for Red Hat Enterprise Linux (RHEL) and Windows.
NOTE: Red Hat limits support of Adoptium JDK to Red Hat Enterprise Linux (RHEL) and Windows
NOTE: Fuse 7 supports running on a FIPS enabled JDK but is neither FIPS compliant nor certified as per KCS article
Red Hat Fuse 7.13 Supported Container Types
For Fuse 7.13, the following container types and versions are supported:
Container Type | Version | Chipset Architecture |
---|---|---|
Spring Boot 2 | 2.7.18 | x86_64 s390x ppc64le |
JBoss Enterprise Application Platform | 7.4.16 (and later 7.4.x micro versions) | x86_64 |
Apache Karaf | 4.4.3.fuse | x86_64 |
NOTE: For Fuse on JBoss EAP deployments, operating system support aligns with Red Hat JBoss EAP 7 Supported Configurations.
Spring Boot 2 Support
Red Hat Fuse 7.13 on OpenShift relies on the Spring Boot Community version. Red Hat's support for Spring Boot 2 is limited to its intended use. Red Hat offers a commercially reasonable effort to support Spring Boot 2, but we may not be able to provide or influence timely patches.
In addition to deployment of Spring Boot 2 on OpenShift, deployment of Spring Boot 2 in standalone mode (Jar file running on a supported JVM) is also supported by Red Hat, provided your application uses the dependencies from the Spring Boot 2 BOM (Apache Maven Bill of Materials) file.
For more details, see Spring Boot Support.
Red Hat Fuse 7.13 Supported Configurations
Red Hat has performed the full range of platform tests on the following tested configurations:
Chipset Architecture | Operating System | Java Runtime Environment |
---|---|---|
x86_64 | Red Hat Enterprise Linux 9 (latest update) | Oracle JDK 1.8.x †, 11.0.x IBM JDK 1.8.x Red Hat build of OpenJDK 1.8 †, 11.0.x, 17.0.x |
x86_64 | Red Hat Enterprise Linux 8 (latest update) | Oracle JDK 1.8.x †, 11.0.x IBM JDK 1.8.x Red Hat build of OpenJDK 1.8 †, 11.0.x, 17.0.x |
x86_64 | Red Hat Enterprise Linux 7 (latest update) | Oracle JDK 1.8.x †, 11.0.x IBM JDK 1.8.x Red Hat build of OpenJDK 1.8 †, 11.0.x, 17.0.x |
x86_64 | Microsoft Windows Server 2019 | Oracle JDK 1.8.x †, OpenJDK 1.8, 11. † |
s390x | Red Hat Enterprise Linux 8 (latest update) | Red Hat build of OpenJDK 11.0.x, 17.0.x |
ppc64le | Red Hat Enterprise Linux 8 (latest update) | Red Hat build of OpenJDK 11.0.x, 17.0.x |
† IMPORTANT: Both OpenJDK 8u292 and OracleJDK 1.8.0_291 suffer from a known issue in the security API, which affects the credentials store in Apache Karaf. We recommend that you avoid these JDK versions. For OpenJDK, you could use either OpenJDK 8u282 or OpenJDK 8u302, which are not affected by this issue.
The following configurations are supported, but not fully tested:
Chipset Architecture | Operating System | Java Virtual Machine |
---|---|---|
SPARC64 | Oracle Solaris 11 **NOTE:** (partial legacy testing, not recommended for new deployments) | Oracle JDK 1.8.x |
Power ISA | IBM AIX 7.2 (partial legacy testing, not recommended for new deployments) | IBM JDK 1.8.x |
IA64 | HP-UX 11i (Deprecated) (Not supported on JBoss EAP since version 7.2) | HP JVM 1.8.x |
NOTE: For Fuse on JBoss EAP deployments, operating system support aligns with Red Hat JBoss EAP 7 Supported Configurations.
Red Hat Fuse 7.13 Tested Integrations
NOTE: The integrations described in this section were tested only for systems based on x86_64 architectures and do not apply to IBM Power Systems (ppc64le) or IBM Z (s390x) unless explicitly stated.
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.
Red Hat Fuse 7.13 Supported Database Integrations
The following databases and database drivers were tested as part of the latest Red Hat Fuse 7 release. They were also tested on IBM Power Systems (ppc64le).
Databases | JDBC Driver |
---|---|
Oracle 18c r3 RAC | Oracle JDBC Driver v21 |
Oracle 19c r3 RAC | Oracle JDBC Driver v21 |
MySQL 5.7 | MySQL Connector J5 |
MySQL 8.0 | MySQL Connector J8 |
Microsoft SQL Server 2017 | MS SQL Server JDBC Driver 10.2 |
Microsoft SQL Server 2019* | MS SQL Server JDBC Driver 10.2 |
PostgreSQL 12.5 | JDBC Postgresql Driver, Version 42.5.2 |
PostgreSQL 13.2 | JDBC Postgresql Driver, Version 42.5.2 |
IBM DB2 10.5* | IBM DB2 JDBC Universal Driver Architecture 4.31 |
IBM DB2 11.1 | IBM DB2 JDBC Universal Driver Architecture 4.31 |
NOTE IBM DB2 10.5 is not supported on JBoss EAP.
NOTE Red Hat tests database integrations using the JDBC driver versions shown above. These drivers are compatible with a range of database server versions. See your database vendor’s documentation for information about JDBC driver compatibility with specific server versions.
Red Hat Fuse 7.13 Supported Messaging Providers
Since Fuse 7.0, only remote brokers are supported.
Broker | Version | Target Containers |
---|---|---|
JBoss A-MQ | 6.3 latest | Apache Karaf Spring Boot JBoss EAP |
AMQ Broker | 7.8.7 7.11 7.12 |
Apache Karaf Spring Boot JBoss EAP |
AMQ Streams | 2.1.0 2.2.0 |
Apache Karaf Spring Boot JBoss EAP |
Websphere MQ1 | 8.0 | Apache Karaf Spring Boot JBoss EAP |
9.1 | Apache Karaf Spring Boot JBoss EAP |
NOTE: 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.
Red Hat Fuse 7.13 Supported Messaging Clients
The following messaging clients and JCA adapters have been tested for Red Hat Fuse 7.13.
Messaging Components for Apache Karaf
The following messaging components are tested on Apache Karaf:
Apache Karaf | |||
---|---|---|---|
Broker | Version | Client | Camel components |
JBoss A-MQ | 6.3 | activemq-client
|
camel-activemq |
AMQ Broker | 7.8.7 7.11 7.12 |
artemis-jms-client |
camel-jms camel-sjms camel-sjms2 |
qpid-jms-client |
camel-amqp |
||
IBM MQ | 8.0 | Client v8 | camel-jms |
9.1 | Client v9 | JMS API from Java code |
Messaging Components for JBoss EAP
Messaging on the JBoss EAP container is supported using JCA adapters, see JBoss EAP 7.4 Supported Configurations. The following messaging components are tested on JBoss EAP 7.4:
JBoss EAP | |||
---|---|---|---|
Broker | Version | Adapter | Camel components |
JBoss A-MQ | 6.3 | AMQ JCA Adapter v5.11.0 |
camel-jms camel-activemq |
AMQ Broker | 7.8.7 7.11 7.12 |
AMQ JCA Adapter which is integrated in JBoss EAP 7.4 | camel-jms camel-sjms |
IBM MQ | 8.0 | Client v8 | camel-jms |
9.1 | Client v9 | JMS API from Java code |
Messaging Components for Spring Boot
The following messaging components are tested on Spring Boot 2.7:
Spring Boot 2.7 | |||
---|---|---|---|
Broker | Version | Client | Camel components |
JBoss A-MQ | 6.3 | activemq-client |
camel-jms |
AMQ Broker | 7.8.7 7.11 7.12 |
artemis-jms-client |
camel-jms camel-sjms camel-sjms2 |
qpid-jms-client |
camel-jms camel-amqp |
||
IBM MQ | 8.0 | Client v8 | camel-jms |
9.1 | Client v9.1.0.6 | 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.12 (Apache Karaf, and JBoss EAP, respectively).
Red Hat Fuse 7.13 Supported Security Providers
Red Hat Fuse 7 is tested against Red Hat Single Sign-On (RH SSO). The following RH SSO versions are supported with Fuse 7.13:
Security Provider | Version | Target Containers |
---|---|---|
RH SSO | 7.6.2 GA |
Apache Karaf JBoss EAP (only integration with Hawtio) Spring Boot 2 (only integration with Hawtio) |
Red Hat Fuse 7.13 LDAP Providers
The following LDAP providers are supported with Fuse 7.13:
Server | Version |
---|---|
Apache Directory | 2.0.0-M24 |
OpenLDAP | 2.4.44 |
Red Hat Directory Server | 10.6 |
Windows Active Directory | 69 (Windows Server 2012 R2) |
Red Hat Fuse 7.13 Supported Data Grid
Client
Camel component | RH-JDG Version | Target Container |
---|---|---|
camel-infinispan | 9.4.19.Final-redhat-00001 | Apache Karaf Spring Boot 2 |
11.0.18.Final-redhat-00001 | JBoss EAP |
Server
Server | RH-JDG Version | Target Container |
---|---|---|
redhat-datagrid | 8.x | Apache Karaf JBoss EAP Spring Boot 2 |
Red Hat Fuse 7.13 Supported SAP Client Integrations
Red Hat's Apache Camel SAP component works with the following JCo client and IDoc client libraries:
Component | SAP Client | Version |
---|---|---|
Camel SAP | JCo | 3.1.4 |
Camel SAP | IDoc | 3.1.1 |
Red Hat Fuse 7.13 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.13 release.
Browser |
---|
Mozilla Firefox |
Google Chrome |
Microsoft Edge |
Red Hat Fuse 7.12
Red Hat Fuse 7.12 includes an entitlement to Red Hat AMQ, and an entitlement to JBoss Enterprise Application Platform (possibly, more than one version of each). See the tables below for supported versions of AMQ and JBoss EAP.
Red Hat Fuse 7.12 on OpenShift
You must run Fuse on OpenShift on a supported version of OpenShift. The following OpenShift versions were tested against Red Hat Fuse 7.12 on OpenShift at the time of the relevant OpenShift release:
OpenShift Product | Version | Chipset Architecture | Note |
---|---|---|---|
OpenShift Container Platform (OCP) | 4.10, 4.11, 4.12, 4.13 | x86_64 s390x ppc64le |
Before upgrading OpenShift to version 4.10 or newer, you must upgrade Fuse to at least version 7.10. |
OpenShift Kubernetes Engine (OKE) | 4.10, 4.11, 4.12, 4.13 | x86_64 s390x ppc64le |
Before upgrading OpenShift to version 4.10 or newer, you must upgrade Fuse to at least version 7.10. |
NOTE: In Fuse 7.12, installing the Fuse on OpenShift imagestreams and templates on IBM Power Systems or IBM Z, it is not supported
Fuse is supported on Red Hat OpenShift Service on AWS (ROSA) on the same versions of OpenShift as Fuse on the x86_64 architecture
Red Hat Fuse 7.12 without OpenShift on a Cloud Platform
If you deploy Fuse without OpenShift directly on any cloud platform — for example, MS Azure or Amazon Web Services (AWS) — Red Hat support extends to the Fuse components, but not to the underlying cloud platform. Red Hat does not provide any documentation on installing and configuring Fuse without OpenShift on cloud platforms. Consult your cloud provider's documentation to learn how to configure your application deployments in the cloud.
For more information, see Support Guidelines for Red Hat Middleware Products Deployed in 3rd-party Environments.
Red Hat Fuse 7.12 Supported Java Runtimes
For the configuration to be supported you must run Red Hat Fuse 7.12 in one of the following Java runtimes and on one of the operating systems supported by that runtime:
Java Virtual Machine | Version |
---|---|
OpenJDK | 1.8, 11, 17 |
OpenJDK (FIPS Enabled) | 1.8, 11, 17 |
Oracle JDK | 1.8, 11 |
IBM JDK | 1.8, 11, 17 |
HP JVM | 1.8 |
Adoptium JDK | 1.8, 11, 17 |
NOTE: Red Hat limits support of OpenJDK to the Red Hat builds of OpenJDK for Red Hat Enterprise Linux (RHEL) and Windows.
NOTE: Red Hat limits support of Adoptium JDK to Red Hat Enterprise Linux (RHEL) and Windows
NOTE: Fuse 7 supports running on a FIPS enabled JDK but is neither FIPS compliant nor certified as per KCS article
Red Hat Fuse 7.12 Supported Container Types
For Fuse 7.12, the following container types and versions are supported:
Container Type | Version | Chipset Architecture |
---|---|---|
Spring Boot 2 | 2.7.12 | x86_64 s390x ppc64le |
JBoss Enterprise Application Platform | 7.4.10 (and later 7.4.x micro versions) | x86_64 |
Apache Karaf | 4.4.3.fuse | x86_64 |
NOTE: For Fuse on JBoss EAP deployments, operating system support aligns with Red Hat JBoss EAP 7 Supported Configurations.
Spring Boot 2 Support
Red Hat Fuse 7.12 on OpenShift relies on the Spring Boot Community version and. Red Hat's support for Spring Boot 2 is limited to its intended use. Red Hat offers a commercially reasonable effort to support Spring Boot 2, but we may not be able to provide or influence timely patches.
In addition to deployment of Spring Boot 2 on OpenShift, deployment of Spring Boot 2 in standalone mode (Jar file running on a supported JVM) is also supported by Red Hat, provided your application uses the dependencies from the Spring Boot 2 BOM (Apache Maven Bill of Materials) file.
For more details, see Spring Boot Support.
Red Hat Fuse 7.12 Supported Configurations
Red Hat has performed the full range of platform tests on the following tested configurations:
Chipset Architecture | Operating System | Java Runtime Environment |
---|---|---|
x86_64 | Red Hat Enterprise Linux 9 (latest update) | Oracle JDK 1.8.x †, 11.0.x IBM JDK 1.8.x Red Hat build of OpenJDK 1.8 †, 11.0.x, 17.0.x |
x86_64 | Red Hat Enterprise Linux 8 (latest update) | Oracle JDK 1.8.x †, 11.0.x IBM JDK 1.8.x Red Hat build of OpenJDK 1.8 †, 11.0.x, 17.0.x |
x86_64 | Red Hat Enterprise Linux 7 (latest update) | Oracle JDK 1.8.x †, 11.0.x IBM JDK 1.8.x Red Hat build of OpenJDK 1.8 †, 11.0.x, 17.0.x |
x86_64 | Microsoft Windows Server 2019 | Oracle JDK 1.8.x †, OpenJDK 1.8, 11. † |
s390x | Red Hat Enterprise Linux 8 (latest update) | Red Hat build of OpenJDK 11.0.x, 17.0.x |
ppc64le | Red Hat Enterprise Linux 8 (latest update) | Red Hat build of OpenJDK 11.0.x, 17.0.x |
† IMPORTANT: Both OpenJDK 8u292 and OracleJDK 1.8.0_291 suffer from a known issue in the security API, which affects the credentials store in Apache Karaf. We recommend that you avoid these JDK versions. For OpenJDK, you could use either OpenJDK 8u282 or OpenJDK 8u302, which are not affected by this issue.
The following configurations are supported, but not fully tested:
Chipset Architecture | Operating System | Java Virtual Machine |
---|---|---|
SPARC64 | Oracle Solaris 11 **NOTE:** (partial legacy testing, not recommended for new deployments) | Oracle JDK 1.8.x |
Power ISA | IBM AIX 7.2 (partial legacy testing, not recommended for new deployments) | IBM JDK 1.8.x |
IA64 | HP-UX 11i (Deprecated) (Not supported on JBoss EAP since version 7.2) | HP JVM 1.8.x |
NOTE: For Fuse on JBoss EAP deployments, operating system support aligns with Red Hat JBoss EAP 7 Supported Configurations.
Red Hat Fuse 7.12 Tested Integrations
NOTE: The integrations described in this section were tested only for systems based on x86_64 architectures and do not apply to IBM Power Systems (ppc64le) or IBM Z (s390x) unless explicitly stated.
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.
Red Hat Fuse 7.12 Supported Database Integrations
The following databases and database drivers were tested as part of the latest Red Hat Fuse 7 release. They were also tested on IBM Power Systems (ppc64le).
Databases | JDBC Driver |
---|---|
Oracle 12c r2 RAC | Oracle JDBC Driver v21 |
Oracle 18c r3 RAC | Oracle JDBC Driver v21 |
Oracle 19c r3 RAC | Oracle JDBC Driver v21 |
MySQL 5.7 | MySQL Connector J5 |
MySQL 8.0 | MySQL Connector J8 |
Microsoft SQL Server 2017 | MS SQL Server JDBC Driver 9.2 |
Microsoft SQL Server 2019* | MS SQL Server JDBC Driver 9.2 |
PostgreSQL 12.5 | JDBC Postgresql Driver, Version 42.5.2 |
PostgreSQL 13.2 | JDBC Postgresql Driver, Version 42.5.2 |
IBM DB2 10.5* | IBM DB2 JDBC Universal Driver Architecture 4.31 |
IBM DB2 11.1 | IBM DB2 JDBC Universal Driver Architecture 4.31 |
NOTE IBM DB2 10.5 is not supported on JBoss EAP.
NOTE Red Hat tests database integrations using the JDBC driver versions shown above. These drivers are compatible with a range of database server versions. See your database vendor’s documentation for information about JDBC driver compatibility with specific server versions.
Red Hat Fuse 7.12 Supported Messaging Providers
Since Fuse 7.0, only remote brokers are supported.
Broker | Version | Target Containers |
---|---|---|
JBoss A-MQ | 6.3 latest | Apache Karaf Spring Boot 2.5 JBoss EAP |
AMQ Broker | 7.8.7 7.10.x |
Apache Karaf Spring Boot 2.5 JBoss EAP |
AMQ Streams | 2.1.0 2.2.0 |
Apache Karaf Spring Boot 2.5 JBoss EAP Fuse Online |
Websphere MQ1 | 8.0 | Apache Karaf Spring Boot 2.5 JBoss EAP |
9.1 | Apache Karaf Spring Boot 2.5 JBoss EAP |
NOTE: 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.
Red Hat Fuse 7.12 Supported Messaging Clients
The following messaging clients and JCA adapters have been tested for Red Hat Fuse 7.12.
Messaging Components for Apache Karaf
The following messaging components are tested on Apache Karaf:
Apache Karaf | |||
---|---|---|---|
Broker | Version | Client | Camel components |
JBoss A-MQ | 6.3 | activemq-client
|
camel-activemq |
AMQ Broker | 7.8.7 | artemis-jms-client |
camel-jms camel-sjms camel-sjms2 |
qpid-jms-client |
camel-amqp |
||
IBM MQ | 8.0 | Client v8 | camel-jms |
9.1 | Client v9 | JMS API from Java code |
Messaging Components for JBoss EAP
Messaging on the JBoss EAP container is supported using JCA adapters, see JBoss EAP 7.4 Supported Configurations. The following messaging components are tested on JBoss EAP 7.4:
JBoss EAP | |||
---|---|---|---|
Broker | Version | Adapter | Camel components |
JBoss A-MQ | 6.3 | AMQ JCA Adapter v5.11.0 |
camel-jms camel-activemq |
AMQ Broker | 7.10.x | AMQ JCA Adapter which is integrated in JBoss EAP 7.4 | camel-jms camel-sjms |
IBM MQ | 8.0 | Client v8 | camel-jms |
9.1 | Client v9 | JMS API from Java code |
Messaging Components for Spring Boot
The following messaging components are tested on Spring Boot 2.5:
Spring Boot 2.5 | |||
---|---|---|---|
Broker | Version | Client | Camel components |
JBoss A-MQ | 6.3 | activemq-client |
camel-jms |
AMQ Broker | 7.10.x | artemis-jms-client |
camel-jms camel-sjms camel-sjms2 |
qpid-jms-client |
camel-jms camel-amqp |
||
IBM MQ | 8.0 | Client v8 | camel-jms |
9.1 | Client v9.1.0.6 | 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.12 (Apache Karaf, and JBoss EAP, respectively).
Red Hat Fuse 7.12 Supported Security Providers
Red Hat Fuse 7 is tested against Red Hat Single Sign-On (RH SSO). The following RH SSO versions are supported with Fuse 7.12:
Security Provider | Version | Target Containers |
---|---|---|
RH SSO | 7.6.2 GA |
Apache Karaf JBoss EAP (only integration with Hawtio) Spring Boot 2 (only integration with Hawtio) |
Red Hat Fuse 7.12 LDAP Providers
The following LDAP providers are supported with Fuse 7.12:
Server | Version |
---|---|
Apache Directory | 2.0.0-M24 |
OpenLDAP | 2.4.57 |
Red Hat Directory Server | 10.6 |
Windows Active Directory | 69 (Windows Server 2012 R2) |
Red Hat Fuse 7.12 Supported Data Grid
Client
Camel component | RH-JDG Version | Target Container |
---|---|---|
camel-infinispan | 9.4.19.Final-redhat-00001 | Apache Karaf Spring Boot 2 |
11.0.17.Final-redhat-00001 | JBoss EAP |
Server
Server | RH-JDG Version | Target Container |
---|---|---|
redhat-datagrid | 8.x | Apache Karaf JBoss EAP Spring Boot 2 |
Red Hat Fuse 7.12 Supported SAP Client Integrations
Red Hat's Apache Camel SAP component works with the following JCo client and IDoc client libraries:
Component | SAP Client | Version |
---|---|---|
Camel SAP | JCo | 3.1.4 |
Camel SAP | IDoc | 3.1.1 |
Red Hat Fuse 7.12 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.12 release.
Browser |
---|
Mozilla Firefox |
Google Chrome |
Microsoft Edge |
Red Hat Fuse 7.11
Red Hat Fuse 7.11 includes an entitlement to Red Hat AMQ, and an entitlement to JBoss Enterprise Application Platform (possibly, more than one version of each). See the tables below for supported versions of AMQ and JBoss EAP.
Red Hat Fuse 7.11 on OpenShift
You must run Fuse on OpenShift on a supported version of OpenShift. The following OpenShift versions were tested against Red Hat Fuse 7.11 on OpenShift at the time of the relevant OpenShift release:
OpenShift Product | Version | Chipset Architecture | Note |
---|---|---|---|
OpenShift Container Platform (OCP) | 4.6, 4.8, 4.9, 4.10, 4.11, 4.12 | x86_64 s390x ppc64le |
Before upgrading OpenShift to version 4.9 or newer, you must upgrade Fuse to at least version 7.10. |
OpenShift Kubernetes Engine (OKE) | 4.6, 4.8, 4.9, 4.10, 4.11 | x86_64 s390x ppc64le |
Before upgrading OpenShift to version 4.9 or newer, you must upgrade Fuse to at least version 7.10. |
NOTE: In Fuse 7.11, installing the Fuse on OpenShift imagestreams and templates on IBM Power Systems or IBM Z, it is not supported
Fuse is supported on Red Hat OpenShift Service on AWS (ROSA) on the same versions of OpenShift as Fuse on the x86_64 architecture
Red Hat Fuse 7.11 without OpenShift on a Cloud Platform
If you deploy Fuse without OpenShift directly on any cloud platform — for example, MS Azure or Amazon Web Services (AWS) — Red Hat support extends to the Fuse components, but not to the underlying cloud platform. Red Hat does not provide any documentation on installing and configuring Fuse without OpenShift on cloud platforms. Consult your cloud provider's documentation to learn how to configure your application deployments in the cloud.
For more information, see Support Guidelines for Red Hat Middleware Products Deployed in 3rd-party Environments.
Red Hat Fuse 7.11 Supported Java Runtimes
For the configuration to be supported you must run Red Hat Fuse 7.11 in one of the following Java runtimes and on one of the operating systems supported by that runtime:
Java Virtual Machine | Version |
---|---|
OpenJDK | 1.8, 11 |
Oracle JDK | 1.8, 11 |
IBM JDK | 1.8 |
HP JVM | 1.8 |
IBM Semeru | 11.0.13.0 |
Adoptium JDK | 1.8, 11 |
NOTE: Red Hat limits support of OpenJDK to the Red Hat builds of OpenJDK for Red Hat Enterprise Linux (RHEL) and Windows.
NOTE: IBM Semeru is currently the only runtime supported on IBM Power Systems (ppc64le), IBM Z, and LinuxONE (390x)
NOTE: Red Hat limits support of Adoptium JDK to Red Hat Enterprise Linux (RHEL) and Windows
Red Hat Fuse 7.11 Supported Container Types
For Fuse 7.11, the following container types and versions are supported:
Container Type | Version | Chipset Architecture |
---|---|---|
Spring Boot 2 | 2.5.13.RELEASE | x86_64 s390x ppc64le |
JBoss Enterprise Application Platform | 7.4.7 (and later 7.4.x micro versions) | x86_64 |
Apache Karaf | 4.2.15.fuse | x86_64 |
NOTE: For Fuse on JBoss EAP deployments, operating system support aligns with Red Hat JBoss EAP 7 Supported Configurations.
Spring Boot 2 Support
Red Hat Fuse 7.11 on OpenShift relies on the Spring Boot Community version and. Red Hat's support for Spring Boot 2 is limited to its intended use. Red Hat offers a commercially reasonable effort to support Spring Boot 2, but we may not be able to provide or influence timely patches.
In addition to deployment of Spring Boot 2 on OpenShift, deployment of Spring Boot 2 in standalone mode (Jar file running on a supported JVM) is also supported by Red Hat, provided your application uses the dependencies from the Spring Boot 2 BOM (Apache Maven Bill of Materials) file.
For more details, see Spring Boot Support.
Red Hat Fuse 7.11 Supported Configurations
Red Hat has performed the full range of platform tests on the following tested configurations:
Chipset Architecture | Operating System | Java Runtime Environment |
---|---|---|
x86_64 | Red Hat Enterprise Linux 8 (latest update) | Oracle JDK 1.8.x †, 11.0.x IBM JDK 1.8.x Red Hat build of OpenJDK 1.8 †, 11.0.x |
x86_64 | Red Hat Enterprise Linux 7 (latest update) | Oracle JDK 1.8.x †, 11.0.x IBM JDK 1.8.x Red Hat build of OpenJDK 1.8 †, 11.0.x |
x86_64 | Microsoft Windows Server 2019 | Oracle JDK 1.8.x †, OpenJDK 1.8 † |
s390x | Red Hat Enterprise Linux 8 (latest update) | IBM Semeru 11.0.13.0 |
ppc64le | Red Hat Enterprise Linux 8 (latest update) | IBM Semeru 11.0.13.0 |
† IMPORTANT: Both OpenJDK 8u292 and OracleJDK 1.8.0_291 suffer from a known issue in the security API, which affects the credentials store in Apache Karaf. We recommend that you avoid these JDK versions. For OpenJDK, you could use either OpenJDK 8u282 or OpenJDK 8u302, which are not affected by this issue.
The following configurations are supported, but not fully tested:
Chipset Architecture | Operating System | Java Virtual Machine |
---|---|---|
SPARC64 | Oracle Solaris 11 NOTE: (partial legacy testing, not recommended for new deployments) | Oracle JDK 1.8.x |
Power ISA | IBM AIX 7.2 (partial legacy testing, not recommended for new deployments) | IBM JDK 1.8.x |
IA64 | HP-UX 11i (Deprecated) (Not supported on JBoss EAP since version 7.2) | HP JVM 1.8.x |
NOTE: For Fuse on JBoss EAP deployments, operating system support aligns with Red Hat JBoss EAP 7 Supported Configurations.
Red Hat Fuse 7.11 Tested Integrations
NOTE: The integrations described in this section were tested only for systems based on x86_64 architectures and do not apply to IBM Power Systems (ppc64le) or IBM Z (s390x) unless explicitly stated.
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.
Red Hat Fuse 7.11 Supported Database Integrations
The following databases and database drivers were tested as part of the latest Red Hat Fuse 7 release. They were also tested on IBM Power Systems (ppc64le).
Databases | JDBC Driver |
---|---|
Oracle 10g r2 | Oracle JDBC Driver v19 |
Oracle 12c r2 RAC | Oracle JDBC Driver v21 |
Oracle 18c r3 RAC | Oracle JDBC Driver v21 |
Oracle 19c r3 RAC | Oracle JDBC Driver v21 |
MySQL 5.7 | MySQL Connector J5 |
MySQL 8.0 | MySQL Connector J8 |
Microsoft SQL Server 2017 | MS SQL Server JDBC Driver 9.2 |
Microsoft SQL Server 2019* | MS SQL Server JDBC Driver 9.2 |
PostgreSQL 12.5 | JDBC Postgresql Driver, Version 42.4.2 |
PostgreSQL 13.2 | JDBC Postgresql Driver, Version 42.4.2 |
IBM DB2 10.5* | IBM DB2 JDBC Universal Driver Architecture 4.31 |
IBM DB2 11.1 | IBM DB2 JDBC Universal Driver Architecture 4.31 |
NOTE IBM DB2 10.5 is not supported on JBoss EAP.
NOTE Red Hat tests database integrations using the JDBC driver versions shown above. These drivers are compatible with a range of database server versions. See your database vendor’s documentation for information about JDBC driver compatibility with specific server versions.
Red Hat Fuse 7.11 Supported Messaging Providers
Since Fuse 7.0, only remote brokers are supported.
Broker | Version | Target Containers |
---|---|---|
JBoss A-MQ | 6.3 | Apache Karaf Spring Boot 2.5 JBoss EAP |
AMQ Broker | 7.8.7 | Apache Karaf Spring Boot 2.5 JBoss EAP |
AMQ Streams | 1.8.0, 2.1.0, 2.2.0 | Apache Karaf Spring Boot 2.5 JBoss EAP Fuse Online |
Websphere MQ1 | 8.0 | Apache Karaf Spring Boot 2.5 JBoss EAP |
9.3 | Apache Karaf Spring Boot 2.5 JBoss EAP |
NOTE: 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.
Red Hat Fuse 7.11 Supported Messaging Clients
The following messaging clients and JCA adapters have been tested for Red Hat Fuse 7.11.
Messaging Components for Apache Karaf
The following messaging components are tested on Apache Karaf:
Apache Karaf | |||
---|---|---|---|
Broker | Version | Client | Camel components |
JBoss A-MQ | 6.3 | activemq-client
|
camel-activemq |
AMQ Broker | 7.8.7 | artemis-jms-client |
camel-jms camel-sjms camel-sjms2 |
qpid-jms-client |
camel-amqp |
||
IBM MQ | 8.0 | Client v8 | camel-jms |
9.3 | Client v9 | JMS API from Java code |
Messaging Components for JBoss EAP
Messaging on the JBoss EAP container is supported using JCA adapters, see JBoss EAP 7.4 Supported Configurations. The following messaging components are tested on JBoss EAP 7.4:
JBoss EAP | |||
---|---|---|---|
Broker | Version | Adapter | Camel components |
JBoss A-MQ | 6.3 | AMQ JCA Adapter v5.11.0 |
camel-jms camel-activemq |
AMQ Broker | 7.8.7 | AMQ JCA Adapter which is integrated in JBoss EAP 7.4 | camel-jms camel-sjms |
IBM MQ | 8.0 | Client v8 | camel-jms |
9.3 | Client v9 | JMS API from Java code |
Messaging Components for Spring Boot
The following messaging components are tested on Spring Boot 2.5:
Spring Boot 2.5 | |||
---|---|---|---|
Broker | Version | Client | Camel components |
JBoss A-MQ | 6.3 | activemq-client |
camel-jms |
AMQ Broker | 7.8.7 | artemis-jms-client |
camel-jms camel-sjms camel-sjms2 |
qpid-jms-client |
camel-jms camel-amqp |
||
IBM MQ | 8.0 | Client v8 | camel-jms |
9.3 | Client v9.1.0.6 | 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.11 (Apache Karaf, and JBoss EAP, respectively).
Red Hat Fuse 7.11 Supported Security Providers
Red Hat Fuse 7 is tested against Red Hat Single Sign-On (RH SSO). The following RH SSO versions are supported with Fuse 7.11:
Security Provider | Version | Target Containers |
---|---|---|
RH SSO | 7.6.0.GA |
Apache Karaf JBoss EAP (only integration with Hawtio) Spring Boot 2 (only integration with Hawtio) |
Red Hat Fuse 7.11 LDAP Providers
The following LDAP providers are supported with Fuse 7.11:
Server | Version |
---|---|
Apache Directory | 2.0.0-M24 |
OpenLDAP | 2.4.44 |
Red Hat Directory Server | 10.6 |
Windows Active Directory | 69 (Windows Server 2012 R2) |
Red Hat Fuse 7.11 Supported Data Grid
Client
Camel component | RH-JDG Version | Target Container |
---|---|---|
camel-infinispan | 9.4.19.Final-redhat-00001 | Apache Karaf Spring Boot 2 |
11.0.15.Final-redhat-00001 | JBoss EAP |
Server
Server | RH-JDG Version | Target Container |
---|---|---|
redhat-datagrid | 8.x | Apache Karaf JBoss EAP Spring Boot 2 |
Red Hat Fuse 7.11 Supported SAP Client Integrations
Red Hat's Apache Camel SAP component works with the following JCo client and IDoc client libraries:
Component | SAP Client | Version |
---|---|---|
Camel SAP | JCo | 3.1.4 |
Camel SAP | IDoc | 3.1.1 |
Red Hat Fuse 7.11 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.11 release.
Browser |
---|
Mozilla Firefox |
Google Chrome |
Microsoft Edge |
Red Hat Fuse 7.10
Red Hat provides both production and development support for supported configurations according to your subscription agreement in both physical and virtual environments.
Red Hat Fuse 7.10 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.
Red Hat Fuse 7.10 on OpenShift
You must run Fuse on OpenShift on a supported version of OpenShift. The following OpenShift versions were tested against Red Hat Fuse 7.10 on OpenShift at the time of the relevant OpenShift release:
OpenShift Product | Version | Chipset Architecture |
---|---|---|
OpenShift Container Platform (OCP) | 4.10 | x86_64 s390x ppc64le |
4.9* | x86_64 s390x ppc64le |
|
4.6 | x86_64 | |
3.11 | x86_64 | |
OpenShift Kubernetes Engine (OKE) | 4.10* | x86_64 s390x ppc64le |
4.6 | x86_64 |
NOTE: Before upgrading OpenShift to version 4.9 and above, you must upgrade Fuse to version 7.10.
NOTE: In Fuse 7.10, installing the Fuse on OpenShift imagestreams and templates on IBM Power Systems and IBM Z is not supported
Red Hat Fuse 7.10 without OpenShift on a Cloud Platform
If you deploy Fuse without OpenShift directly on any cloud platform — for example, MS Azure or Amazon Web Services (AWS) — Red Hat support extends to the Fuse components, but not to the underlying cloud platform. Red Hat does not provide any documentation on installing and configuring Fuse without OpenShift on cloud platforms. Consult your cloud provider's documentation to learn how to configure your application deployments in the cloud.
For more information, see Support Guidelines for Red Hat Middleware Products Deployed in 3rd-party Environments.
Red Hat Fuse 7.10 Supported Java Runtimes
You must run Red Hat Fuse 7.10 in one of the following Java runtimes and on one of the operating systems supported by that runtime.
Java Virtual Machine | Version |
---|---|
OpenJDK | 1.8, 11 |
Oracle JDK | 1.8, 11 |
IBM JDK | 1.8 |
HP JVM | 1.8 |
IBM Semeru | 11.0.13.0 |
Adoptium JDK | 1.8, 11 |
NOTE: Red Hat limits support of OpenJDK to the Red Hat builds of OpenJDK for Red Hat Enterprise Linux (RHEL) and Windows.
NOTE: IBM Semeru is currently the only runtime supported on IBM Power Systems (ppc64le), IBM Z, and LinuxONE (390x)
NOTE: Red Hat limits support of Adoptium JDK to Red Hat Enterprise Linux (RHEL) and Windows
Red Hat Fuse 7.10 Supported Container Types
For Fuse 7.10, the following container types and versions are supported:
Container Type | Version | Chipset Architecture |
---|---|---|
Spring Boot 2 | 2.3.12.RELEASE | x86_64 s390x ppc64le |
JBoss Enterprise Application Platform | 7.4.2 (and subsequent 7.4.x micro versions) | x86_64 |
Apache Karaf | 4.2.12.fuse | x86_64 |
NOTE: For Fuse on JBoss EAP deployments, operating system support aligns with Red Hat JBoss EAP 7 Supported Configurations.
Spring Boot 2 Support
Red Hat Fuse 7.10 on OpenShift is reliant on the Spring Boot Community version and, as such, Red Hat's support for Spring Boot 2 is limited to its intended use as documented in the quickstarts and templates. We will offer a commercially reasonable effort to support Spring Boot 2, however, we may not be able to provide or influence timely patches.
In addition to deployment of Spring Boot 2 on OpenShift, deployment of Spring Boot 2 in standalone mode (Jar file running on a supported JVM) is also supported by Red Hat, provided your application uses the dependencies from the Spring Boot 2 BOM (Apache Maven Bill of Materials) file.
For more details, see Spring Boot Support.
Red Hat Fuse 7.10 Supported Configurations
Red Hat has performed the full range of platform tests on the following tested configurations:
Chipset Architecture | Operating System | Java Runtime Environment |
---|---|---|
x86_64 | Red Hat Enterprise Linux 8 (latest update) | Oracle JDK 1.8.x †, 11.0.x IBM JDK 1.8.x Red Hat build of OpenJDK 1.8 †, 11.0.x |
x86_64 | Red Hat Enterprise Linux 7 (latest update) | Oracle JDK 1.8.x †, 11.0.x IBM JDK 1.8.x Red Hat build of OpenJDK 1.8 †, 11.0.x |
x86_64 | Microsoft Windows Server 2019 | Oracle JDK 1.8.x †, OpenJDK 1.8 † |
s390x | Red Hat Enterprise Linux 8 (latest update) | IBM Semeru 11.0.13.0 |
ppc64le | Red Hat Enterprise Linux 8 (latest update) | IBM Semeru 11.0.13.0 |
† IMPORTANT: Both OpenJDK 8u292 and OracleJDK 1.8.0_291 suffer from a known issue in the security API, which affects the credentials store in Apache Karaf. We recommend that you avoid these JDK versions. For OpenJDK, you could use either OpenJDK 8u282 or OpenJDK 8u302, which are not affected by this issue.
The following configurations are supported, but not fully tested:
Chipset Architecture | Operating System | Java Virtual Machine |
---|---|---|
SPARC64 | Oracle Solaris 11 NOTE: (partial legacy testing, not recommended for new deployments) | Oracle JDK 1.8.x |
Power ISA | IBM AIX 7.2 (partial legacy testing, not recommended for new deployments) | IBM JDK 1.8.x |
IA64 | HP-UX 11i (Deprecated) (Not supported on JBoss EAP since version 7.2) | HP JVM 1.8.x |
NOTE: For Fuse on JBoss EAP deployments, operating system support aligns with Red Hat JBoss EAP 7 Supported Configurations.
Red Hat Fuse 7.10 Tested Integrations
NOTE: The integrations described in this section were tested only for systems based on x86_64 architectures and do not apply to IBM Power Systems (ppc64le) or IBM Z (s390x) unless explicitly stated.
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. They were tested on IBM Power Systems (ppc64le) also.
Databases | JDBC Driver |
---|---|
Oracle 12c r2 RAC | Oracle JDBC Driver v12 |
Oracle 18c r3 RAC | Oracle JDBC Driver v18 |
Oracle 19c r3 RAC | Oracle JDBC Driver v19 |
MySQL 5.7 | MySQL Connector/J 5 |
MySQL 8.0 | MySQL Connector/J 8 |
Microsoft SQL Server 2017 | MS SQL Server JDBC Driver 7.4 |
Microsoft SQL Server 2019* | MS SQL Server JDBC Driver 7.4 |
PostgreSQL 12.5 | JDBC Postgresql Driver, Version 42.2.19 |
PostgreSQL 13.2 | JDBC Postgresql Driver, Version 42.2.19 |
IBM DB2 10.5* | IBM DB2 JDBC Universal Driver Architecture 4.19 |
IBM DB2 11.1 | IBM DB2 JDBC Universal Driver Architecture 4.25 |
NOTE IBM DB2 10.5 is not supported on JBoss EAP.
NOTE Red Hat tests database integrations using the JDBC driver versions shown above. These drivers are compatible with a range of database server versions. See your database vendor’s documentation for information about JDBC driver compatibility with specific server versions.
Supported Messaging Providers
Since Fuse 7.0, only remote brokers are supported.
Broker | Version | Target Containers |
---|---|---|
JBoss A-MQ | 6.3 | Apache Karaf Spring Boot 2.3 JBoss EAP |
AMQ Broker | 7.8.2 | Apache Karaf Spring Boot 2.3 JBoss EAP |
AMQ Streams | 1.8.0 | Apache Karaf Spring Boot 2.3 JBoss EAP |
Websphere MQ1 | 8.0 | Apache Karaf Spring Boot 2.3 JBoss EAP |
9.1 | Apache Karaf Spring Boot 2.3 JBoss EAP |
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.10.
Messaging Components for Apache Karaf
The following messaging components are tested on Apache Karaf:
Apache Karaf | |||
---|---|---|---|
Broker | Version | Client | Camel components |
JBoss A-MQ | 6.3 | activemq-client
|
camel-activemq |
AMQ Broker | 7.8.2 | artemis-jms-client |
camel-jms camel-sjms camel-sjms2 |
qpid-jms-client |
camel-amqp |
||
WebSphere MQ | 8.0 | Client v8 | camel-jms |
9.1 | Client v9.1.0.6 | camel-jms |
Messaging Components for JBoss EAP
Messaging on the JBoss EAP container is supported using JCA adapters, see JBoss EAP 7.4 Supported Configurations. The following messaging components are tested on JBoss EAP 7.4:
JBoss EAP | |||
---|---|---|---|
Broker | Version | Adapter | Camel components |
JBoss A-MQ | 6.3 | AMQ JCA Adapter v5.11.0 |
camel-jms |
AMQ Broker | 7.8.2 | AMQ JCA Adapter which is integrated in JBoss EAP 7.4 | camel-jms camel-sjms |
WebSphere MQ | 8.0 | Client v8 | camel-jms |
9.1 | Client v9 | camel-jms |
Messaging Components for Spring Boot
The following messaging components are tested on Spring Boot 2.3:
Spring Boot 2.3 | |||
---|---|---|---|
Broker | Version | Client | Camel components |
JBoss A-MQ | 6.3 | activemq-client |
camel-jms |
AMQ Broker | 7.8.2 | artemis-jms-client |
camel-jms camel-sjms camel-sjms2 |
qpid-jms-client |
camel-amqp |
||
WebSphere MQ | 8.0 | Client v8 | camel-jms |
9.1 | Client v9.1.0.6 | 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.10 (Apache Karaf, and JBoss EAP, respectively).
Supported Security Providers
Red Hat Fuse 7 is tested against Red Hat Single Sign-On (RH SSO). The following RH SSO versions are supported with Fuse 7.10:
Security Provider | Version | Target Containers |
---|---|---|
RH SSO | 7.4.9.GA | Apache Karaf JBoss EAP |
Supported SAP Client Integrations
Red Hat's Apache Camel SAP component works with the following JCo client and IDoc client libraries:
Component | SAP Client | Version |
---|---|---|
Camel SAP | JCo | 3.1.4 |
Camel SAP | IDoc | 3.1.1 |
Red Hat Fuse 7.10 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.10 release.
Browser |
---|
Mozilla Firefox |
Google Chrome |
Red Hat Fuse 7.9
Red Hat Fuse 7.9 on OpenShift
OpenShift Deployment
You must run Fuse on OpenShift on a supported version of OpenShift. The following OpenShift versions were tested against Red Hat Fuse 7.9 on OpenShift at the time of the relevant OpenShift release:
OpenShift Product | Versions |
---|---|
OpenShift Container Platform (OCP) |
4.6, 4.7, 4.8 3.11 |
OpenShift Kubernetes Engine (OKE) | 4.6, 4.7, 4.8 |
Spring Boot 2 Support
Red Hat Fuse 7.9 on OpenShift is reliant on the Spring Boot Community version. Red Hat's support for Spring Boot 2 is limited to its intended use as documented in the quickstarts and templates. We will offer a commercially reasonable effort to support Spring Boot 2, however, we may not be able to provide or influence timely patches.
In addition to deployment of Spring Boot 2 on OpenShift, deployment of Spring Boot 2 in standalone mode (Jar file running on a supported JVM) is also supported by Red Hat, provided your application uses the dependencies from the Spring Boot 2 BOM (Apache Maven Bill of Materials) file.
For more details, see Spring Boot Support.
Red Hat Fuse 7.9 Supported Configurations
Red Hat provides both production and development support for supported configurations according to your subscription agreement in both physical and virtual environments.
Red Hat Fuse 7.9 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
You must run Red Hat Fuse 7.9 in one of the following JVM versions and on one of the operating systems supported by that JVM.
Java Virtual Machine | Version |
---|---|
OpenJDK | 1.8, 11* |
Oracle JDK | 1.8, 11* |
IBM JDK | 1.8 |
HP JVM | 1.8 |
NOTE: Java 11 is currently supported only on the Spring Boot 2 runtime and the JBoss EAP runtime. Support for Java 11 on Apache Karaf will come in a later release.
NOTE: Red Hat limits support of OpenJDK to the Red Hat builds of OpenJDK for Red Hat Enterprise Linux (RHEL) and Windows
Supported JBoss EAP Versions
For Fuse 7.9 on EAP installations, the following versions of JBoss Enterprise Application Platform (EAP) are supported:
Java EE Container | Version |
---|---|
JBoss Enterprise Application Platform | 7.4.0 (and subsequent 7.4.x micro versions) |
Fuse without OpenShift on a cloud platform
If you deploy Fuse without OpenShift directly on any cloud platform — for example, MS Azure or Amazon Web Services (AWS) — Red Hat support extends to the Fuse components, but not to the underlying cloud platform. Red Hat does not provide any documentation on installing and configuring Fuse without OpenShift on cloud platforms. Consult your cloud provider's documentation to learn how to configure your application deployments in the cloud.
For more information, see Support Guidelines for Red Hat Middleware Products Deployed in 3rd-party Environments.
Red Hat Fuse 7.9 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 8 (latest update) | x86_64 | Oracle JDK 1.8.x †, 11.0.x* IBM JDK 1.8.x Red Hat build of OpenJDK 1.8 †, 11.0.x* |
Red Hat Enterprise Linux 7 (latest update) | x86_64 | Oracle JDK 1.8.x †, 11.0.x* IBM JDK 1.8.x Red Hat build of OpenJDK 1.8 †, 11.0.x* |
Microsoft Windows Server 2019 | x86_64 | Oracle JDK 1.8.x †, OpenJDK 1.8 † |
* Java 11 is currently supported only on the Spring Boot 2 runtime and the JBoss EAP runtime. Support for Java 11 on Apache Karaf will come in a later release.
† IMPORTANT: Both OpenJDK 8u292 and OracleJDK 1.8.0_291 suffer from a known issue in the security API, which affects the credentials store in Apache Karaf. We recommend that you avoid these JDK versions. For OpenJDK, you could use either OpenJDK 8u282 or OpenJDK 8u302, which are not affected by this issue.
The following configurations are supported, but not fully tested:
Operating System | Chipset Architecture | Java Virtual Machine |
---|---|---|
Oracle Solaris 11 NOTE: (partial legacy testing, not recommended for new deployments) | SPARC64 | Oracle JDK 1.8.x |
IBM AIX 7.2 (partial legacy testing, not recommended for new deployments) | Power ISA | IBM JDK 1.8.x |
HP-UX 11i (Deprecated) (Not supported on JBoss EAP since version 7.2) | IA64 | HP JVM 1.8.x |
NOTE: For Fuse on JBoss EAP deployments, operating system support aligns with Red Hat JBoss EAP 7 Supported Configurations.
Red Hat Fuse 7.9 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 r2 RAC | Oracle JDBC Driver v12 |
Oracle 18c r3 RAC | Oracle JDBC Driver v18 |
Oracle 19c r3 RAC | Oracle JDBC Driver v19 |
MySQL 5.7 | MySQL Connector/J 5 |
MySQL 8.0 | MySQL Connector/J 8 |
Microsoft SQL Server 2017 | MS SQL Server JDBC Driver 6.0 |
Microsoft SQL Server 2019* | MS SQL Server JDBC Driver 6.0 |
PostgreSQL 11.5 | JDBC Postgresql Driver, Version 42.2.12 |
PostgreSQL 12.5 | JDBC Postgresql Driver, Version 42.2.12 |
IBM DB2 10.5* | IBM DB2 JDBC Universal Driver Architecture 4.19 |
IBM DB2 11.1 | IBM DB2 JDBC Universal Driver Architecture 4.25 |
NOTE IBM DB2 10.5 is not supported on JBoss EAP.
NOTE Red Hat tests database integrations using the JDBC driver versions shown above. These drivers are compatible with a range of database server versions. See your database vendor’s documentation for information about JDBC driver compatibility with specific server versions.
Supported Messaging Providers
Since Fuse 7.0, only remote brokers are supported.
Broker | Version | Target Containers |
---|---|---|
JBoss A-MQ | 6.3 | Apache Karaf Spring Boot 2.3 JBoss EAP |
AMQ Broker | 7.8.2 | Apache Karaf Spring Boot 2.3 JBoss EAP |
AMQ Streams | 1.7.0 | Apache Karaf Spring Boot 2.3 JBoss EAP |
Websphere MQ1 | 8.0 | Apache Karaf Spring Boot 2.3 JBoss EAP |
9.1 | Apache Karaf Spring Boot 2.3 JBoss EAP |
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.9.
Messaging Components for Apache Karaf
The following messaging components are tested on Apache Karaf:
Apache Karaf | |||
---|---|---|---|
Broker | Version | Client | Camel components |
JBoss A-MQ | 6.3 | activemq-client
|
camel-activemq |
AMQ Broker | 7.8.2 | artemis-jms-client |
camel-jms camel-sjms camel-sjms2 |
qpid-jms-client |
camel-amqp |
||
WebSphere MQ | 8.0 | Client v8 | camel-jms |
9.1 | Client v9.1.0.6 | camel-jms |
Messaging Components for JBoss EAP
Messaging on the JBoss EAP container is supported using JCA adapters, see JBoss EAP 7.4 Supported Configurations. The following messaging components are tested on JBoss EAP 7.4:
JBoss EAP | |||
---|---|---|---|
Broker | Version | Adapter | Camel components |
JBoss A-MQ | 6.3 | AMQ JCA Adapter v5.11.0 |
camel-jms |
AMQ Broker | 7.8.2 | AMQ JCA Adapter which is integrated in JBoss EAP 7.4 | camel-jms camel-sjms |
WebSphere MQ | 8.0 | Client v8 | camel-jms |
9.0 | Client v9 | camel-jms |
Messaging Components for Spring Boot
The following messaging components are tested on Spring Boot 2.3:
Spring Boot 2.3 | |||
---|---|---|---|
Broker | Version | Client | Camel components |
JBoss A-MQ | 6.3 | activemq-client |
camel-jms |
AMQ Broker | 7.8.2 | artemis-jms-client |
camel-jms camel-sjms camel-sjms2 |
qpid-jms-client |
camel-amqp |
||
WebSphere MQ | 8.0 | Client v8 | camel-jms |
9.1 | Client v9.1.0.6 | 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.9 (Apache Karaf, and JBoss EAP, respectively).
Supported Security Providers
Red Hat Fuse 7 is tested against Red Hat Single Sign-On (RH SSO). The following RH SSO versions are supported with Fuse 7.9:
Security Provider | Version | Target Containers |
---|---|---|
RH SSO | 7.4.6.GA | Apache Karaf JBoss EAP |
Supported SAP Client Integrations
Red Hat's Apache Camel SAP component works with the following JCo client and IDoc client libraries:
Component | SAP Client | Version |
---|---|---|
Camel SAP | JCo | 3.1.2 |
Camel SAP | IDoc | 3.1.0 |
Red Hat Fuse 7.9 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.9 release.
Browser |
---|
Mozilla Firefox |
Google Chrome |
Red Hat Fuse 7.8
Red Hat Fuse 7.8 on OpenShift
OpenShift Deployment
You must run Fuse on OpenShift on a supported version of OpenShift. The following OpenShift versions were tested against Red Hat Fuse 7.8 on OpenShift at the time of the relevant OpenShift release:
OpenShift Product | Versions |
---|---|
OpenShift Container Platform (OCP) |
4.6, 4.5 3.11 |
OpenShift Kubernetes Engine (OKE) | 4.6, 4.5 |
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
Important: In Fuse 7.8, only Spring Boot 2 is supported. Spring Boot 1 has been removed from this release.
Red Hat Fuse 7.8 on OpenShift is reliant on the Spring Boot Community version. 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.8 Supported Configurations
Red Hat provides both production and development support for supported configurations according to your subscription agreement in both physical and virtual environments.
Red Hat Fuse 7.8 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
You must run Red Hat Fuse 7.8 in one of the following JVM versions and on one of the operating systems supported by that JVM.
Java Virtual Machine | Version |
---|---|
OpenJDK | 1.8 |
Oracle JDK | 1.8 |
IBM JDK | 1.8 |
HP JVM | 1.8 |
NOTE: Red Hat limits support of OpenJDK to the Red Hat builds of OpenJDK for Red Hat Enterprise Linux (RHEL) and Windows.
Supported JBoss EAP Versions
For Fuse 7.8 on EAP installations, the following versions of JBoss Enterprise Application Platform (EAP) are supported:
Java EE Container | Version |
---|---|
JBoss Enterprise Application Platform | 7.3.2 (and subsequent 7.3.x micro versions) |
Fuse without OpenShift on a cloud platform
If you deploy Fuse without OpenShift directly on any cloud platform — for example, MS Azure or Amazon Web Services (AWS) — Red Hat support extends to the Fuse components, but not to the underlying cloud platform. Red Hat does not provide any documentation on installing and configuring Fuse without OpenShift on cloud platforms. Consult your cloud provider's documentation to learn how to configure your application deployments in the cloud.
For more information, see Support Guidelines for Red Hat Middleware Products Deployed in 3rd-party Environments.
Red Hat Fuse 7.8 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 8 (latest update) | x86_64 | Oracle JDK 1.8.x IBM JDK 1.8.x Red Hat build of OpenJDK 1.8 |
Red Hat Enterprise Linux 7 (latest update) | x86_64 | Oracle JDK 1.8.x IBM JDK 1.8.x Red Hat build of OpenJDK 1.8 |
Microsoft Windows Server 2016 | x86_64 | Oracle JDK 1.8.x |
The following configurations are supported, but not fully tested:
Operating System | Chipset Architecture | Java Virtual Machine |
---|---|---|
Oracle Solaris 11 NOTE: (partial legacy testing, not recommended for new deployments) | SPARC64 | Oracle JDK 1.8.x |
IBM AIX 7.2 (partial legacy testing, not recommended for new deployments) | Power ISA | IBM JDK 1.8.x |
HP-UX 11i (Deprecated) (Not supported on JBoss EAP since version 7.2) | IA64 | HP JVM 1.8.x |
NOTE: For Fuse on JBoss EAP deployments, operating system support aligns with Red Hat JBoss EAP 7 Supported Configurations.
Red Hat Fuse 7.8 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 r2 RAC | Oracle JDBC Driver v12 |
Oracle 18c r3 RAC | Oracle JDBC Driver v18 |
Oracle 19c r3 RAC | Oracle JDBC Driver v19 |
MySQL 5.7 | MySQL Connector/J 5 |
MySQL 8.0 | MySQL Connector/J 8 |
Microsoft SQL Server 2016 | MS SQL Server JDBC Driver 6.0 |
Microsoft SQL Server 2017* | MS SQL Server JDBC Driver 6.0 |
PostgreSQL 10.8 | JDBC Postgresql Driver, Version 42.2.12 |
PostgreSQL 11.5 | JDBC Postgresql Driver, Version 42.2.12 |
IBM DB2 10.5* | IBM DB2 JDBC Universal Driver Architecture 4.19 |
IBM DB2 11.1 | IBM DB2 JDBC Universal Driver Architecture 4.25 |
NOTE IBM DB2 10.5 is not supported on JBoss EAP.
NOTE Red Hat tests database integrations using the JDBC driver versions shown above. These drivers are compatible with a range of database server versions. See your database vendor’s documentation for information about JDBC driver compatibility with specific server versions.
Supported Messaging Providers
Since Fuse 7.0, only remote brokers are supported.
Broker | Version | Target Containers |
---|---|---|
JBoss A-MQ | 6.3 | Apache Karaf Spring Boot 2.3 JBoss EAP |
AMQ Broker | 7.7.0 | Apache Karaf Spring Boot 2.3 JBoss EAP |
AMQ Streams | 1.5.0 | Apache Karaf Spring Boot 2.3 JBoss EAP |
Websphere MQ1 | 8.0 | Apache Karaf Spring Boot 2.3 JBoss EAP |
9.0 | JBoss EAP | |
9.1 | Apache Karaf Spring Boot 2.3 |
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.8.
Messaging Components for Apache Karaf
The following messaging components are tested on Apache Karaf:
Apache Karaf | |||
---|---|---|---|
Broker | Version | Client | Camel components |
JBoss A-MQ | 6.3 | activemq-client
|
camel-activemq |
AMQ Broker | 7.7.0 | artemis-jms-client |
camel-jms camel-sjms camel-sjms2 |
qpid-jms-client |
camel-amqp |
||
WebSphere MQ | 8.0 | Client v8 | camel-jms |
9.1 | Client v9.1.0.6 | camel-jms |
Messaging Components for JBoss EAP
Messaging on the JBoss EAP container is supported using JCA adapters, see JBoss EAP 7.3 Supported Configurations. The following messaging components are tested on JBoss EAP 7.3:
JBoss EAP | |||
---|---|---|---|
Broker | Version | Adapter | Camel components |
JBoss A-MQ | 6.3 | AMQ JCA Adapter v5.11.0 |
camel-jms |
AMQ Broker | 7.7.0 | AMQ JCA Adapter which is integrated in JBoss EAP 7.3 | camel-jms camel-sjms |
WebSphere MQ | 8.0 | Client v8 | camel-jms |
9.0 | Client v9 | camel-jms |
Messaging Components for Spring Boot
The following messaging components are tested on Spring Boot 2.3:
Spring Boot 2.3 | |||
---|---|---|---|
Broker | Version | Client | Camel components |
AMQ Broker | 7.7.0 | artemis-jms-client |
camel-jms camel-sjms camel-sjms2 |
qpid-jms-client |
camel-amqp |
||
WebSphere MQ | 8.0 | Client v8 | camel-jms |
9.1 | Client v9.1.0.6 | 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.8 (Apache Karaf, and JBoss EAP, respectively).
Supported Security Providers
Red Hat Fuse 7 is tested against Red Hat Single Sign-On (RH SSO). The following RH SSO versions are supported with Fuse 7.8:
Security Provider | Version | Target Containers |
---|---|---|
RH SSO | 7.4.2.GA | Apache Karaf JBoss EAP |
Supported SAP Client Integrations
Red Hat's Apache Camel SAP component works with the following JCo client and IDoc client libraries:
Component | SAP Client | Version |
---|---|---|
Camel SAP | JCo | 3.1.2 |
Camel SAP | IDoc | 3.1.0 |
Red Hat Fuse 7.8 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.8 release.
Browser |
---|
Mozilla Firefox |
Google Chrome |
Red Hat Fuse 7.7
Red Hat Fuse 7.7 on OpenShift
OpenShift Deployment
You must run Fuse on OpenShift on a supported version of OpenShift. The following OpenShift versions were tested against Red Hat Fuse 7.7 on OpenShift at the time of the relevant OpenShift release:
OpenShift Product | Versions |
---|---|
OpenShift Container Platform (OCP) |
4.6, 4.5, 4.4, 4.3 3.11 |
OpenShift Kubernetes Engine (OKE) | 4.6, 4.5, 4.4, 4.3 |
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
Important: Starting from Fuse 7.7, Spring Boot 1 is deprecated and will be removed in a future release (where both deployment options, Spring Boot 1 standalone and Spring Boot 1 on OpenShift are deprecated).
Red Hat Fuse 7.7 on OpenShift is reliant on the Spring Boot Community version. 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.7 Supported Configurations
Red Hat provides both production and development support for supported configurations according to your subscription agreement in both physical and virtual environments.
Red Hat Fuse 7.7 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
You must run Red Hat Fuse 7.7 in one of the following JVM versions and on one of the operating systems supported by that JVM.
Java Virtual Machine | Version |
---|---|
OpenJDK | 1.8 |
Oracle JDK | 1.8 |
IBM JDK | 1.8 |
HP JVM | 1.8 |
NOTE: Red Hat limits support of OpenJDK to the Red Hat builds of OpenJDK for Red Hat Enterprise Linux (RHEL) and Windows.
Supported JBoss EAP Versions
For Fuse 7.7 on EAP installations, the following versions of JBoss Enterprise Application Platform (EAP) are supported:
Java EE Container | Version |
---|---|
JBoss Enterprise Application Platform | 7.2.7 (and subsequent 7.2.x micro versions) |
Fuse without OpenShift on a cloud platform
If you deploy Fuse without OpenShift directly on any cloud platform — for example, MS Azure or Amazon Web Services (AWS) — Red Hat support extends to the Fuse components, but not to the underlying cloud platform. Red Hat does not provide any documentation on installing and configuring Fuse without OpenShift on cloud platforms. Consult your cloud provider's documentation to learn how to configure your application deployments in the cloud.
For more information, see Support Guidelines for Red Hat Middleware Products Deployed in 3rd-party Environments.
Red Hat Fuse 7.7 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 8 (latest update) | x86_64 | Oracle JDK 1.8.x IBM JDK 1.8.x Red Hat build of OpenJDK 1.8 |
Red Hat Enterprise Linux 7 (latest update) | x86_64 | Oracle JDK 1.8.x IBM JDK 1.8.x Red Hat build of OpenJDK 1.8 |
Microsoft Windows Server 2016 | x86_64 | Oracle JDK 1.8.x |
The following configurations are supported, but not fully tested:
Operating System | Chipset Architecture | Java Virtual Machine |
---|---|---|
Oracle Solaris 11 NOTE: (partial legacy testing, not recommended for new deployments) | SPARC64 | Oracle JDK 1.8.x |
IBM AIX 7.2 (partial legacy testing, not recommended for new deployments) | Power ISA | IBM JDK 1.8.x |
HP-UX 11i (Deprecated) (Not supported for JBoss EAP 7.2) | IA64 | HP JVM 1.8.x |
NOTE: For Fuse on JBoss EAP deployments, operating system support aligns with Red Hat JBoss EAP 7 Supported Configurations.
Red Hat Fuse 7.7 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 r2 RAC | Oracle JDBC Driver v12 |
Oracle 18c r3 RAC | Oracle JDBC Driver v18 |
Oracle 19c r3 RAC | Oracle JDBC Driver v19 |
MySQL 5.7 | MySQL Connector/J 5 |
MySQL 8.0 | MySQL Connector/J 8 |
Microsoft SQL Server 2016 | MS SQL Server JDBC Driver 6.0 |
Microsoft SQL Server 2017* | MS SQL Server JDBC Driver 6.0 |
PostgreSQL 10.8 | JDBC Postgresql Driver, Version 42.2.12 |
PostgreSQL 11.5 | JDBC Postgresql Driver, Version 42.2.12 |
IBM DB2 10.5* | IBM DB2 JDBC Universal Driver Architecture 4.19 |
IBM DB2 11.1 | IBM DB2 JDBC Universal Driver Architecture 4.25 |
NOTE IBM DB2 10.5 is not supported on JBoss EAP.
NOTE Red Hat tests database integrations using the JDBC driver versions shown above. These drivers are compatible with a range of database server versions. See your database vendor’s documentation for information about JDBC driver compatibility with specific server versions.
Supported Messaging Providers
Since Fuse 7.0, only remote brokers are supported.
Broker | Version | Target Containers |
---|---|---|
JBoss A-MQ | 6.3 | Apache Karaf Spring Boot 1.5 JBoss EAP |
AMQ Broker | 7.7.0 | Apache Karaf Spring Boot 1.5 Spring Boot 2.1 JBoss EAP |
AMQ Streams | 1.5.0 | Apache Karaf Spring Boot 1.5 Spring Boot 2.1 JBoss EAP |
Websphere MQ1 | 8.0 | Apache Karaf Spring Boot 1.5 JBoss EAP |
9.0 | Apache Karaf Spring Boot 1.5 JBoss EAP |
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.7.
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 Broker | 7.7.0 | artemis-jms-client |
camel-jms camel-sjms camel-sjms2 |
qpid-jms-client |
camel-amqp |
||
WebSphere MQ | 8.0 | Client v8 | camel-jms |
9.0 | Client v9 | camel-jms |
Messaging on the JBoss EAP container is supported using JCA adapters, see JBoss EAP 7.2 Supported Configurations. The following messaging components are supported on JBoss EAP 7.2:
JBoss EAP | |||
---|---|---|---|
Broker | Version | Adapter | Camel components |
JBoss A-MQ | 6.3 | AMQ JCA Adapter v5.11.0 |
camel-activemq |
AMQ | 7.2.x | AMQ JCA Adapter which is integrated in JBoss EAP 7.2 | camel-jms camel-sjms |
WebSphere MQ | 8.0 | Client v8 | camel-jms |
9.0 | Client v9 | camel-jms |
The following messaging components are supported on Spring Boot 1.5:
Spring Boot 1.5 | |||
---|---|---|---|
Broker | Version | Client | Camel components |
JBoss A-MQ | 6.3 | activemq-client
|
camel-activemq |
AMQ Broker | 7.7.0 | artemis-jms-client |
camel-jms camel-sjms camel-sjms2 |
qpid-jms-client |
camel-amqp |
||
WebSphere MQ | 8.0 | Client v8 | camel-jms (not tested) |
9.0 | Client v9 | camel-jms |
The following messaging components are supported on Spring Boot 2.1:
Spring Boot 2.1 | |||
---|---|---|---|
Broker | Version | Client | Camel components |
AMQ Broker | 7.7.0 | artemis-jms-client |
camel-jms camel-sjms camel-sjms2 |
qpid-jms-client |
camel-amqp |
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.7 (Apache Karaf, JBoss EAP, and Spring Boot 1.x, respectively).
Supported Security Providers
Red Hat Fuse 7 is tested against Red Hat Single Sign-On (RH SSO). The following RH SSO versions are supported with Fuse 7.7:
Security Provider | Version | Target Containers |
---|---|---|
RH SSO | 7.3.7.GA | Apache Karaf JBoss EAP |
Red Hat Fuse 7.7 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.7 release.
Browser |
---|
Mozilla Firefox |
Google Chrome |
Red Hat Fuse 7.6
Red Hat Fuse 7.6 on OpenShift
OpenShift Deployment
You must run Fuse on OpenShift on a supported version of OpenShift Container Platform (OCP). The following versions of OCP were tested against Red Hat Fuse 7.6 on OpenShift at the time of the relevant OCP GA release:
OpenShift Product | Versions |
---|---|
OpenShift Container Platform (OCP) |
4.3, 4.2 3.11 |
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.6 on OpenShift is reliant on the Spring Boot Community version. 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.6 Supported Configurations
Red Hat provides both production and development support for supported configurations according to your subscription agreement in both physical and virtual environments.
Red Hat Fuse 7.6 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
You must run Red Hat Fuse 7.6 in one of the following JVM versions and on one of the operating systems supported by that JVM.
Java Virtual Machine | Version |
---|---|
OpenJDK | 1.8 |
Oracle JDK | 1.8 |
IBM JDK | 1.8 |
HP JVM | 1.8 |
NOTE: Red Hat limits support of OpenJDK to the Red Hat builds of OpenJDK for Red Hat Enterprise Linux (RHEL) and Windows.
NOTE: For Spring Boot 2 standalone deployments, IBM JDK 8 is currently not tested and not supported.
Supported JBoss EAP Versions
For Fuse 7.6 on EAP installations, the following versions of JBoss Enterprise Application Platform (EAP) are supported:
Java EE Container | Version |
---|---|
JBoss Enterprise Application Platform | 7.2.5 (and subsequent 7.2.x micro versions) |
Fuse without OpenShift on a cloud platform
If you deploy Fuse without OpenShift directly on any cloud platform — for example, MS Azure or Amazon Web Services (AWS) — Red Hat support extends to the Fuse components, but not to the underlying cloud platform. Red Hat does not provide any documentation on installing and configuring Fuse without OpenShift on cloud platforms. Consult your cloud provider's documentation to learn how to configure your application deployments in the cloud.
For more information, see Support Guidelines for Red Hat Middleware Products Deployed in 3rd-party Environments.
Red Hat Fuse 7.6 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 8 (latest update) | x86_64 | Oracle JDK 1.8.x IBM JDK 1.8.x Red Hat build of OpenJDK 1.8 |
Red Hat Enterprise Linux 7 (latest update) | x86_64 | Oracle JDK 1.8.x IBM JDK 1.8.x Red Hat build of OpenJDK 1.8 |
Microsoft Windows Server 2016 | x86_64 | Oracle JDK 1.8.x |
Oracle Solaris 11 NOTE: (partial legacy testing, not recommended for new deployments) | SPARC64 | Oracle JDK 1.8.x |
IBM AIX 7.2 (partial legacy testing, not recommended for new deployments) | Power ISA | IBM JDK 1.8.x |
HP-UX 11i (Deprecated) (Not supported for JBoss EAP 7.2) | IA64 | HP JVM 1.8.x |
NOTE: For Fuse on JBoss EAP deployments, operating system support aligns with Red Hat JBoss EAP 7 Supported Configurations.
NOTE: For Spring Boot 2 standalone deployments, the HP-UX, AIX, and Solaris operating systems are currently not tested and not supported.
Red Hat Fuse 7.6 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 r2 | Oracle JDBC Driver v12 |
Oracle 12c r2 RAC | Oracle JDBC Driver v12 |
MySQL 5.7 | MySQL Connector/J 5 |
MySQL 8.0 | MySQL Connector/J 8 |
Microsoft SQL Server 2016 | MS SQL Server JDBC Driver 6.0 |
Microsoft SQL Server 2017* | MS SQL Server JDBC Driver 6.0 | PostgreSQL 9.6* | JDBC 4.2 Postgresql Driver, Version 9 |
PostgreSQL 10.1 | JDBC Postgresql Driver, Version 42.2.5 |
IBM DB2 10.5* | IBM DB2 JDBC Universal Driver Architecture 4.19 |
IBM DB2 11.1 | IBM DB2 JDBC Universal Driver Architecture 4.25 |
NOTE IBM DB2 10.5 is not supported on JBoss EAP.
NOTE Red Hat tests database integrations using the JDBC driver versions shown above. These drivers are compatible with a range of database server versions. See your database vendor’s documentation for information about JDBC driver compatibility with specific server versions.
Supported Messaging Providers
Since Fuse 7.0, only remote brokers are supported.
Broker | Version | Target Containers |
---|---|---|
JBoss A-MQ | 6.3 | Apache Karaf Spring Boot 1.5 JBoss EAP |
AMQ Broker | 7.6.0 | Apache Karaf Spring Boot 1.5 Spring Boot 2.1 JBoss EAP |
AMQ Streams | 1.4.0 | Apache Karaf Spring Boot 1.5 Spring Boot 2.1 JBoss EAP |
Websphere MQ1 | 8.0 | Apache Karaf Spring Boot 1.5 JBoss EAP |
9.0 | Apache Karaf Spring Boot 1.5 JBoss EAP |
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.6.
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 Broker | 7.6.0 | artemis-jms-client |
camel-jms camel-sjms camel-sjms2 |
qpid-jms-client |
camel-amqp |
||
WebSphere MQ | 8.0 | Client v8 | camel-jms |
9.0 | Client v9 | camel-jms |
Messaging on the JBoss EAP container is supported using JCA adapters, see JBoss EAP 7.2 Supported Configurations. The following messaging components are supported on JBoss EAP 7.2:
JBoss EAP | |||
---|---|---|---|
Broker | Version | Adapter | Camel components |
JBoss A-MQ | 6.3 | AMQ JCA Adapter v5.11.0 |
camel-activemq |
AMQ | 7.2.x | AMQ JCA Adapter which is integrated in JBoss EAP 7.2 | camel-jms camel-sjms |
WebSphere MQ | 8.0 | Client v8 | camel-jms |
9.0 | Client v9 | camel-jms |
The following messaging components are supported on Spring Boot 1.5:
Spring Boot 1.5 | |||
---|---|---|---|
Broker | Version | Client | Camel components |
JBoss A-MQ | 6.3 | activemq-client
|
camel-activemq |
AMQ Broker | 7.6.0 | artemis-jms-client |
camel-jms camel-sjms camel-sjms2 |
qpid-jms-client |
camel-amqp |
||
WebSphere MQ | 8.0 | Client v8 | camel-jms (not tested) |
9.0 | Client v9 | camel-jms |
The following messaging components are supported on Spring Boot 2.1:
Spring Boot 2.1 | |||
---|---|---|---|
Broker | Version | Client | Camel components |
AMQ Broker | 7.6.0 | artemis-jms-client |
camel-jms camel-sjms camel-sjms2 |
qpid-jms-client |
camel-amqp |
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.6 (Apache Karaf, JBoss EAP, and Spring Boot 1.x, respectively).
Supported Security Providers
Red Hat Fuse 7 is tested against Red Hat Single Sign-On (RH SSO). The following RH SSO versions are supported with Fuse 7.6:
Security Provider | Version | Target Containers |
---|---|---|
RH SSO | 7.3.5.GA | Apache Karaf JBoss EAP |
Red Hat Fuse 7.6 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.6 release.
Browser |
---|
Mozilla Firefox |
Google Chrome |
Red Hat Fuse 7.5
Red Hat Fuse 7.5 on OpenShift
OpenShift Deployment
You must run Fuse on OpenShift on a supported version of OpenShift Container Platform (OCP). The following versions of OCP were tested against Red Hat Fuse 7.5 on OpenShift at the time of the relevant OCP GA release:
OpenShift Product | Versions |
---|---|
OpenShift Container Platform (OCP) |
4.3, 4.2, 4.1 3.11 |
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.5 on OpenShift is reliant on the Spring Boot Community version. 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.5 Supported Configurations
Red Hat provides both production and development support for supported configurations according to your subscription agreement in both physical and virtual environments.
Red Hat Fuse 7.5 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
You must run Red Hat Fuse 7.5 in one of the following JVM versions and on one of the operating systems supported by that JVM.
Java Virtual Machine | Version |
---|---|
OpenJDK | 1.8 |
Oracle JDK | 1.8 |
IBM JDK | 1.8 |
HP JVM | 1.8 |
NOTE: Red Hat limits support of OpenJDK to the Red Hat builds of OpenJDK for Red Hat Enterprise Linux (RHEL) and Windows.
NOTE: For Spring Boot 2 standalone deployments, IBM JDK 8 is currently not tested and not supported.
Supported JBoss EAP Versions
For Fuse 7.5 on EAP installations, the following versions of JBoss Enterprise Application Platform (EAP) are supported:
Java EE Container | Version |
---|---|
JBoss Enterprise Application Platform | 7.2.3 |
Important: Fuse on EAP is not supported in managed domain operating mode. Only standalone server mode is supported.
Fuse without OpenShift on a cloud platform
If you deploy Fuse without OpenShift directly on any cloud platform — for example, MS Azure or Amazon Web Services (AWS) — Red Hat support extends to the Fuse components, but not to the underlying cloud platform. Red Hat does not provide any documentation on installing and configuring Fuse without OpenShift on cloud platforms. Consult your cloud provider's documentation to learn how to configure your application deployments in the cloud.
For more information, see Support Guidelines for Red Hat Middleware Products Deployed in 3rd-party Environments.
Red Hat Fuse 7.5 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 8 (latest update) | x86_64 | Oracle JDK 1.8.x IBM JDK 1.8.x Red Hat build of OpenJDK 1.8 |
Red Hat Enterprise Linux 7 (latest update) | x86_64 | Oracle JDK 1.8.x IBM JDK 1.8.x Red Hat build of OpenJDK 1.8 |
Microsoft Windows Server 2016 | x86_64 | Oracle JDK 1.8.x |
Oracle Solaris 11 NOTE: (partial legacy testing, not recommended for new deployments) | SPARC64 | Oracle JDK 1.8.x |
IBM AIX 7.2 (partial legacy testing, not recommended for new deployments) | Power ISA | IBM JDK 1.8.x |
HP-UX 11i (Deprecated) (Not supported for JBoss EAP 7.2) | IA64 | HP JVM 1.8.x |
NOTE: For Fuse on JBoss EAP deployments, operating system support aligns with Red Hat JBoss EAP 7 Supported Configurations.
NOTE: For Spring Boot 2 standalone deployments, the HP-UX, AIX, and Solaris operating systems are currently not tested and not supported.
Red Hat Fuse 7.5 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 r2 | Oracle JDBC Driver v12 |
Oracle 12c r2 RAC | Oracle JDBC Driver v12 |
MySQL 5.7 | MySQL Connector/J 5 |
MySQL 8.0 | MySQL Connector/J 8 |
Microsoft SQL Server 2016 | MS SQL Server JDBC Driver 6.0 |
Microsoft SQL Server 2017 (not supported on JBoss EAP) |
MS SQL Server JDBC Driver 6.0 | PostgreSQL 9.6* | JDBC 4.2 Postgresql Driver, Version 9 |
PostgreSQL 10.1 | JDBC Postgresql Driver, Version 42.2.5 |
IBM DB2 10.5* | IBM DB2 JDBC Universal Driver Architecture 4.19 |
IBM DB2 11.1 | IBM DB2 JDBC Universal Driver Architecture 4.25 |
NOTE IBM DB2 10.5 is not supported on JBoss EAP.
NOTE Red Hat tests database integrations using the JDBC driver versions shown above. These drivers are compatible with a range of database server versions. See your database vendor’s documentation for information about JDBC driver compatibility with specific server versions.
Supported Messaging Providers
Since Fuse 7.0, only remote brokers are supported.
Broker | Version | Target Containers |
---|---|---|
JBoss A-MQ | 6.3 | Apache Karaf Spring Boot 1.5 JBoss EAP |
AMQ Broker | 7.4.1 | Apache Karaf Spring Boot 1.5 Spring Boot 2.1 JBoss EAP |
AMQ Streams | 1.3.0 | Apache Karaf Spring Boot 1.5 Spring Boot 2.1 JBoss EAP |
Websphere MQ1 | 8.0 | Apache Karaf Spring Boot 1.5 JBoss EAP |
9.0 | Apache Karaf Spring Boot 1.5 JBoss EAP |
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.5.
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 Broker | 7.4.1 | artemis-jms-client |
camel-jms camel-sjms camel-sjms2 |
qpid-jms-client |
camel-amqp |
||
WebSphere MQ | 8.0 | Client v8 | camel-jms (not tested) |
9.0 | Client v9 | JMS API from Java code |
Messaging on the JBoss EAP container is supported using JCA adapters, see JBoss EAP 7.2 Supported Configurations. The following messaging components are supported on JBoss EAP 7.2:
JBoss EAP | |||
---|---|---|---|
Broker | Version | Adapter | Camel components |
JBoss A-MQ | 6.3 | AMQ JCA Adapter v5.11.0 |
camel-activemq |
AMQ | 7.2.x | AMQ JCA Adapter which is integrated in JBoss EAP 7.2 | camel-jms camel-sjms |
WebSphere MQ | 8.0 | Client v8 | camel-jms |
9.0 | Client v9 | camel-jms |
The following messaging components are supported on Spring Boot 1.5 (the messaging clients have not been tested in Spring Boot 2.1):
Spring Boot 1.5 | |||
---|---|---|---|
Broker | Version | Client | Camel components |
JBoss A-MQ | 6.3 | activemq-client
|
camel-activemq |
AMQ Broker | 7.4.1 | artemis-jms-client |
camel-jms camel-sjms camel-sjms2 |
qpid-jms-client |
camel-amqp |
||
WebSphere MQ | 8.0 | Client v8 | camel-jms (not tested) |
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.5 (Apache Karaf, JBoss EAP, and Spring Boot 1.x, respectively).
Supported Security Providers
Red Hat Fuse 7 is tested against Red Hat Single Sign-On (RH SSO). The following RH SSO versions are supported with Fuse 7.5:
Security Provider | Version | Target Containers |
---|---|---|
RH SSO | 7.3.3.GA | Apache Karaf JBoss EAP |
Red Hat Fuse 7.5 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.5 release.
Browser |
---|
Mozilla Firefox |
Google Chrome |
Microsoft Edge |
Red Hat Fuse 7.4
Red Hat Fuse 7.4 on OpenShift
OpenShift Deployment
You must run Fuse on OpenShift on a supported version of OpenShift Container Platform (OCP). The following versions of OCP were tested against Red Hat Fuse 7.4 on OpenShift at the time of the relevant OCP GA release:
OpenShift Product | Versions |
---|---|
OpenShift Container Platform (OCP) |
4.1 3.11 |
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.4 on OpenShift is reliant on the Spring Boot Community version. 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.4 Supported Configurations
Red Hat provides both production and development support for supported configurations according to your subscription agreement in both physical and virtual environments.
NOTE: Red Hat Fuse 7.4 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
You must run Red Hat Fuse 7.4 in one of the following JVM versions and on one of the operating systems supported by that JVM.
Java Virtual Machine | Version |
---|---|
OpenJDK | 1.8 |
Oracle JDK | 1.8 |
IBM JDK | 1.8 |
HP JVM | 1.8 |
NOTE: Red Hat limits support of OpenJDK to the Red Hat builds of OpenJDK for Red Hat Enterprise Linux (RHEL) and Windows.
NOTE: For Spring Boot 2 standalone deployments, IBM JDK 8 is currently not tested and not supported.
Supported JBoss EAP Versions
For Fuse 7.4 on EAP installations, the following versions of JBoss Enterprise Application Platform (EAP) are supported:
Java EE Container | Version |
---|---|
JBoss Enterprise Application Platform | 7.2.1 |
Important: Fuse on EAP is not supported in managed domain operating mode. Only standalone server mode is supported.
Fuse without OpenShift on a cloud platform
If you deploy Fuse without OpenShift directly on any cloud platform — for example, MS Azure or Amazon Web Services (AWS) — Red Hat support extends to the Fuse components, but not to the underlying cloud platform. Red Hat does not provide any documentation on installing and configuring Fuse without OpenShift on cloud platforms. Consult your cloud provider's documentation to learn how to configure your application deployments in the cloud.
For more information, see Support Guidelines for Red Hat Middleware Products Deployed in 3rd-party Environments.
Red Hat Fuse 7.4 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 8 (latest update) | x86_64 | Oracle JDK 1.8.x IBM JDK 1.8.x Red Hat build of OpenJDK 1.8 |
Red Hat Enterprise Linux 7 (latest update) | x86_64 | Oracle JDK 1.8.x IBM JDK 1.8.x Red Hat build of OpenJDK 1.8 |
Microsoft Windows Server 2016 | x86_64 | Oracle JDK 1.8.x |
Oracle Solaris 11 NOTE: (partial legacy testing, not recommended for new deployments) | SPARC64 | Oracle JDK 1.8.x |
IBM AIX 7.2 (partial legacy testing, not recommended for new deployments) | Power ISA | IBM JDK 1.8.x |
HP-UX 11i (Deprecated) (Not supported for JBoss EAP 7.2) | IA64 | HP JVM 1.8.x |
NOTE: For Fuse on JBoss EAP deployments, operating system support aligns with Red Hat JBoss EAP 7 Supported Configurations.
NOTE: For Spring Boot 2 standalone deployments, the HP-UX, AIX, and Solaris operating systems are currently not tested and not supported.
Red Hat Fuse 7.4 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 r2 | Oracle JDBC Driver v12 |
Oracle 12c r2 RAC | Oracle JDBC Driver v12 |
MySQL 5.7 | MySQL Connector/J 5 |
MySQL 8.0 | MySQL Connector/J 8 |
Microsoft SQL Server 2014* | MS SQL Server JDBC Driver 6.0 |
Microsoft SQL Server 2016 | MS SQL Server JDBC Driver 6.0 |
PostgreSQL 9.6* | JDBC 4.2 Postgresql Driver, Version 9 |
PostgreSQL 10.1 | JDBC Postgresql Driver, Version 42.2.5 |
IBM DB2 10.5* | IBM DB2 JDBC Universal Driver Architecture 4.19 |
IBM DB2 11.1 | IBM DB2 JDBC Universal Driver Architecture 4.25 |
NOTE IBM DB2 10.5 is not supported on JBoss EAP.
NOTE Red Hat tests database integrations using the JDBC driver versions shown above. These drivers are compatible with a range of database server versions. See your database vendor’s documentation for information about JDBC driver compatibility with specific server versions.
Supported Messaging Providers
Since Fuse 7.0, only remote brokers are supported.
Broker | Version | Target Containers |
---|---|---|
JBoss A-MQ | 6.3 | Apache Karaf Spring Boot 1.5 JBoss EAP |
AMQ Broker | 7.3.0 | Apache Karaf Spring Boot 1.5 Spring Boot 2.1 JBoss EAP |
AMQ Streams | 1.1.0 | Apache Karaf Spring Boot 1.5 Spring Boot 2.1 JBoss EAP |
Websphere MQ1 | 8.0 | Apache Karaf Spring Boot 1.5 JBoss EAP |
9.0 | Apache Karaf Spring Boot 1.5 JBoss EAP |
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.4.
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 Broker | 7.3.0 | artemis-jms-client |
camel-jms camel-sjms camel-sjms2 |
qpid-jms-client |
camel-amqp |
||
WebSphere MQ | 8.0 | Client v8 | camel-jms (not tested) |
9.0 | Client v9 | JMS API from Java code |
Messaging on the JBoss EAP container is supported using JCA adapters, see JBoss EAP 7.2 Supported Configurations. The following messaging components are supported on JBoss EAP 7.2:
JBoss EAP | |||
---|---|---|---|
Broker | Version | Adapter | Camel components |
JBoss A-MQ | 6.3 | AMQ JCA Adapter v5.11.0 |
camel-activemq |
AMQ | 7.2.x | AMQ JCA Adapter which is integrated in JBoss EAP 7.2 | camel-jms camel-sjms |
WebSphere MQ | 8.0 | Client v8 | camel-jms |
9.0 | Client v9 | camel-jms |
The following messaging components are supported on Spring Boot 1.5 (the messaging clients have not been tested in Spring Boot 2.1):
Spring Boot 1.5 | |||
---|---|---|---|
Broker | Version | Client | Camel components |
JBoss A-MQ | 6.3 | activemq-client
|
camel-activemq |
AMQ | 7.3.0 | artemis-jms-client |
camel-jms camel-sjms camel-sjms2 |
qpid-jms-client |
camel-amqp |
||
WebSphere MQ | 8.0 | Client v8 | camel-jms (not tested) |
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.4 (Apache Karaf, JBoss EAP, and Spring Boot 1.x, respectively).
Supported Security Providers
Red Hat Fuse 7 is tested against Red Hat Single Sign-On (RH SSO). The following RH SSO versions are supported with Fuse 7.4:
Security Provider | Version | Target Containers |
---|---|---|
RH SSO | 7.3.1.GA | Apache Karaf JBoss EAP |
Red Hat Fuse 7.4 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.4 release.
Browser |
---|
Mozilla Firefox |
Google Chrome |
Microsoft Edge |
Red Hat Fuse 7.3
Red Hat Fuse 7.3 on OpenShift
OpenShift Deployment
You must run Fuse on OpenShift on a supported version of OpenShift Container Platform (OCP). The following versions of OCP were tested against Red Hat Fuse 7.3 on OpenShift at the time of the relevant OCP GA release:
OpenShift Product | Versions |
---|---|
OpenShift Container Platform (OCP) |
3.11 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.3 on OpenShift is reliant on the Spring Boot Community version. 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.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.
NOTE: Red Hat Fuse 7.3 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
You must run Red Hat Fuse 7.3 in one of the following JVM versions and on one of the operating systems supported by that JVM.
Java Virtual Machine | Version |
---|---|
OpenJDK | 1.8 |
Oracle JDK | 1.8 |
IBM JDK | 1.8 |
HP JVM | 1.8 |
NOTE: Red Hat limits support of OpenJDK to the Red Hat builds of OpenJDK for Red Hat Enterprise Linux (RHEL) and Windows.
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.2.0 |
Important: Fuse on EAP is not supported in managed domain operating mode. Only standalone server mode is supported.
Fuse without OpenShift on a cloud platform
If you deploy Fuse without OpenShift directly on any cloud platform — for example, MS Azure or Amazon Web Services (AWS) — Red Hat support extends to the Fuse components, but not to the underlying cloud platform. Red Hat does not provide any documentation on installing and configuring Fuse without OpenShift on cloud platforms. Consult your cloud provider's documentation to learn how to configure your application deployments in the cloud.
For more information, see Support Guidelines for Red Hat Middleware Products Deployed in 3rd-party Environments.
Red Hat Fuse 7.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 8 (latest update) | x86_64 | Oracle JDK 1.8.x IBM JDK 1.8.x Red Hat build of OpenJDK 1.8 |
Red Hat Enterprise Linux 7 (latest update) | x86_64 | Oracle JDK 1.8.x IBM JDK 1.8.x Red Hat build of OpenJDK 1.8 |
Microsoft Windows Server 2016 | x86_64 | Oracle JDK 1.8.x |
Oracle Solaris 11 NOTE: (partial legacy testing, not recommended for new deployments) | SPARC64 | Oracle JDK 1.8.x |
IBM AIX 7.2 (partial legacy testing, not recommended for new deployments) | Power ISA | IBM JDK 1.8.x |
HP-UX 11i (Deprecated) (Not supported for JBoss EAP 7.2) | IA64 | HP JVM 1.8.x |
NOTE: For Fuse on JBoss EAP deployments, operating system support aligns with Red Hat JBoss EAP 7 Supported Configurations.
Red Hat Fuse 7.3 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 |
MySQL 8.0 | MySQL Connector/J 8 |
Microsoft SQL Server 2014* | MS SQL Server JDBC Driver 6.0 |
Microsoft SQL Server 2016 | MS SQL Server JDBC Driver 6.0 |
PostgreSQL 9.6* | JDBC 4.2 Postgresql Driver, Version 9 |
PostgreSQL 10.1 | JDBC Postgresql Driver, Version 42.2.5 |
IBM DB2 10.5* | IBM DB2 JDBC Universal Driver Architecture 4.19 |
IBM DB2 11.1 | IBM DB2 JDBC Universal Driver Architecture 4.25 |
NOTE IBM DB2 10.5 is not supported on JBoss EAP.
NOTE Red Hat tests database integrations using the JDBC driver versions shown above. These drivers are compatible with a range of database server versions. See your database vendor’s documentation for information about JDBC driver compatibility with specific server versions.
Supported Messaging Providers
Since Fuse 7.0, only remote brokers are supported.
Broker | Version | Target Containers |
---|---|---|
JBoss A-MQ | 6.3 | Apache Karaf Spring Boot JBoss EAP |
AMQ Broker | 7.2.3 | Apache Karaf Spring Boot JBoss EAP |
AMQ Streams | 1.1.0 | Apache Karaf Spring Boot JBoss EAP |
Websphere MQ1 | 8.0 | Apache Karaf Spring Boot JBoss EAP |
9.0 | Apache Karaf Spring Boot JBoss EAP |
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.3.
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 Broker | 7.2.3 | artemis-jms-client |
camel-jms camel-sjms camel-sjms2 |
qpid-jms-client |
camel-amqp |
||
WebSphere MQ | 8.0 | Client v8 | camel-jms (not tested) |
9.0 | Client v9 | JMS API from Java code |
Messaging on the JBoss EAP container is supported using JCA adapters, see JBoss EAP 7.2 Supported Configurations. The following messaging components are supported on JBoss EAP 7.2:
JBoss EAP | |||
---|---|---|---|
Broker | Version | Adapter | Camel components |
JBoss A-MQ | 6.3 | AMQ JCA Adapter v5.11.0 |
camel-activemq |
AMQ | 7.2.x | AMQ JCA Adapter which is integrated in JBoss EAP 7.2 | camel-jms camel-sjms |
WebSphere MQ | 8.0 | Client v8 | camel-jms |
9.0 | Client v9 | 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.2.3 | artemis-jms-client |
camel-jms camel-sjms camel-sjms2 |
qpid-jms-client |
camel-amqp |
||
WebSphere MQ | 8.0 | Client v8 | camel-jms (not tested) |
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.3 (Apache Karaf, JBoss EAP, and Spring Boot, respectively).
Supported Security Providers
Red Hat Fuse 7 is tested against Red Hat Single Sign-On (RH SSO). The following RH SSO versions are supported with Fuse 7.3:
Security Provider | Version | Target Containers |
---|---|---|
RH SSO | 7.3.1.GA | Apache Karaf JBoss EAP |
Red Hat Fuse 7.3 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.3 release.
Browser |
---|
Mozilla Firefox |
Google Chrome |
Microsoft Edge |
Red Hat Fuse 7.2
Red Hat Fuse 7.2 on OpenShift
OpenShift Deployment
You must run Fuse on OpenShift on a supported version of OpenShift Container Platform (OCP). The following versions of OCP were tested against Red Hat Fuse 7.2 on OpenShift at the time of the relevant OCP GA release:
OpenShift Product | Versions |
---|---|
OpenShift Container Platform (OCP) |
3.11 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.2 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.2 Supported Configurations
Red Hat provides both production and development support for supported configurations according to your subscription agreement in both physical and virtual environments.
NOTE: Red Hat Fuse 7.2 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
You must run Red Hat Fuse 7.2 in one of the following JVM versions and on one of the operating systems supported by that JVM.
Java Virtual Machine | Version |
---|---|
OpenJDK | 1.8 |
Oracle JDK | 1.8 |
IBM JDK | 1.8 |
HP JVM | 1.8 |
NOTE: Red Hat limits support of OpenJDK to the Red Hat builds of OpenJDK for Red Hat Enterprise Linux (RHEL) and Windows.
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.4 |
Important: Fuse on EAP is not supported in managed domain operating mode. Only standalone server mode is supported.
Fuse without OpenShift on a cloud platform
If you deploy Fuse without OpenShift directly on any cloud platform — for example, MS Azure or Amazon Web Services (AWS) — Red Hat support extends to the Fuse components, but not to the underlying cloud platform. Red Hat does not provide any documentation on installing and configuring Fuse without OpenShift on cloud platforms. Consult your cloud provider's documentation to learn how to configure your application deployments in the cloud.
For more information, see Support Guidelines for Red Hat Middleware Products Deployed in 3rd-party Environments.
Red Hat Fuse 7.2 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) | x86_64 | Oracle JDK 1.8.x IBM JDK 1.8.x Red Hat build of OpenJDK 1.8 |
Microsoft Windows Server 2016 | x86_64 | Oracle JDK 1.8.x |
Oracle Solaris 11 NOTE: (partial legacy testing, not recommended for new deployments) | SPARC64 | Oracle JDK 1.8.x |
IBM AIX 7.2 (partial legacy testing, not recommended for new deployments) | Power ISA | IBM JDK 1.8.x |
HP-UX 11i (Deprecated) | IA64 | HP JVM 1.8.x |
NOTE: For Fuse on JBoss EAP deployments, operating system support aligns with Red Hat JBoss EAP 7 Supported Configurations.
Red Hat Fuse 7.2 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.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 Broker | 7.1 and 7.2 | Apache Karaf JBoss EAP Spring Boot |
AMQ Streams | 1.0 | Apache Karaf JBoss EAP Spring Boot |
Websphere MQ1 | 8.0 | Apache Karaf JBoss EAP Spring Boot |
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.2.
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 Broker | 7.1 and 7.2 | artemis-jms-client |
camel-jms camel-sjms camel-sjms2 |
qpid-jms-client |
camel-amqp |
||
WebSphere MQ | 8.0 | Client v8 | camel-jms (not testedI) |
9.0 | Client v9 | JMS API from Java code |
Messaging on the JBoss EAP container is supported using JCA adapters, 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 and 7.2 | AMQ JCA Adapter 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 and 7.2 | artemis-jms-client |
camel-jms camel-sjms camel-sjms2 |
qpid-jms-client |
camel-amqp |
||
WebSphere MQ | 8.0 | Client v8 | camel-jms (not testedI) |
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.2 (Apache Karaf, JBoss EAP, and Spring Boot, respectively).
Red Hat Fuse 7.2 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.2 release.
Browser |
---|
Mozilla Firefox |
Google Chrome |
Microsoft Edge |
Red Hat Fuse 7.1
Red Hat Fuse 7.1 on OpenShift
OpenShift Deployment
You must run Fuse on OpenShift 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.
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
You must run Red Hat Fuse 7.1 in one of the following JVM versions and on one of the operating systems supported by that JVM.
Java Virtual Machine | Version |
---|---|
OpenJDK | 1.8 |
Oracle JDK | 1.8 |
IBM JDK | 1.8 |
HP JVM | 1.8 |
NOTE: Red Hat limits support of OpenJDK to the Red Hat builds of OpenJDK for Red Hat Enterprise Linux (RHEL) and Windows.
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 |
Important: Fuse on EAP is not supported in managed domain operating mode. Only standalone server mode is supported.
Fuse without OpenShift on a cloud platform
If you deploy Fuse without OpenShift directly on any cloud platform — for example, MS Azure or Amazon Web Services (AWS) — Red Hat support extends to the Fuse components, but not to the underlying cloud platform. Red Hat does not provide any documentation on installing and configuring Fuse without OpenShift on cloud platforms. Consult your cloud provider's documentation to learn how to configure your application deployments in the cloud.
For more information, see Support Guidelines for Red Hat Middleware Products Deployed in 3rd-party Environments.
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) | x86_64 | Oracle JDK 1.8.x IBM JDK 1.8.x Red Hat build of OpenJDK 1.8 |
Microsoft Windows Server 2016 | x86_64 | Oracle JDK 1.8.x |
Oracle Solaris 11 NOTE: (partial legacy testing, not recommended for new deployments) | SPARC64 | Oracle JDK 1.8.x |
IBM AIX 7.2 (partial legacy testing, not recommended for new deployments) | 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 MQ1 | 8.0 | Apache Karaf JBoss EAP Spring Boot |
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.1.
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 |
qpid-jms-client |
camel-amqp |
||
WebSphere MQ | 8.0 | Client v8 | camel-jms (not testedI) |
9.0 | Client v9 | JMS API from Java code |
Messaging on the JBoss EAP container is supported using JCA adapters, 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 Adapter 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 |
qpid-jms-client |
camel-amqp |
||
WebSphere MQ | 8.0 | Client v8 | camel-jms (not testedI) |
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.1 (Apache Karaf, JBoss EAP, and Spring Boot, respectively).
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
You must run Fuse on OpenShift 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 |
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.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.
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
You must run Red Hat Fuse in one of the following JVM versions and on one of the operating systems supported by that JVM.
Java Virtual Machine | Version |
---|---|
OpenJDK | 1.8 |
Oracle JDK | 1.8 |
IBM JDK | 1.8 |
HP JVM | 1.8 |
NOTE: Red Hat limits support of OpenJDK to the Red Hat builds of OpenJDK for Red Hat Enterprise Linux (RHEL) and Windows.
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 |
Important: Fuse on EAP is not supported in managed domain operating mode. Only standalone server mode is supported.
Fuse without OpenShift on a cloud platform
If you deploy Fuse without OpenShift directly on any cloud platform — for example, MS Azure or Amazon Web Services (AWS) — Red Hat support extends to the Fuse components, but not to the underlying cloud platform. Red Hat does not provide any documentation on installing and configuring Fuse without OpenShift on cloud platforms. Consult your cloud provider's documentation to learn how to configure your application deployments in the cloud.
For more information, see Support Guidelines for Red Hat Middleware Products Deployed in 3rd-party Environments.
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) | x86_64 | Oracle JDK 1.8.x IBM JDK 1.8.x Red Hat build of OpenJDK 1.8 |
Microsoft Windows Server 2016 | x86_64 | Oracle JDK 1.8.x |
Oracle Solaris 11 NOTE: (partial legacy testing, not recommended for new deployments) | SPARC64 | Oracle JDK 1.8.x |
IBM AIX 7.2 (partial legacy testing, not recommended for new deployments) | 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.
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 |
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 MQ1 | 8.0 | Apache Karaf JBoss EAP Spring Boot |
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 |
qpid-jms-client |
camel-amqp |
||
WebSphere MQ | 8.0 | Client v8 | camel-jms (not testedI) |
9.0 | Client v9 | JMS API from Java code |
Messaging on the JBoss EAP container is supported using JCA adapters, 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 Adapter 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 |
qpid-jms-client |
camel-amqp |
||
WebSphere MQ | 8.0 | Client v8 | camel-jms (not testedI) |
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).
Red Hat Fuse 7.0 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.0 release.
Browser |
---|
Mozilla Firefox |
Google Chrome |
Microsoft Edge |
Red Hat JBoss Fuse 6.3
JBoss Fuse Integration Services for JBoss Fuse 6.3
OpenShift Deployment
You must run Fuse Integration Services (FIS) 2.0 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 3.11 |
OCP 3.11 has been tested against Fuse 6.3 patch R10.
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 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.
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
You must run JBoss Fuse in one of the following JVM versions and on one of the operating systems supported by that JVM.
Java Virtual Machine | Version |
---|---|
OpenJDK | 1.7 (deprecated) 1.8 |
Oracle JDK | 1.7 (deprecated) 1.8 |
IBM JDK | 1.7 1.8 |
HP JVM | 1.7 1.8 |
NOTE: Red Hat limits support of OpenJDK to the Red Hat builds of OpenJDK for Red Hat Enterprise Linux (RHEL) and Windows.
NOTE: Due to recent changes in the security requirements for connecting to the Maven central repository, Oracle JDK 1.7 is no longer compatible with Maven central and is unable to download Maven artifacts. We recommend that you upgrade to Oracle JDK 1.8 to avoid this issue.
Running Fuse on Oracle JDK 1.7 and OpenJDK 1.7 is deprecated, because these JVMs are end of life.
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 |
Important: Although JBoss Fuse 6.3 is currently in Maintenance Support for a Fuse on EAP deployment, the underlying JBoss EAP 6 container is already in the Extended Life Support (ELS) phase. As long as JBoss Fuse 6.3 is in Maintenance Support, however, it is not necessary to purchase a separate ELS subscription for JBoss EAP. For more details, see Red Hat JBoss Middleware Product Update and Support Policy.
Fuse without OpenShift on a cloud platform
If you deploy Fuse without OpenShift directly on any cloud platform — for example, MS Azure or Amazon Web Services (AWS) — Red Hat support extends to the Fuse components, but not to the underlying cloud platform. Red Hat does not provide any documentation on installing and configuring Fuse without OpenShift on cloud platforms. Consult your cloud provider's documentation to learn how to configure your application deployments in the cloud.
For more information, see Support Guidelines for Red Hat Middleware Products Deployed in 3rd-party Environments.
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) | x86_64 | Oracle JDK 1.7.x (deprecated) Oracle JDK 1.8.x IBM JDK 1.7.x IBM JDK 1.8.x Red Hat build of OpenJDK 1.7.x (deprecated) Red Hat build of OpenJDK 1.8 |
Red Hat Enterprise Linux 6 (latest update) | x86 | Oracle JDK 1.7.x (deprecated) Oracle JDK 1.8.x Red Hat build of OpenJDK 1.7.x (deprecated) Red Hat build of OpenJDK 1.8 |
Red Hat Enterprise Linux 6 (latest update) | x86_64 | Oracle JDK 1.7.x (deprecated) Oracle JDK 1.8.x IBM JDK 1.7.x IBM JDK 1.8.x Red Hat build of OpenJDK 1.7.x (deprecated) Red Hat build of OpenJDK 1.8 |
Microsoft Windows Server 2012 R2 | x86_64 | Oracle JDK 1.7.x (deprecated) Oracle JDK 1.8.x |
The following configurations are supported, but not fully tested:
Operating System | Chipset Architecture | Java Virtual Machine |
---|---|---|
Oracle Solaris 10 NOTE: (partial legacy testing, not recommended for new deployments) | x86 x86_64 SPARC64 |
Oracle JDK 1.7.x (deprecated) Oracle JDK 1.8.x |
Oracle Solaris 11 NOTE: (partial legacy testing, not recommended for new deployments) | x86 x86_64 SPARC64 |
Oracle JDK 1.7.x (deprecated) Oracle JDK 1.8.x |
IBM AIX 7.1 (partial legacy testing, not recommended for new deployments) | 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.
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 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 client1 | 7.5.x 8.0.x | Apache Karaf | Remote Broker |
1 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.
Supported SAP Client Integrations
Red Hat's Apache Camel SAP component works with the following JCo client and IDoc client libraries:
Component | SAP Client | Version |
---|---|---|
Camel SAP | JCo | 3.1.2 |
Camel SAP | IDoc | 3.1.0 |
JBoss Fuse 6.3 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 JBoss Fuse 6.3 release.
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 | 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] You must run JBoss Fuse in one of the following JVM versions and on one of the operating systems supported by that JVM.
Java Virtual Machine | Version |
---|---|
OpenJDK | 1.7 (deprecated) 1.8 |
Oracle JDK | 1.7 (deprecated) 1.8 |
IBM JDK | 1.7 1.8 |
HP JVM | 1.7 |
NOTE: Red Hat limits support of OpenJDK to the Red Hat builds of OpenJDK for Red Hat Enterprise Linux (RHEL) and Windows.
Running Fuse on Oracle JDK 1.7 and OpenJDK 1.7 is deprecated, because these JVMs are end of life.
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.
Fuse without OpenShift on a cloud platform
If you deploy Fuse without OpenShift directly on any cloud platform — for example, MS Azure or Amazon Web Services (AWS) — Red Hat support extends to the Fuse components, but not to the underlying cloud platform. Red Hat does not provide any documentation on installing and configuring Fuse without OpenShift on cloud platforms. Consult your cloud provider's documentation to learn how to configure your application deployments in the cloud.
For more information, see Support Guidelines for Red Hat Middleware Products Deployed in 3rd-party Environments.
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) | x86_64 | Oracle JDK 1.7.x (deprecated) Oracle JDK 1.8.x IBM JDK 1.7.x IBM JDK 1.8.x Red Hat build of OpenJDK 1.7.x (deprecated) Red Hat build of OpenJDK 1.8 |
Red Hat Enterprise Linux 6 (latest update) | x86 | Oracle JDK 1.7.x (deprecated) Oracle JDK 1.8.x Red Hat build of OpenJDK 1.7.x (deprecated) Red Hat build of OpenJDK 1.8 |
Red Hat Enterprise Linux 6 (latest update) | x86_64 | Oracle JDK 1.7.x (deprecated) Oracle JDK 1.8.x IBM JDK 1.7.x IBM JDK 1.8.x Red Hat build of OpenJDK 1.7.x (deprecated) Red Hat build of OpenJDK 1.8 |
Red Hat Enterprise Linux 5 (latest update) NOTE: (deprecated) | x86 x86_64 |
Oracle JDK 1.7.x (deprecated) Oracle JDK 1.8.x Red Hat build of OpenJDK 1.7.x (deprecated) |
Microsoft Windows Server 2012 R2 | x86_64 | Oracle JDK 1.7.x (deprecated) Oracle JDK 1.8.x |
Oracle Solaris 10 | x86 x86_64 SPARC64 |
Oracle JDK 1.7.x (deprecated) Oracle JDK 1.8.x |
Oracle Solaris 11 | x86 x86_64 SPARC64 |
Oracle JDK 1.7.x (deprecated) 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.
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.
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
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 | 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
Red Hat provides both production and development support for supported configurations according to your subscription agreement in both physical and virtual environments.[1] You must run JBoss Fuse in one of the following JVM versions and on one of the operating systems supported by that JVM.
Java Virtual Machine | Version |
---|---|
OpenJDK | 1.7 (deprecated) 1.6 (deprecated) |
Oracle JDK | 1.7 (deprecated) 1.6 (deprecated) |
IBM JDK | 1.7 1.6 (deprecated) |
NOTE: Red Hat limits support of OpenJDK to the Red Hat builds of OpenJDK for Red Hat Enterprise Linux (RHEL) and Windows.
Running Fuse on Oracle JDK 1.6, 1.7 and OpenJDK 1.6, 1.7 is deprecated, because these JVMs are end of life.
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.
Fuse without OpenShift on a cloud platform
If you deploy Fuse without OpenShift directly on any cloud platform — for example, MS Azure or Amazon Web Services (AWS) — Red Hat support extends to the Fuse components, but not to the underlying cloud platform. Red Hat does not provide any documentation on installing and configuring Fuse without OpenShift on cloud platforms. Consult your cloud provider's documentation to learn how to configure your application deployments in the cloud.
For more information, see Support Guidelines for Red Hat Middleware Products Deployed in 3rd-party Environments.
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) | x86 x86_64 |
Oracle JDK 1.7.x (deprecated) Oracle JDK 1.6.x (deprecated) IBM JDK 1.7.x IBM JDK 1.6.x (deprecated) Red Hat build of OpenJDK 1.7.x (deprecated) Red Hat build of OpenJDK 1.6.x (deprecated) |
Red Hat Enterprise Linux 5 (latest update) NOTE: (deprecated) | x86 x86_64 |
Oracle JDK 1.7.x (deprecated) Oracle JDK 1.6.x (deprecated) IBM JDK 1.7.x IBM JDK 1.6.x (deprecated) Red Hat build of OpenJDK 1.7.x (deprecated) Red Hat build of OpenJDK 1.6.x (deprecated) |
Microsoft Windows 2008 Server R2 (deprecated) | x86_64 | Oracle JDK 1.7.x (deprecated) Oracle JDK 1.6.x (deprecated) |
Oracle Solaris 10 | x86 x86_64 SPARC64 |
Oracle JDK 1.7.x (deprecated) Oracle JDK 1.6.x (deprecated) |
Oracle Solaris 11 | x86 x86_64 SPARC64 |
Oracle JDK 1.7.x (deprecated) 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.
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.
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
Red Hat provides both production and development support for supported configurations according to your subscription agreement in both physical and virtual environments.[1] 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 | 1.7 (deprecated) 1.6 (deprecated) |
Oracle JDK | 1.7 (deprecated) 1.6 (deprecated) |
IBM JDK | 1.7 1.6 (deprecated) |
NOTE: Red Hat limits support of OpenJDK to the Red Hat builds of OpenJDK for Red Hat Enterprise Linux (RHEL) and Windows.
Running Fuse on Oracle JDK 1.6, 1.7 and OpenJDK 1.6, 1.7 is deprecated, because these JVMs are end of life.
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.
Fuse without OpenShift on a cloud platform
If you deploy Fuse without OpenShift directly on any cloud platform — for example, MS Azure or Amazon Web Services (AWS) — Red Hat support extends to the Fuse components, but not to the underlying cloud platform. Red Hat does not provide any documentation on installing and configuring Fuse without OpenShift on cloud platforms. Consult your cloud provider's documentation to learn how to configure your application deployments in the cloud.
For more information, see Support Guidelines for Red Hat Middleware Products Deployed in 3rd-party Environments.
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) | x86 x86_64 |
Oracle JDK 1.7.x (deprecated) Oracle JDK 1.6.x (deprecated) IBM JDK 1.7.x IBM JDK 1.6.x (deprecated) Red Hat build of OpenJDK 1.7.x (deprecated) Red Hat build of OpenJDK 1.6.x (deprecated) |
Red Hat Enterprise Linux 5 (latest update) NOTE: (deprecated) | x86 x86_64 |
Oracle JDK 1.7.x (deprecated) Oracle JDK 1.6.x (deprecated) IBM JDK 1.7.x IBM JDK 1.6.x (deprecated) Red Hat build of OpenJDK 1.7.x (deprecated) Red Hat build of OpenJDK 1.6.x (deprecated) |
Microsoft Windows 2008 Server R2 (deprecated) | x86_64 | Oracle JDK 1.7.x (deprecated) Oracle JDK 1.6.x (deprecated) |
Oracle Solaris 10 | SPARC64 | Oracle JDK 1.7.x (deprecated) 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: 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 |
NOTE: Red Hat expects that customers will remain on a supported environment. In the event that a JVM, operating system, database, and so on, 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.
NOTE: Red Hat limits support of OpenJDK to the Red Hat builds of OpenJDK for Red Hat Enterprise Linux (RHEL) and Windows.
NOTE: For each supported major version of Red Hat Enterprise Linux (5, 6, 7, or 8), JBoss Fuse is tested against the corresponding latest minor version (5.x, 6.x, 7.x, or 8.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.
NOTE: Solaris Zones are not considered a supported environment, only physical Solaris systems are supported.
Comments