This document contains system requirements on WebSphere MQ V6 Linux for System x (32-bit).
The System Requirements documented on this page, for the Linux on x86 platform, are for the 32-bit x86 operating systems. If you require support information about the 64-bit operating systems, refer to the Linux for System x (64-bit) platform System Requirements.
|Java and JMS Client||
|Databases||Where IBM WebSphere MQ is acting as the transaction manager.
|Transaction Managers||Where one of these products is acting as the transaction manager and IBM WebSphere MQ is acting as a resource manager, it's recommended that you contact the transaction manager vendor in the first instance for support.
|Cryptography Cards||Refer to the Cryptography Card List for WebSphere MQ v6 and v7 document for further information.|
- JDBC/XA usage is not supported on this platform.
- Only 32-bit versions of the above operating systems are supported. 64-bit versions are NOT supported.
- For Oracle 9i, Release 2 with Patch Set 4 (V220.127.116.11) patch 3501955 is required.
- On 64-bit platforms where WebSphere MQ provides both a 32-bit and a 64-bit product, there is NO migration path from V6 32-bit Queue Managers to V6 64-bit Queue Managers. Customers are strongly advised to install WebSphere MQ 64-bit products on 64-bit platforms as there is a migration path from V5 32-bit products to V6 64-bit products.
- The 'MQ Explorer' tooling is supported on the following Linux(x86) environments: Red Hat Enterprise Linux Advanced Server V3.0 (Update 2); Red Hat Enterprise Linux Advanced Server V4.0; Red Hat Enterprise Linux Advanced Server V5.0; and SUSE Linux Enterprise Server (SLES) 9; SUSE Linux Enterprise Server (SLES) 10; and SUSE Linux Enterprise Server (SLES) 11.
- The WebSphere MQ Explorer tooling is only supported running inside the eclipse version installed as part of the WebSphere MQ V6 install or running inside the WebSphere Message Broker V6 installed eclipse environment. Note that running inside the WebSphere Message Broker V6 eclipse environment requires MQ version 18.104.22.168 or later.
- WebSphere MQ V22.214.171.124 or later is required.
- For details of the Support Statement for JCA (on WebSphere MQ V126.96.36.199 or later only) please see here.
- Defect support is available for virtualization environments where they relate to releases of this platform already supported by WebSphere MQ. Unless stated elsewhere in the system requirements, WebSphere MQ has not been specifically tested in virtualization environments. WebSphere MQ Support is therefore unable to assist in issues related to configuration and setup, or issues that are directly related to the virtualization environment itself.
- On Linux platforms, if you need to use SSL in a C++ MQ application then you must link the application against the libstdc++.so.5 runtime library. This is because the version of the GSkit SSL libraries supplied with MQ depends on libstdc++.so.5 and this GSkit version is not compatible with other C++ runtime library versions. MQ C++ applications built against the GCC 3.2 or 3.3 C++ runtime libraries comply with this restriction and will be able to use SSL.
- WebSphere MQ V188.8.131.52 or later is required.
- SELinux must be disabled.
- WebSphere MQ V184.108.40.206 or later is required.
- This only applies to Red Hat Linux: With Tuxedo V8.1, ensure you have a fix with identifier CR235194. This ensures that WebSphere MQ can successfully access the C library function catopen() in a Tuxedo server program. For Tuxedo V10 this fix is already included in the code. For both Tuxedo V8.1 and V10 an environment variable must be exported to enable the fix. Please issue the command export TM_OS_CAT=libc.so in the shell before starting the Tuxedo program. This will enable the fix in CR235194. Refer also to BEA solution ID S-31436. Please refer to Tuxedo product documentation or contact Tuxedo support for any further technical details.
- Use rolling patch R017 so as to obtain a fix with identifier CR382618. After the rolling patch is installed over the base release of Tuxedo 10, the $TUXDIR/udataobj directory will contain a patchlev.txt file containing the list of patches applied. To properly implement the fix for CR382618 you must modify the $TUXDIR/udataobj/RM file so that it uses static registration and you must set and export the TUXWA4MQSERIES environment variable (to anything, e.g. export TUXWA4MQSERIES=1) before performing a tmboot. Please refer to Tuxedo product documentation or contact Tuxedo support for any further technical details.
- WebSphere MQ V220.127.116.11 or later is required.
- WebSphere MQ V18.104.22.168 or later is required.
- Only supported at the following combination: OS - RHEL 3.0/4.0 or SLES 8/9; Java - BEA WebLogic 1.4.2; Usage - EJB's (including MDB's) and JMS only.
- Defect support is available for Linux environments that are fully compatible - both source and binary - with Red Hat Enterprise Linux V5. Unless stated otherwise, WebSphere MQ has not been specifically tested in such compatible environments. WebSphere MQ Support is therefore unable to assist in issues related to configuration and setup, or issues that are directly related to the linux environment itself.
If issues arise that are related to the compatible linux environment, the user may need to contact the linux environment vendor for support, or the issue may need to be recreated inside an environment tested by IBM in order to receive WebSphere MQ support.
- 27 July 2005: Changed Oracle 10g to Oracle 10g Release 1.
- 2 August 2005: Clarification about 64-bit operating system support
- 30 September 2005: Added support for Red Hat Enterprise Linux (RHEL) V4.0.
- 26 October 2005: Modifications to the format & minor clarifications; Added support for NLPOS9 FP1 and IRES V2.
- 27 October 2005: Corrected GNU C Compiler (gcc) version number; changed V2.9.5 to V2.95.
- 18 November 2005: Clarified RHEL V3.0 Update 2 support.
- 23 December 2005: Added support for Red Flag Data Center V5.0.
- 6 March 2006: Clarified RHEL V4.0 update support.
- 2 May 2006: Added support for IBM SDK V5.0.
- 2 June 2006: Added support for Oracle 10GR2.
- 27 June 2006: Added note 6.
- 27 June 2006: Added "or later maintenance update" to the Red Hat operating systems.
- 6 October 2006: Added "SP1 or later" to SLES 9.
- 13 January 2007: Removed SLES 8 reference from WebSphere Application Server V5.1.
- 1 February 2007: Added support for SUSE Linux Enterprise Server (SLES) V10 with Service Pack (SP) 1 or later.
- 7 February 2007: Added support for IBM DB2 Universal Database V9.1 (JDBC/XA not supported)
Added "or later" to SUSE Linux Enterprise Server (SLES) V8 with Service Pack (SP) 3
- 30 March 2007: Added note 9.
- 19 June 2007: Made change to databases IBM DB2 and Connectivity TCP/IP.
- 10 July 2007: Added Red Hat Enterprise Linux (RHEL) V5.0 or later maintenance update.
- 22 November 2007: Added support for IBM WebSphere Application Server V6.
- 18 December 2007: Added Micro Focus Server Express V5.0 (COBOL).
- 10 March 2008: Added virtualization note.
- 30 April 2008: Clarified SSL support is not available with JDK 1.3.1.
- 17 June 2008: Added support for GNU C Compiler (gcc) and g++ V4.1.
- 19 June Added SSL note 11.
- 10 July 2008: In the Transaction Manager section added the IBM WebSphere Application Server V6.0.2 and V6.1 entries.
- 18 November 2008: Added support for IBM WebSphere Application Server, including the WebSphere Application Server client container, V7.0.
- 11 November 2008: Added support for Red Hat Enterprise Linux (RHEL) V5.1 and V5.2.
- 28 November 2008: Note 4 deleted.
- 8 December 2008: Added support for BEA Tuxedo V10.0.
- 22 December 2008: Added the Cryptography Cards section.
- 12 February 2009: Added notes relating to Tuxedo V8.1 and V10.
- 7 April 2009: Added support for IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition V6.0.
- 9 July 2009: Added support for Red Hat Enterprise Linux (RHEL) V5.3 and SUSE Linux Enterprise Server (SLES) V11.
- 8 October 2009: Added 64-bit compatibility to the Hardware Requirements.
- 22 October 2009: Added support for Micro Focus Server Express V5.1 (COBOL).
- 14 April 2010: Added support for Red Hat Enterprise Linux (RHEL) V5.4.
- 10 May 2011: Added the Linux Redhat V5.0 compatibility support statement.
- 4 July 2012: Updated expiry date to keep current.
Original publication date