Every Red Hat JBoss® Fuse (JBoss Fuse) release is tested and supported on a variety of market-leading operating systems, Java™ Virtual Machines (JVMs), and database combinations. Red Hat provides both production and development support for supported configurations and tested integrations according to your subscription agreement in both physical and virtual environments.[1]
Supported Configurations
Red Hat provides both production and development support for supported configurations according to your subscription agreement in both physical and virtual environments.[1] In order to be running in a supported configuration, JBoss Fuse must be running in one of the following JVM versions and on one of the operating systems supported by that JVM.
| Java Virtual Machine | Version |
|---|---|
| OpenJDK [2] | 1.6 1.7 |
| Oracle JDK | 1.6 1.7 |
| IBM JDK | 1.6 1.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 6 (latest update) | x86 x86_64 |
Oracle JDK 1.6.x Oracle JDK 1.7.x IBM JDK 1.6.x IBM JDK 1.7.x OpenJDK 1.6.x OpenJDK 1.7.x |
| Red Hat Enterprise Linux 5 (latest update) | x86 x86_64 |
Oracle JDK 1.6.x Oracle JDK 1.7.x IBM JDK 1.6.x IBM JDK 1.7.x OpenJDK 1.6.x |
| Microsoft Windows 2008 Server R2 | x86_64 | Oracle JDK 1.6.x Oracle JDK 1.7.x |
| Oracle Solaris 10 | x86 x86_64 SPARC64 |
Oracle JDK 1.6.x Oracle JDK 1.7.x |
| Oracle Solaris 11 | x86 x86_64 SPARC64 |
Oracle JDK 1.6.x Oracle JDK 1.7.x |
| IBM AIX 7.1 | pSeries | IBM JDK 1.6.x IBM JDK 1.7.x |
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 |
Supported Browsers for use with the hawit.io console
| Browser | Version |
|---|---|
| Microsoft IE | 10, 11 |
| Chrome | 31 |
| Firefox | 27 |
JBoss Fuse Container Interoperability
Certain components of the JBoss Fuse distribution are supported on other JBoss containers. Components that are supported on other containers are provided in the "/extras" directory of the JBoss Fuse distribution for your convenience. Note: For these configurations to be supported a subscription to JBoss Fuse and a supported container is required.
| Fuse Component | Version | JBoss Container | Version |
|---|---|---|---|
| Camel | 2.10.0.redhat-60024 | EAP | 6.1.1 |
| Camel | 2.12.0.redhat-610379 | EAP | 6.2 and newer |
| Camel | 2.10.0.redhat-60024 | EWS | 2.0.1 |
[1] Red Hat expects that customers will remain on a supported environment. In the event that a JVM, operating system, database, etc., or its version is no longer supported by its vendor, Red Hat may be limited in its ability to provide support and may require you to reproduce the issue in a supported environment for continued assistance.
[2] Red Hat limits support of OpenJDK to Red Hat Enterprise Linux.
For a list of changes to this document follow this link.