System requirements for WebSphere Message Broker V6.0 on Linux for System p and WebSphere Event Broker V6.0 on Linux for System p

Product documentation


Abstract

This document contains system requirements for the WebSphere Broker V6 products on Linux for System p.

Content


The Configuration Manager and Broker requirements on Linux for System p platform are documented below.


Configuration Manager Requirements:

Operating Systems
  • Linux PowerPC Red Hat Enterprise Linux 4.0 (plus Update 2 or later)
  • Linux PowerPC Red Hat Enterprise Linux 5.0 to 5.2
  • Linux PowerPC SUSE Linux Enterprise Server (SLES) 9 (RC5 or above, with kernel 2.6.5-7.244 or above)
  • Linux PowerPC SUSE Linux Enterprise Server (SLES) 10 (or later)
Hardware Requirements
  • 64-bit iSeries and pSeries IBM POWER processor-based systems only, capable of running the required level of a compatible operating system with enough storage to meet the requirements of WebSphere Message Broker.
WebSphere MQ
  • IBM WebSphere MQ for POWER platform, V6.0
  • IBM WebSphere MQ for POWER platform, V7.0 [see note 12]
  • IBM WebSphere MQ for POWER platform, V7.0.1 [see note 12]


Broker Requirements:

Operating Systems
  • Linux PowerPC Red Hat Enterprise Linux 4.0 (plus Update 2 or later)
  • Linux PowerPC Red Hat Enterprise Linux 5.0 to 5.2
  • Linux PowerPC SUSE Linux Enterprise Server (SLES) 9 (RC5 or above, with kernel 2.6.5-7.244 or above)
  • Linux PowerPC SUSE Linux Enterprise Server (SLES) 10 (or later)
Hardware Requirements
  • 64-bit iSeries and pSeries IBM POWER processor-based systems only, capable of running the required level of a compatible operating system with enough storage to meet the requirements of WebSphere Message Broker.
Databases
  • IBM DB2 Universal Database Enterprise Server Edition, V8.2 and other IBM DB2 Universal Database V8.2 editions for production purposes
  • IBM DB2 Universal Database V9.1
  • IBM DB2 V9.5 for Linux, UNIX, and Windows [see note 12]
WebSphere MQ
  • IBM WebSphere MQ for POWER platform, V6.0
  • IBM WebSphere MQ for POWER platform, V7.0 [see note 12]
  • IBM WebSphere MQ for POWER platform, V7.0.1 [see note 12]

Notes:

  1. Globally coordinated transaction support (‘XA’) is provided only with DB2.
  2. 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.
  3. 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.
  4. Brokers can access Information Integrator databases, for user data, on WebSphere Information Integrator for Linux, UNIX, and Windows V8.2.
  5. 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.
  6. The specified WebSphere MQ level is the minimum level however certain functionality will require a higher level:
    • JMS Real-time Multicast PGM support – requires WebSphere MQ V6.0.1.0
  7. Rational Agent Controller V5.0.2.1 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 5.0.2.1.
  8. 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.
  9. 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.
  10. Automatic Client Reroute for DB2 is supported.
  11. 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.
  12. WebSphere Message Broker V6.0.0.9 or later is required.



Change History
  • 31 March 2006: First release.
  • 19 April 2006: Minor text change.
  • 22 June 2006: Added note 8.
  • 7 July 2006: Amended note 3 to include "or IBM DB2 Universal Database V8.1 (5625-DB2).
  • 10 July 2006: Removed "WebSphere Message Broker with Rules and Formatter Extension V6.0 for Linux on POWER platform" from the title.
  • 19 September 2006: Clarified note 1.
  • 30 September 2006: Removed AS from the Red Hat statements and added "or later" to the updates clarification.
  • 01 February 2007: Added support for Linux PowerPC SUSE Linux Enterprise Server (SLES) 10 (or later).
  • 7 February 2007: Added support for IBM DB2 Universal Database V9.1 (JDBC/XA not supported).
  • 25 May 2007: Removed (JDBC/XA not supported) [see note 9] and removed note 9.
  • 3 July 2007: Removed of in first line of Hardware Requirements.
  • 21 September 2007: Added note 5.
  • 15 February 2008: Added support for Linux PowerPC Red Hat Enterprise Linux 5.
  • 27 February 2008: Added Automatic Client Reroute for DB2 is supported.
  • 29 February 2008: Revamped hardware section.
  • 11 March 2008: Added virtualization note.
  • 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 POWER platform, V7.0.
  • 20 January 2010: Added support for IBM WebSphere MQ for POWER platform, V7.0.1.

Related information

WebSphere Brokers detailed system requirements
Recommended Fixes

Cross reference information
Segment Product Component Platform Version Edition
Business Integration WebSphere Event Broker Documentation Linux 6.0

Product Alias/Synonym

WMB WEB WMB with RFE

Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Message Broker
Documentation

Software version:

6.0

Operating system(s):

Linux

Reference #:

7007484

Modified date:

2007-07-03

Translate my page

Machine Translation

Content navigation