System Requirements for WebSphere MQ V7.0/7.0.1 on Linux for System x (64-bit)

Product documentation


Abstract

This document contains the system requirements for WebSphere MQ V7.0 on Linux for System x (64-bit).

Content

Please read first
  • On platforms where WebSphere MQ provides a 64-bit product, both 32-bit and 64-bit MQ APIs are supported and the OS must be capable of running 64-bit applications.
  • Migration of 32-bit x86 MQ product queue managers to the 64-bit x86-64 MQ product is not supported at the same MQ release. So a queue manager created or started using the 32-bit x86 MQ V7 product cannot be started using the 64-bit x86-64 V7 MQ product. Also, no migration is supported from any 64-bit x86-64 MQ product to any 32-bit x86 MQ product. Migration is supported from queue managers last started using the 32-bit MQ V6 to the 64-bit MQ x86-64 V7 product.
  • The 'MQ Explorer' tooling will run on all supported Linux x86-64 environments.
  • For details of which browsers are supported for the ‘MQ Explorer’ see: http://www.eclipse.org/swt/faq.php#browserlinux
  • 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.
Hardware requirements
  • AMD64, EM64T, and compatible processors - any hardware that is explicitly compatible and fully capable of running the specified operating system, all the corresponding supporting software shown below, and any associated applications unmodified.
Operating Systems
  • Red Hat Enterprise Linux (RHEL) V4 or later update [see section notes 1, 2 and 4]
  • Red Hat Enterprise Linux (RHEL) V5 or later update [see section notes 1, 2, 3, 5 and 8]
  • Red Hat Enterprise Linux (RHEL) V6 or later update [see section notes 2, 6, 7, 8 and 9]
  • SUSE Linux Enterprise Server (SLES) V9 with Service Pack 1 or later update
  • SUSE Linux Enterprise Server (SLES) V10 with Service Pack 1 or later update
  • SUSE Linux Enterprise Server (SLES) V11 or later update [see section note 1]
  • Ubuntu 10.04 LTS [see section note 10]

Note:
  1. WebSphere MQ V7.0.0.2 or later is required.
  2. SELinux must be disabled.
  3. For multi-instance queue managers support, ensure the fix associated with Bugzilla 524520 (CVE-2009-3286) is applied.
  4. For SSL/TLS support on Red Hat Enterprise Linux V4, patch compat-libstdc++-33-3.2.3-47.3 or later is required.
  5. For SSL/TLS support on Red Hat Enterprise Linux V5, patch compat-libstdc++-33-3.2.3-61 or later is required.
  6. For SSL/TLS support on Red Hat Enterprise Linux V6, patch compat-libstdc++-33-3.2.3-69 or later is required.
  7. WebSphere MQ V7.0.1.3 or later is required..
  8. 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.
  9. Installation of WebSphere MQ 7.0/7.0.1 requires support for 32-bit C applications, this is not installed by default on RHEL V6.
  10. WebSphere MQ 7.0.1.3 required .All Applicable Components For development use.  Not for use within production systems. Limitations no support for WMQ Explorer and SSL/TLS.  Java support limited to 1.6 and 1.7.
For C/C++ applications
  • GNU C Compiler (gcc) and g++ V3.3 (SLES/9)
  • GNU C Compiler (gcc) and g++ V4.1 (SLES/10) [see section note 1,2]
  • GNU C Compiler (gcc) and g++ V4.3 (SLES/11) [see section note 1,2]
  • GNU C Compiler (gcc) and g++ V3.4 (RedHat/4) [see section note 1,2]
  • GNU C Compiler (gcc) and g++ V4.1 (RedHat/5) [see section note 1,2]
  • GNU C Compiler (gcc) and g++ V4.4 (RedHat/6) [see section note 1,2]

Notes:
  1. 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.
  2. The C++ libraries provided with WebSphere MQ are built with GNU g++ version 4.1. These libraries are compatible with all versions of the GNU g++ compiler which share the same ABI. Versions of the gnu g++ compiler which are known to be consistent with the GNU 4.1 ABI are:
  • GNU g++ 4.1
  • GNU g++ 4.2
  • GNU g++ 4.3
  • GNU g++ 4.4
For COBOL applications
  • Micro Focus Server Express V4.0, V5.0 and V5.1 [see section note 1]

Notes:
  1. For V5.1, WebSphere MQ V7.0.1 or later is required.
For Java™ applications using the WebSphere MQ classes for Java or JMS 32-bit:
  • Java 2 Platform, Standard Edition (J2SE) V1.4.2 from Sun Microsystems, Inc.
  • Java 2 Platform, Standard Edition (J2SE) V5.0 from Sun Microsystems, Inc.
  • Oracle JRockit 6 [see section notes 2 and 3]
  • Sun Java SDK/JRE/JDK 6.0/1.6
  • Oracle Java SDK/JRE/JDK 7.0.5 [see section notes 4 and 5]
  • IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition V1.4.2 (see section note 1 and 7)
  • IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition V5.0 (SR1 or above) [see section note 7]
  • IBM 32-bit SDK for Linux on Intel architecture, Java Technology Edition V6.0 [see section note 1 and 7]
  • IBM Runtime Environment, Java Technology Edition 7.0 and future Fix Packs [see section notes 1,4,5 and 7]
64-bit:
  • Java 2 Platform, Standard Edition (J2SE) V1.5 from Sun Microsystems, Inc.
  • Oracle JRockit 6 [see section notes 2, 3 and 6]
  • Sun Java SDK/JRE/JDK 6.0/1.6
  • Oracle Java SDK/JRE/JDK 7.0.5 [see section notes 4 and 5]
  • IBM 64-bit SDK for Linux on AMD64/EM64T architecture, Java 2 Technology Edition, V1.4.2 (see section note 1 and 7)
  • IBM 64-bit SDK for Linux on AMD64/EM64T architecture, Java 2 Technology Edition, V5.0 (SR1 or above) [see section note 7]
  • IBM 64-bit SDK for Linux on AMD64/EM64T architecture, Java Technology Edition, V6.0 (see section note 1 and 7)
  • IBM Runtime Environment, Java Technology Edition 7.0 and future Fix Packs [see section notes 1, 4, 5, and 7]

Notes:
  1. Only if the JDK is supplied with another IBM product.
  2. WebSphere MQ V7.0.1.3 or later is required.
  3. Only supported when being used in conjunction with Oracle WebLogic Server.
  4. Java 7 not available on RHEL 4 and SLES 9.
  5. WebSphere MQ V7.0.1.6 or later is required.
  6. When using the JRockit JVM and connecting to a queue manager using the BINDINGS transport, the LD_PRELOAD environment variable must be set to the following:
    export LD_PRELOAD=$JROCKIT_HOME/jre/lib/i386/libjsig.so
  7. FIPS 140-2 compliance is only supported on IBM JREs
SOAP Support
  • IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition V1.4.2
  • IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition V5.0 (SR1 or above)
  • IBM 32-bit SDK for Linux on Intel architecture, Java Technology Edition V6.0
  • IBM Runtime Environment, Java Technology Edition 7.0 and future Fix Packs 32-bit only.
  • Transport for SOAP support on 32-bit only (Apache Axis 1.4) - commonly known as Axis 1
    (supplied with WebSphere MQ)
  • Transport for SOAP support on 32-bit only (Apache Axis2 1.4 ) - commonly known as Axis2
Transactions Managers Using the WebSphere MQ classes for JMS, WebSphere MQ can only act in the role of a Resource Manager. A 3rd party Transaction Coordinator must be used, for example WebSphere Application Server.

Using the WebSphere MQ classes for Java, WebSphere MQ can act as a Transaction Coordinator. However it is not possible to participate in a JTA style transaction.

The WebSphere MQ V7 Queue Manager can participate as a Resource Manager with the following Transaction Coordinators:
  • BEA Tuxedo V9.1
  • Oracle Tuxedo 11gR1 [see section note 1]
  • IBM WebSphere Application Server, including the WebSphere Application Server client container, V6.0.2 (see this document for more information)
  • IBM WebSphere Application Server, including the WebSphere Application Server client container, V6.1 (see this document for more information)
  • IBM WebSphere Application Server, including the WebSphere Application Server client container, V7.0 (see this document for more information
  • IBM WebSphere Application Server, including the WebSphere Application Server client container, V8.0 (see this document for more information

Notes:
  1. WebSphere MQ V7.0.1.1 or later is required.
Application Servers Where a WebSphere MQ client application is running in one of the listed transaction manager environments, it is recommended that you contact the transaction manager vendor in the first instance for support.

WebSphere MQ V7 Java Messaging is supported for use within the following application servers [see section note 4]:
  • IBM WebSphere Application Server, including the WebSphere Application Server client container, V6.0.2 (see this document for more information)
  • IBM WebSphere Application Server, including the WebSphere Application Server client container, V6.1 (see this document for more information)
  • IBM WebSphere Application Server V7.0 and V8.0 include the WebSphere MQ V7 Java Messaging feature. Information on the levels of the WebSphere MQ V7 Java Messaging feature that are shipped with these versions of the application server can be found here
  • BEA WebLogic Server 9.2 (JMS only)
  • Oracle WebLogic Server 10.3 (JMS only) [see section note 2]
  • Oracle WebLogic Server 11gR1 (JMS only) [see section note 3 and 5]
  • Other application server environments may be supported [see section note 1]
  • Oracle WebLogic Server 12cR1 (12.1.1) [see section note 6]

Notes:
  1. For more detailed information about using WebSphere MQ with application servers see the WebSphere MQ resource adapter statement of support document.
  2. WebSphere MQ V7.0.1 or later is required.
  3. WebSphere MQ V7.0.1.1 or later is required.
  4. The use of the WebSphere MQ classes for JMS in enterprise JavaBeans, Servlets and message-driven beans is fully supported. The WebSphere MQ base classes for Java are supported with restrictions - for more details see Using WebSphere MQ Java Interfaces in J2EE/JEE Environments.
  5. Oracle WebLogic Server 11gR1 equals all versions 10.3.1 up to and including 10.3.6
  6. WebSphere MQ V7.0.1.8 or later is required.
Resource Managers (when MQ is the Transaction Manager)
Notes:
  1. Informix Dynamic Server (IDS) and Sybase Adaptive Server Enterprise (ASE) are NOT supported by the WebSphere MQ Java Classes.
  2. WebSphere MQ V7.0.1 or later is required.
  3. For JDBC XA support, WMQ V7.0.1.2 or later is required plus APAR IZ66717; alternatively, use WMQ V7.0.1.5 or later.
  4. WebSphere MQ V7.0.1.1 or later is required.
Connectivity
  • TCP/IP (IPv4 and IPv6 provided by the operating system)
SSL/TLS GSKit:
  • IBM Global Security Kit V7D (32-bit)
  • IBM Global Security Kit V7D (64-bit)

Refer to the Cryptography Card List for WebSphere MQ v6 and v7 document for further information.
Supported browsers for the WebSphere MQ information center
  • Mozilla 1.7
  • Firefox 1.5, Firefox 2.0
  • Konqueror (UI base mode only - meaning that only the basic functions of the information center will work, i.e. All function that supports base user activities with the content such as displaying a topic, locating a topic via the table of contents, searching for a topic and displaying it, etc are retained in base mode)
Supported application servers for the WebSphere MQ Bridge for HTTP
  • WebSphere Application Server V6.0.2.1 or later
  • WebSphere Application Server V7 or later
  • WebSphere Application Server Community Edition (WAS CE) V1.1 or later
  • WebSphere Application Server Community Edition (WAS CE) V2.1 or later
Multi-instance queue manager WebSphere MQ V7.0.1 introduces Multi-instance queue managers. For this you will need a networked storage device (such as a NAS). The storage must be accessed by a network file system protocol which is Posix-compliant and supports lease-based locking. Network File System version 4 (NFS v4) and IBM's General Parallel File System (GPFS) both satisfy this requirement. Please note that earlier versions of NFS do NOT satisfy this requirement and must not be used with multi-instance queue managers.

Testing and support statement for WebSphere MQ multi-instance queue managers

Notes:
  1. RHEL V4 - multi-instance queue managers are not supported.
  2. RHEL V5.4 - apply the fix associated with Bugzilla 524520 (CVE-2009-3286).
Virtualization Please read the read me first section in conjunction with this
  • VMWare: 3.0, 3.5, 4.0, 4.1
  • VMware ESXi 3.5, 4.0, 4.1, 5.0, 5.1 and 5.5



Change history:
  • 25th April 2008: Added the WebSphere MQ Bridge for HTTP section.
  • 2nd May 2008: Added the Service Pack reference to both SLES V9 and V10.
  • 19th June 2008: Added "For C/C++ applications" note 1.
  • 10th July 2008: In the Application Server section split the IBM WebSphere Application Server V6.0.2 and V6.1 entry into separate listings.
  • 24th September 2008: Corrected Informix Dynamic Server (IDS) V10.50 with Client SDK V2.91 to V11.10 with Client SDK V3.0.
  • 19th December 2008: Added support for IBM WebSphere Application Server V7.0.
  • 19th December 2008: Added the Cryptography Cards section.
  • 11th March 2009: Added support for WebSphere Application Server V7.
  • 11th March 2009: Added support for WebSphere Application Server Community Edition (WAS CE) V2.1.
  • 26th June 2009: Added support for RHEL V5.3 and SLES V11.
  • 8th July 2009: Clarified 'MQ Explorer' will run on both Linux x86 and x86-64 environments.
  • 25th August: 2009: Added support for WMQ V7.0.1.
  • 20th October 2009: Added support for Micro Focus Server Express V5.1.
  • 12th December 2009: Added "SELinux must be disabled." note.
  • 7th October 2009: Added support for Oracle WebLogic Server 10.3.
  • 23rd January 2010: Added support for IBM DB2 9.7 for Linux, UNIX and Windows and Oracle 11g Release 1.
  • 1st April 2010: Added support for Informix Dynamic Server (IDS) V11.5.
  • 8th April 2010: Added support for Oracle 11g Release 2.
  • 10th April 2010: Added support for Red Hat Enterprise Linux (RHEL) V5.4.
  • 20th April 2010: Added support for Oracle WebLogic Server 11gR1.
  • 2nd July 2010: Added support for Oracle Tuxedo 11gR1.
  • 22nd October 2010: Added JDBC XA support for DB2 and Oracle databases.
  • 26th November 2010: Added support for Oracle JRockit 6.
  • 11th February 2011: Added support for Red Hat Enterprise Linux (RHEL) V6.0.
  • 11th July 2011: Added support for IBM WebSphere Application Server V8.0.
  • 27th January 2012: Added SLES/11 and RedHat/6 to Compiler list and "For C/C++ applications" note 2.
  • 19th July 2012: Added note 9 to Operating System section.
  • 12th October 2012: Added Java 7 (1.7) support.
  • 6th December 2012: Added Note 5 to Application Servers section.
  • 2nd January 2013: Added Oracle WebLogic Server 12cR1 (12.1.1) and Note 5 to Application Server section.
  • 31st January 2013: Added support for DB2 Advanced Enterprise Server Edition 10.1
  • 1st February 2013: Added clarification to Oracle Database 11g Standard/Enterprise Editions Release 1 and 2
  • 14th June 2013: Virtualization update.
  • 17th June 2013: Java correction.
  • 2nd August 2013: Added support for Ubuntu 10.04 LTS and section note 10.
  • 15 October 2013: Added clarification to SOAP Support section.
  • 6 November 2013: Added DB2 Advanced Enterprise Server Edition 10.5
  • 17 December 2013: Added VMware ESXi 5.5
  • 21 March 2014: Added comment to JRockit statement
  • 21 July 2014: Added FIPS 140-2 compliance is only supported on IBM JREs comment.
  • 22 July 2014: Added FIPS 140-2 compliance is only supported on IBM JREs comment to an entry previously missing it.

Product Alias/Synonym

WMQ MQ

Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere MQ
Documentation

Software version:

7.0

Operating system(s):

Linux

Reference #:

7011926

Modified date:

2014-07-22

Translate my page

Machine Translation

Content navigation