Skip to main content

Software  >  WebSphere  >  WebSphere Message Broker product Line  >  

System Requirements for WebSphere Message Broker V6.1 on Linux for System x (32-bit)

 Product documentation
 
Abstract
This document contains system requirements for the WebSphere Broker V6.1 products on Linux for System x (32-bit).
 
 
Content
The Toolkit, Configuration Manager, User Name Server and Broker requirements on Linux for System x (32-bit) are documented below.

Toolkit Requirements:

Please read first
  • WebSphere Message Broker, WebSphere MQ Integrator, and Integrator Broker product READMEs
  • 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.
  • 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.
Hardware Requirements
  • IBM eServer System x or equivalent Intel based system (Minimum requirement: Intel Pentium III, 700 MHz or higher, 512 MB RAM. A minimum display resolution of 1024 x 768 is recommended.
Operating Systems
  • Red Hat Enterprise Linux (RHEL) V4.0 (plus Update 2) or later
  • SUSE Linux Enterprise Server (SLES) 9
  • Requires Mozilla Version 1.4.2 or later


Configuration Manager, User Name Server and Broker Requirements:

Please read first
  • Please note the above "Toolkit Requirements: Please read first section" as that is also applicable here.
  • The Message Broker supports any JMS 1.1 provider. The minimum embedded JRE is Java™ 1.5. Both of these factors need to be considered when selecting a JMS provider whose client will be embedded in Message Broker.
Hardware Requirements
  • IBM eServer System x or equivalent Intel based system from various manufacturers
Operating Systems
  • Red Hat Enterprise Linux AS 4.0 (plus Update 2) or later
  • Red Hat Enterprise Linux (RHEL) V5.0 to V5.3 [see section note 1]
  • SUSE Linux Enterprise Server (SLES) 9
  • SUSE Linux Enterprise Server (SLES) 10

Notes:
  1. Red Hat Enterprise Linux (RHEL) V5.3 requires a minimum level of WMB V6.1.0.4.
Databases
(required for the broker component only)
Brokers can access Information Integrator data sources, for user data, on WebSphere Information Integrator for Linux, UNIX, and Windows V8.2.
Brokers can access, via JDBC only, Information Integrator data sources for user data on WebSphere Information Integrator Classic Federation (IICF) for z/OS, where the WebSphere IICF client code is provided for the Message Broker platform.

Notes:
  1. Oracle Database Server requires the Oracle Runtime Client.
  2. JDBC Type-4 transaction support using DB2 requires a minimum level of DB2 v9.1 Fix Pack 3 or later. Support on DB2 v8 is not available.
  3. Only the connect-time failover feature of Oracle RAC in non-XA environments is supported. Oracle RAC is supported in XA environments for Oracle 10gR2 10.2.0.4 or above, with WebSphere Message Broker V6.1.0.4. Please note that this is only supported for 32 bit execution groups for this platform.
  4. Automatic Client Reroute for DB2 is supported.
  5. Informix support only for user databases. Large objects (LOBs) are not supported. Stored procedures are supported with WebSphere Message Broker V6.1.0.4 and Informix Client SDK V3.50 with UC4 Fix Pack.
  6. Globally coordinated transaction support (‘XA’) is provided.
  7. IBM DB2 Database Server - System i support (non-XA only).
    a. Brokers can access DB2 Databases, for user data, on System i servers running OS/400 V5R2, V5R3 or V5R4 via DB2 Connect.

    b. This support is subject to the following restrictions:


      i. The broker database may not reside on the System i server.

      ii. Globally coordinated ('XA') transactions are not supported.

      iii. Database stored procedures on the System i server may be called, when using DB2 Connect, but not with System i Access for Windows.

      iv. Message flows containing Rules and Formatter Extension nodes may not access System i databases.

IBM DB2 Database Server - System z support:

    a. Brokers can access DB2 Databases, for user data, on System z servers via DB2 Connect. Supported versions of DB2 can be found here.

    b. This support is subject to the following restrictions:
      i. The broker database may not reside on the System z server.

      ii. Message flows containing Rules and Formatter Extension nodes may not access System z databases.
WebSphere MQ
Notes:
  1. WebSphere MQ V6.0.1.0 or later is required for globally coordinated transaction support (‘XA’).
  2. WebSphere Message Broker V6.1.0.3 or later is required.
Supported AdaptersFor specific enterprise information system (EIS) product versions supported by the v6.1 WebSphere Adapters embedded in WebSphere Message Broker please refer to the software requirements page at: Supported software for IBM WebSphere Adapters and IBM WebSphere Business Integration Adapters
  • SAP (RHEL AS 4.0, RHEL 5.0, SLES 9 and SLES 10)
  • PeopleSoft (RHEL AS 4.0 and SLES 9)
Rules and Formatter ExtensionPlease refer to the Rules and Formatter Extension installation readme for a list of supported databases.



Change History
  • 20 November 2007: Added note 12.
  • 3 December 2007: Added Supported Adapters and note 13.
  • 10 December 2007: Removed Supported Adapters from the toolkit section.
  • 7 March 2008: Added Automatic Client Reroute for DB2 is supported.
  • 11 March 2008: Added virtualization note.
  • 29 May 2009: New format released (WMB 6.1.0.2 information is also included).
  • 1 July 2008: Replaced note 3 in the Databases section.
  • 27 November 2008: General update in support of the WMB 6.1.0.3 release.
  • 4 March 2009: Clarified RHEL V5 version support.
  • 11th June 2009: Added support for stored procedures on IDS and Oracle RAC in XA environment.
  • 18th September 2009: Added support for Red Hat Enterprise Linux (RHEL) V5.3.
 
Related information
WebSphere Broker detailed system requirements
 
 
 

Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Rate this page
Please take a moment to complete this form to help us better serve you.
This material provides me with the information I need.




This material is clear and easy to understand.




Did the information help you to achieve your goal?
What updates, improvements, or related information would you like to see in this document?
Your response will be used to improve our document content. Requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site.
Input the verification number to submit feedback:
Document information
 Product categories:
 Software
 Business Integration and Optimization
 Application Integration and Connectivity
 WebSphere Message Broker
 Documentation
 Operating system(s):
  Linux
 Software version:
  6.1
 Reference #:
  7010516
 IBM Group:
 Software Group
 Modified date:
 2007-10-25

Translate My Page
 
 

Rate this page

Help us improve this page. Your response will be used to improve our document content. Requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site.