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

The Toolkit, Configuration Manager and Broker requirements for Windows are documented below.


Toolkit Requirements:

Operating Systems		Microsoft® Windows 2000 Professional, Server and Advanced Server (with SP3) Microsoft Windows XP Professional SP1 or later [see note 7].
Hardware Requirements		IBM® xSeries® or equivalent Intel® based system (Minimum requirement: Intel® Pentium III, 700 MHz or higher, 512 MB RAM)

Operating Systems		Microsoft Windows 2000 Professional, Server and Advanced Server (with SP3) Microsoft Windows Server 2003 (Standard and Enterprise editions) Microsoft Windows XP Professional SP or later [see note 7].
Hardware Requirements		IBM® xSeries® or equivalent Intel® based system (Minimum requirement: Intel Pentium III, 700 MHz or higher, 512 MB RAM)
Databases		IBM DB2® Enterprise Edition, V7.2 (plus FixPak 9) IBM DB2 Enterprise Server Edition, V8.1 (plus FixPak 2) or V8.2
WebSphere MQ		IBM WebSphere MQ for Microsoft Windows V5.3 (plus CSD 4) IBM WebSphere MQ Windows V6.0.1 or above

1. Where a DB2® Client/Server configuration is employed, only DB2 Servers in distributed environments are supported (for example not OS/400® nor z/OS®).

Operating Systems		Microsoft Windows 2000 Server (with SP3) Microsoft Windows 2000 Advanced Server (with SP3) Windows Server 2003 (Standard and Enterprise editions)
Hardware Requirements		IBM xSeries (or equivalent Intel® based system) iSeries® Server (using the IBM Integrated xSeries Server)
Java™		Java Runtime Environment 1.3.1 (embedded within the product) Java Runtime Environment 1.4.2 (with limitations, see additional notes)
Databases		IBM DB2 Enterprise Edition, V7.2 (plus FixPak 9) (not supported on Windows Server 2003) IBM DB2 Enterprise Server Edition, V8.1 (plus FixPak 2) or V8.2 Oracle 9i Release 2 Oracle 10g Release 1 (see note 6) Sybase Adaptive Server Enterprise (ASE) V12.5 (On Windows 2003 you should use V12.5.3 ESD1) Microsoft SQL Server 2000 (SP3)
WebSphere MQ		IBM WebSphere MQ for Microsoft Windows V5.3 (plus CSD 4) IBM WebSphere MQ Windows V6.0.1 or above

1. Coordinated transactional support:
   • On WebSphere MQ V5.3, Coordinated transactional support is available for all supported databases, except Microsoft SQL Server 2000 and Sybase ASE.
   • On WebSphere MQ V6.0, coordinated transactional support is only available on DB2. You should be running on WBI 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.
2. 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.
3. 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.
4. Support for JRE 1.4:
   • Broker Fix Pack 6 or later is recommended.
   • The WebSphere MQ Real-time Transport is not currently supported with JRE 1.4.
   • The Configuration Manager is not supported with Java version 1.4.
   • The Configuration Manager and the Broker automatically look for the JRE in the directory <install dir>\jre which is populated at product install time with JRE 1.3.1. For the Broker to use JRE 1.4, rename the <install dir>\jre directory and replace this directory with the JRE 1.4 installation. This implies that the Configuration Manager and the Broker cannot run on the same machine if the Broker is configured to use JRE 1.4.
   • Only the IBM packaged JRE 1.4.2 for Windows is supported with the Broker, available on request from IBM Support.
5. 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.
6. Oracle 10gR1 is only supported with WBI-MB Fix Pack 8 or later. The DataDirect V5.0 drivers must be used. Oracle patch set 10.1.0.4 or later is also required.
7. Only 32-bit (NOT 64-bit) operating systems are supported.

• 1 September 2005: Moved information from static page and redirected to this document.
• 21 September 2005: Clarification regarding Sybase coordinated transactional support.
• 5 October 2005: Added support for JDK 1.4.2.
• 19 October 2005: Added support for Sybase ASE V12.5.3 ESD1 on Windows 2003.
• 5 December 2005: Added support for WebSphere MQ V6.
• 20 December 2005: Added note 5.
• 6 July 2006: Added support for Oracle 10GR1.
• 3 November 2006: Clarified XP SP1 or later and added note 7.