This article explains supported configurations for Fuse Service Works.
Every JBoss® Fuse Service Works (JBoss FSW) 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.
In order to be running in a supported configuration, FSW must be running in one of the following Technology Component Kit (TCK) certified implementations and on one of the operating systems supported by that implementation. Red Hat relies on the TCK to validate platform compatibility.
|Java Virtual Machine||Version|
|IBM JDK||1.7 |
Red Hat has performed the full range of platform tests on the following tested configurations.
|Operating system||Chip architecture||Java Virtual Machine|
|Red Hat Enterprise Linux® 6 (latest update)||x86, x86_64||
Oracle JDK 1.7
IBM JDK 1.7
|Microsoft Windows 2008||x86_64||Oracle JDK 1.7|
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 FSW 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 validated and certified as part of the JBoss Fuse Service Works release process for use as a persistence store for platform components. A persistence store is used by product components to store state or other run time information. Product components include JMS messaging, jBPM, Riftsaw/BPEL Engine, DTGov and RTGov.
|Oracle 11g R2||Oracle JDBC Driver v22.214.171.124.0|
|IBM DB2 9.7||IBM DB2 JDBC Universal Driver Architecture 4.9.78|
|Microsoft SQL Server 2008||Microsoft SQL Server JDBC Driver 3.0|
|Microsoft SQL Server 2012||Microsoft SQL Server JDBC Driver 4.0|
|MySQL v5.5||mysql-connector-java v5.1.13|
|PostgreSQL 9.2||JDBC4 Postgresql Driver, Version 9.2.1002|
The following JMS providers are supported:
|HornetQ||As packaged in JBoss Enterprise Application Platform|
|TIBCO Enterprise Message Service||6.0|
|IBM WebSphereMQ||6.0.2, 7.0|
A JBoss FSW subscription includes full entitlements to JBoss Fuse and JBoss EAP. Customers may allocate subscription core count to deployments of either technology.
Note that the initial release of JBoss FSW does not include support when EAP is used in domain mode and the use of human tasks with jBPM is only supported with a subscription to JBoss BPM Suite
 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.
 Red Hat limits support of OpenJDK to Red Hat Enterprise Linux.
 When using IBM and jbpm customers may encounter a known issue ( https://bugzilla.redhat.com/show_bug.cgi?id=1070728 ).
For more information on JBoss Enterprise Middleware, contact your Red Hat account manager.