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

Operating Systems		IBM® AIX Version 5.1 (maintenance level 3), IBM AIX Version 5.2 (maintenance level 2) or IBM AIX Version 5.3 (maintenance level 2)
Hardware Requirements		IBM eServer™ pSeries®, IBM RS/6000® processor machines or IBM eServer i5
Java™		Broker requires Java Runtime Environment 1.3.1 (SR3 or later) or 1.4.2 (with limitations, see additional notes)
Databases		IBM DB2® Enterprise Edition, V7.2 (plus Fix Pack 9) IBM DB2 Enterprise Server Edition, V8.1 (plus Fix Pack 2) or V8.2 Oracle 9i Release 2 Oracle 10g Release 1 (see note 9) Oracle 10g Release 2 (see note 9) Sybase Adaptive Server Enterprise (ASE) V12.5
WebSphere MQ		IBM WebSphere MQ for AIX, V5.3 (plus CSD 4) IBM WebSphere MQ AIX V6.0.1 or above

Notes:

1. Only the Broker is supported on this operating system. The Configuration Manager and Broker Toolkit are not supported on AIX.
2. Coordinated transactional support:
   • On WebSphere MQ V5.3, coordinated transactional support is available for all supported databases, except 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 Fix Pack 3 is recommended for DB2 v8.1 for coordinated transactional support.
3. 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.
4. 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 Fix Pack 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.
5. Support for 64-bit databases (DB2 and Oracle):
   • The Broker is a 32-bit application and interacts with 32-bit database libraries. In these Broker environments, our statement of support for databases refers to the database client.
   • The Broker supports connecting to a 32-bit database client which connects to a 64-bit server.
   • The Broker does not support connecting to a 64-bit database client. This restriction is imposed by both the Broker and the DataDirect drivers.
   • Oracle 9i installs both 64-bit and 32-bit libraries, with the 64-bit libraries as the default. For example, the 64-bit libraries are installed in the ${ORACLE_HOME}/lib directory and the 32-bit libraries are installed in the /lib32 directory. The customer must configure the Broker environment to use the 32-bit libraries (using mqsi_setupdatabase)
6. Support for JRE 1.4:
   • Broker Fix Pack 5 or later is recommended.
   • The WebSphere MQ Real-time Transport is not currently supported with JRE 1.4.
   • On AIX, the Broker automatically looks for the JRE in the directory /usr/java131. For the Broker to use JRE 1.4, rename the java131 directory and replace this directory with a soft link to the JRE 1.4 installation.
     For example, "ln -s /usr/java14 /usr/java131".
7. If you are using IBM JRE 1.3.1 SR9 (or later) or JRE 1.4.2 SR2 (or later) you must ensure that /usr/java131/jre/bin/classic and /usr/java131/jre/bin are added and exported to your LIBPATH (if you are using Java 1.4.2, you must have a symbolic link from /usr/java131 to your Java 1.4.2 installation). It is also necessary to set and export LDR_CNTRL=USERREGS.
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. Oracle 10gR1 and 10gR2 is only supported with WBI-MB Fix Pack 8 or later. The DataDirect V5.0 drivers must be used.
10. If you are using xlC/xlC++ runtime libraries at V9 the minimum supported level is V9.0.0.3.

Change History:

• 25 August 2005: Moved information from static page and redirected to this document.
• 21 September 2005: Clarification regarding Sybase coordinated transactional support.
• 25 November 2005: Additional note added (note 7).
• 5 December 2005: Added support for WebSphere MQ V6.
• 20 December 2005: Added note 8.
• 16 January 2006: Additional detail provided for note 7.
• 27 June 2006: Added support for Oracle 10gR1.
• 13 January 2007: Added support for Oracle 10gR2.
• 2 August 2007: Added 10gR2 to note 9.
• 21 April 2008: Added note 10.