System Requirements for WebSphere Business Integration Message Broker, Message Broker with Rules and Formatter Extension, and Event Broker V5.0 for Linux on Intel

Operating Systems		Red Hat Enterprise Linux AS 3.0. See additional notes for supported environment Red Hat Enterprise Linux AS 2.1 (formerly known as Red Hat Advanced Server V2.1) SuSE Linux Enterprise Server (SLES) 8 SuSE Linux Enterprise Server (SLES) 9. See additional notes for supported environment. United Linux 1.0 (plus SP2a)
Hardware Requirements		Linux Intel: IBM® xSeries® or equivalent Intel based system
Java™		Java Runtime Environment 1.3.1 (embedded within the product) Java Runtime Environment 1.4 (for Red Hat Enterprise Linux AS 3.0 and SLES 9)
Databases		IBM DB2® Enterprise Edition, V7.2 (plus Fix Pack 9) IBM DB2 Enterprise Server Edition, V8.1 (plus Fix Pack 2) or V8.2 Oracle 9i Release 2 Oracle 10g Release 1 (see note 8) Oracle 10g Release 2 (see notes 8 and 9)
WebSphere MQ		IBM WebSphere MQ for Linux (Intel) V5.3 (plus CSD 4) IBM WebSphere MQ Linux on x86 platform V6.0.1 or above

Notes:

1. Only the Broker is supported on this operating system. The Configuration Manager and Broker Toolkit are not supported on Linux on Intel.
2. The WebSphere MQ Real-time Transport is not currently supported with JRE 1.4
3. Coordinated transactional support:
   • On WebSphere MQ V5.3, coordinated transactional support is available for all supported databases, except Sybase ASE.
   • On WebSphere MQ V6.0, coordinated transactional support is only available on DB2. You should be running on WebSphere Business Integration Brokers V5 Fix Pack 06 or above. The switch load file will need to be built using the samples provided with MQ V6.0, as described in the MQ documentation.
   • A minimum maintenance level of FixPak 3 is recommended for DB2 v8.1 for coordinated transactional support.
4. DB2 Database Server - iSeries® Support:
   • Brokers can access DB2 Databases, for user data, on iSeries servers running OS/400® V5R1 (PTFs SI03013 and SI04047 required) or V5R2. This can be done using either DB2 Connect (on UNIX® and Windows®) or iSeries Access for Windows (OS/400 V5R1 requires PTF SI05361 and V5R2 requires PTF SI05854).
   • Support for accessing DB2 Databases on iSeries servers is subject to the following restrictions:
     • The broker database may not reside on the iSeries server.
     • Globally coordinated ('XA') transactions are not supported.
     • Database stored procedures on the iSeries server may be called when using DB2 Connect or iSeries Access for Windows V5R2.
     • Message flows containing New Era of Networks nodes may not access iSeries databases.
5. DB2 Database Server - zSeries® Support:
   • Brokers can access DB2 Databases, for user data, on zSeries servers running the versions of operating system and DB2 listed below. This can be done using DB2 Connect on UNIX and Windows.
   • Support for accessing DB2 Databases on zSeries servers is subject to the following restrictions:
     • Large Database Objects (LOBs) support requires DB2 Connect V8.1 FixPak 4 and DB2 Universal Database for z/OS® 7.1 at RSU0310.
     • The broker database may not reside on the zSeries server.
     • Message flows containing New Era of Networks nodes may not access zSeries databases.
6. Red Hat EL AS 3.0 and SLES 9 additional notes
   • The minimum supported combination is WebSphere Business Integration Brokers V5.0 FixPak 3 + WebSphere MQ V5.3 CSD 6 + JRE 1.4.x + DB2 ESE v8.1 FixPak 5 (or DB2 v8.2). To install WebSphere Business Integration Brokers v5.0, use the command line option "-is:javahome" to point to JRE 1.4.x. For example, "setuplinux -is:javahome /opt/IBMJava2-142". Likewise for uninstall.
   • After installation, backup the product supplied JRE in /opt/mqsi/jre and replace this directory with a soft link to the JRE 1.4.x installation. For example, "ln -s /opt/IBMJava2-142/jre /opt/mqsi/jre".
   • IBM Java 1.4.x may be downloaded from the IBM Developer Kits download page.
   • The SCADA input and output Nodes are not supported
7. Where patches for a product are specified, this means that these patches were required to resolve problems found during testing and should therefore be considered as the minimum necessary maintenance level. Further maintenance should be applied in accordance with the guidance of the relevant software manufacturer.
8. Oracle 9iR2, 10gR1 and 10gR2 are only supported with WebSphere Business Integration Message Broker Fix Pack 8 or later. The DataDirect V5.0 drivers must be used.
9. Oracle 10GR2 is only supported with Red Hat Enterprise Linux AS 3.0.

• 1 September 2005: Moved information from static page and redirected to this document.
• 6 September 2005: Added support for SLES 9.
• 7 September 2005: Added note about Real-Time Transport support with JRE 1.4
• 24 October 2005: Corrected "-is:javahome" statements.
• 5 December 2005: Added support for WebSphere MQ V6.
• 20 December 2005: Added note 7.
• 22 June 2006: Modified note 6.
• 6 July 2006: Added support for Oracle 10GR1.
• 20 October 2006: Added Oracle 10GR2 support with Red Hat Enterprise Linux AS 3.0 (also note 9).
• 2 August 2007: Added 10gR2 to note 8.