This document contains system requirements for the WebSphere Broker V6 products on Linux for System x.
Configuration Manager Requirements:
- Globally coordinated transaction support (‘XA’) is provided only with DB2 and Oracle.
- Linux Intel Red Hat Enterprise Linux 4.0 requires IBM WebSphere MQ V6.0.
- IBM DB2 Database Server - iSeries support:
- Brokers can access DB2 Databases, for user data, on iSeries servers running OS/400 V5R2 or V5R3. This can be done using either DB2 Connect (on UNIX and Windows) or, on Windows platforms only, iSeries Access for Windows.
- This support 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, but not with iSeries Access for Windows.
- Message flows containing New Era of Networks nodes may not access iSeries databases.
- IBM DB2 Database Server - zSeries support:
- Brokers can access DB2 Databases, for user data, on zSeries servers running z/OS with IBM DB2 Universal Database V7.1 (5675-DB2) at RSU0409 and PUT0402 or later or IBM DB2 Universal Database V8.1 (5625-DB2). This can be done using DB2 Connect on UNIX and Windows.
- This support is subject to the following restrictions:
- The broker database may not reside on the zSeries server.
- Large database Objects (LOBs) are supported; this support requires DB2 Universal Database for z/OS 7.1, at RSU0409 or later.
- Message flows containing New Era of Networks nodes may not access zSeries databases.
- Brokers can access Information Integrator databases, for user data, on WebSphere Information Integrator for Linux, UNIX, and Windows V8.2.
- Brokers can access Information Integrator data sources for user data on WebSphere Information Integrator Classic Federation for z/OS where the WebSphere Information Integrator Classic Federation client code is provided for the Message Broker platform.
- The specified WebSphere MQ level is the minimum level however certain functionality will require a higher level:
- JMS Real-time support requires WebSphere MQ V5.3 Fix Pack 10.
- Support for JMS MQ Optimized node requires WebSphere MQ V5.3 Fix Pack 10.
- JMS Real-time Multicast PGM support – requires WebSphere MQ V22.214.171.124
- Support for JMS MQ Optimized node requires WebSphere MQ V5.3 Fix Pack 10
- Benefit from NPTL performance gains requires WebSphere MQ V6
- Support for JMS SSL requires WebSphere MQ V5.3 Fix Pack 11
- Rational Agent Controller V126.96.36.199 or V6.0.1 is required to support Broker v6 debugging. If you are also debugging v5 brokers on a v6 system, you must use RAC 188.8.131.52.
- 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.
- The Message Broker supports any JMS 1.1 provider. The embedded JRE is Java 1.4.2. Both of these factors need to be considered when selecting a JMS provider whose client will be embedded in Message Broker.
- Linux x86 (64-bit) Red Hat Enterprise Linux 4.0 and 5.0 notes:
- The Message Broker is a 32-bit application and therefore requires 32-bit C and C++ runtime libraries.
- Both DB2 and Oracle are supported.
- If you are using DB2 v8 Fix Pack 9, you must use a 32-bit instance. With later DB2 Fix Packs, both 32-bit and 64-bit instances can be used.
- For Oracle, the 32-bit Oracle client libraries must be used.
- Only V6.0 of IBM WebSphere MQ for Linux on x86 is supported on this platform.
- XA is supported only if the customer uses the x86 (32-bit) offering of IBM WebSphere MQ v6.0. The customer may use the x86_64 (64-bit) offering of WebSphere MQ v6.0 if XA is not required. The reason for this is that a 64-bit queue manager requires 64-bit ODBC drivers and switchload files, which are not provided.
- Oracle Database Server requires the Oracle Runtime Client.
- WebSphere MQ v5.3 End of Support Date is 28th September, 2007. Customers should upgrade to WebSphere MQ v6.0.
- Only the connect-time failover feature of Oracle RAC in non-XA environments is supported.
- Automatic Client Reroute for DB2 is supported.
- Defect support is available for virtualization environments where they relate to releases of this platform already supported by WebSphere Message Broker. Unless stated elsewhere in the system requirements, WebSphere Message Broker has not been specifically tested in virtualization environments. WebSphere Message Broker Support is therefore unable to assist in issues related to configuration and setup, or issues that are directly related to the virtualization environment itself.
- WebSphere Message Broker V184.108.40.206 or later is required.
- DataDirect V5.3 ODBC Drivers are required.
- 20 December 2005: Added note 6.
- 9 January 2006: Minor clarification.
- 31 March 2006: Added support for Informix Dynamic Server V9.40, Microsoft SQL Server 2000 and Linux Intel (32-bit) Red Hat Enterprise Linux AS 4.0. Added additional notes.
- 24 April 2006: Clarified that we support Oracle 10g Release 1.
- 22 June 2006: Added note 9.
- 5 July 2006: Added Linux x86 (64-bit) Red Hat Enterprise Linux AS 4.0 (plus Update 2) - supported on version 220.127.116.11 or later and note 10.
- 7 July 2006: Amended note 4 to include "or IBM DB2 Universal Database V8.1 (5625-DB2)."
- 21 July 2006: Added "The Message Broker....." comment to note 10.
- 24 July 2006: Removed the "Oracle" reference from note 10.
- 31 July 2006: Added the "If you are using DB2 v8 Fix Pack 9....." comment to the first point of note 10.
- 6 September 2006: Added Oracle 10G Release 2 support.
- 22 September 2006:Removed non-XA comments from DB list since the XA support statements is explicit in Note 1.
- 30 September 2006: Removed AS from the Red Hat statements and added "or later" to the updates clarification.
- 2 October 2006: Corrected the first Red Hat statement as per the previous change.
- 6 December 2006: In the Broker database section, changed 'UC4' to 'UC3'.
- 25 January 2007: Added note 11 "Oracle Database Server requires the Oracle Runtime Client."
- 01 February 2007: Added support for SUSE Linux Enterprise Server (SLES) 10 or later.
- 7 February 2007: Added support for IBM DB2 Universal Database V9.1 (JDBC/XA not supported).
- 13 February 2007: Removed (zSeries) and (zSeries) from WebSphere MQ.
- 11 April 2007: Added Linux Intel (64-bit) SUSE Linux Enterprise Server (SLES) 9 or later - supported on version 18.104.22.168
- 25 May 2007: Removed (JDBC/XA not supported) [see note 12] and removed note 12.
- 12 July 2007: Added 64-bit in hardware and changed IBM DB2 in Databases.
- 27 July 2007: Added Linux Intel (64-bit) SUSE Linux Enterprise Server (SLES) 10 - supported on version 22.214.171.124.
- 11 September 2007: Added support for Red Hat Enterprise Linux v 5.0.
- 21 September 2007: Added note 6.
- 6 November 2007. Added notes 13 and 14.
- 27 February 2008: Added Automatic Client Reroute for DB2 is supported.
- 11 March 2008: Added virtualization note.
- 20 May 2008: Added or later Fix Packs in WebSphere MQ.
- 1 July 2008: Replaced Note 14.
- 4 March 2009: Clarified RHEL V5 version support.
- 10 July 2009: Added support for DB2 9.5.
- 15 July 2009: Added support for IBM WebSphere MQ for Linux, V7.0 and Microsoft SQL Server 2005.
- 10 August 2009: Added support for Oracle 11g Release 1.
- 3 September 2009: Added support for Sybase Adaptive Server Enterprise (ASE) V15.0.
- 20 January 2010: Added support for IBM WebSphere MQ for Linux, V7.0.1.
Original publication date
|Business Integration||WebSphere Event Broker||Documentation||Linux||6.0|
|Business Integration||WebSphere Message Broker with Rules and Formatter Extension||Workbench - General||Linux||6.0|
WMB WEB WMB with RFE