System Requirements for WebSphere Message Broker V6.1 for Windows

Product documentation


Abstract

This document contains system requirements for the WebSphere Broker V6.1 products on Windows.

Content

The Toolkit, Configuration Manager, User Name Server and Broker requirements for Windows 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
  • Windows x86 technology-compatible PC hardware, capable of running the required level of a compatible operating system with enough storage to meet the requirements of the WebSphere Message Broker Toolkit
Operating Systems
  • Microsoft Windows XP Professional with SP2
  • Microsoft Windows XP Professional with SP2 x64 Edition [see section note 1]
  • Windows Server 2003 Standard and Enterprise Edition
  • Windows Server 2003 Standard and Enterprise x64 Edition [see section note 1]
  • Windows Server 2003 R2 Standard and Enterprise Edition
  • Windows Server 2003 R2 Standard and Enterprise x64 Edition [see section note 1]
  • Microsoft Windows Server 2008 (Standard or Enterprise 32-bit and 64-bit Edition) [see section note 1]
  • Microsoft Windows Vista (Business, Enterprise or Ultimate Edition) [see section note 1]
  • Microsoft Windows Vista (64-bit versions of Business, Enterprise or Ultimate Edition) [see section note 1]
  • Microsoft Windows 7 (32 bit versions of Professional, Enterprise or Ultimate Edition) [see section note 2]
  • Microsoft Windows 7 (64 bit versions of Professional, Enterprise or Ultimate Edition) [see section note 2]

Note:
  1. WebSphere Message Broker v6.1.0.3 or later is required.
  2. WebSphere Message Broker Toolkit v6.1.0.9 or later is required. English only.


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
  • Windows x86 technology-compatible PC hardware, capable of running the required level of a compatible operating system with enough storage to meet the combined requirements of WebSphere Message Broker and all prerequisite products
Operating Systems
  • Microsoft Windows XP Professional with SP2
  • Microsoft Windows XP Professional with SP2 x64 Edition [see section note 1]
  • Windows Server 2003 Standard and Enterprise Edition
  • Windows Server 2003 Standard and Enterprise x64 Edition [see section note 1]
  • Windows Server 2003 R2 Standard and Enterprise Edition
  • Windows Server 2003 R2 Standard and Enterprise x64 Edition [see section note 1]
  • Microsoft Windows Server 2008 (Standard or Enterprise 32-bit and 64-bit Edition) [see section note 1]
  • Microsoft Windows Vista (Business, Enterprise or Ultimate Edition) [see section note 1]
  • Microsoft Windows Vista (64-bit versions of Business, Enterprise or Ultimate Edition) [see section note 1]

Note:
  1. WebSphere Message Broker v6.1.0.3 or later is required.
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 9.1 Fix Pack 3 or later. Support on DB2 8 is not available.
  3. Only the connect-time failover feature,using a list of alternate servers, of Oracle RAC in non-XA environments is supported. The connect-time failover feature,using a list of alternate servers, of Oracle RAC is also supported in ODBC XA environments for supported Oracle versions from 10.2.0.4 and above, with WebSphere Message Broker V6.1.0.6 or later. Please note that this is only supported for 64 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 TC4 Fix Pack.
  6. Globally coordinated transaction support (‘XA’) is provided.
  7. A minimum level of DB2 9.1 FP3 is required for Windows Vista and 2008 platforms.
  8. WMB V6.1.0.5 or later is required.
  9. WMB V6.1.0.8 or later is required.
  10. 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 either DB2 Connect or System i Access for Windows.

    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. APAR IC57915 must be applied.
  3. WebSphere Message Broker V6.1.0.3 or later is required.
  4. WebSphere Message Broker V6.1.0.5 or later is required.
Supported Adapters For 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 (Microsoft Windows Server 2003 Standard Edition and Enterprise Edition)
  • Siebel (Microsoft Windows Server 2003 Standard Edition and Enterprise Edition and Windows XP Professional)
  • PeopleSoft (Microsoft Windows Server 2003 Standard Edition and Enterprise Edition)
Connectivity
  • WebSphere Message Broker 6.1 supports the command console and Toolkit being published via Citrix Presentation Server 4.0 and 4.5 on Microsoft Windows Server 2003 Standard and Enterprise Editions.
Rules and Formatter Extension Please refer to the Rules and Formatter Extension installation readme for a list of supported databases.
WebSphere Service Registry and Repository
Notes:
  1. Support is provided when using 6.1 compatibility URLs.
    Documentation for the "compatibility URLs" mentioned can be found at: WebSphere Service Registry and Repository - Web service interface URLs


Change History
  • 12 October 2007: Initial release date November.
  • 20 November 2007: Added note 13 and changed Hardware Requirements.
  • 3 December 2007: Added Supported Adapters section and note 14.
  • 10 December 2007: Removed Supported Adapters and changed Hardware Requirements from the toolkit section.
  • 7 March 2008: Added Automatic Client Reroute for DB2 is supported.
  • 11 March 2008: Added virtualization note.
  • 29 May 2008: New format released (WebSphere Message Broker 6.1.0.2 information is also included).
  • 1 July 2008: Replaced note 3 in Databases section.
  • 1 September 2008: Added support for Informix Dynamic Server V10.00.
  • 27 November 2008: General update in support of the WebSphere Message Broker 6.1.0.3 release.
  • 6 April 2009: Added 'XA' support to DB2 9.5.
  • 11th June 2009: Added support for stored procedures on IDS and Oracle RAC in XA environment.
  • 17th December 2009: Added support for Microsoft SQL Server 2008.
  • 20th January 2010: Added support for IBM WebSphere MQ for Windows, V7.0.1.
  • 7th April 2010: Added support for IBM DB2 9.7.
  • 29th September 2010: Added support for Oracle 11g Release 2.
  • 16th January 2012: Added support for Windows 7 for Toolkit v6.1.0.9.
  • 12th March 2012: Oracle RAC support clarification
  • 8th May 2012: Added support for WSRR 7.5

Related information

WebSphere Broker detailed system requirements

Product Alias/Synonym

WMB WEB WMB with RFE

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Message Broker
Documentation

Software version:

6.1

Operating system(s):

Windows

Reference #:

7010522

Modified date:

2007-10-25

Translate my page

Machine Translation

Content navigation