System Requirements for WebSphere MQ V7.0/7.0.1 on Linux for System p

Product documentation


Abstract

This document contains the system requirements for WebSphere MQ V7.0 on Linux for System p.

Content

Please read first
  • The 'MQ Explorer' will not run on this platform.
  • 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. Please also refer to WebSphere MQ's support position on Virtualization, low-level hardware, file systems on networks and high availability.
Hardware requirements
  • 64-bit System i and System p IBM POWER processor-based systems only, capable of running the required level of a compatible operating system with enough storage to meet the combined requirements of the programming prerequisites, WebSphere MQ, the access methods and the application programs.
  • POWER7 systems are supported with WebSphere MQ 7.0 or later when the guidance in IBM Developer Kits support for IBM Power7™ systems is adhered to. The recommended Fix Pack level is WebSphere MQ V7.0.1.2 or later.
Operating Systems
  • Red Hat Enterprise Linux (RHEL) V4 or later update [see section notes 1 and 2]
  • Red Hat Enterprise Linux (RHEL) V5 or later update [see section notes 1, 2, 3, 4 and 7]
  • Red Hat Enterprise Linux (RHEL) V6 or later update [see section notes 2, 5, 6, 7 and 8]
  • 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]

Notes:
  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 V5, patch compat-libstdc++-33-3.2.3-61 or later is required (for 32-bit GSKit binaries only).
  5. For SSL/TLS support on Red Hat Enterprise Linux V6, patch compat-libstdc++-33-3.2.3-69 or later is required (for 32-bit GSKit binaries only).
  6. WebSphere MQ V7.0.1.3 or later is required.
  7. 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.
  8. 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.
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 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:
  • IBM 32-bit SDK for Linux on iSeries and pSeries, Java 2 Technology Edition, V1.4.2 (supported on System p only) (see section note 1)
  • IBM 32-bit SDK for Linux on iSeries and pSeries, Java 2 Technology Edition, V5.0 (SR1 or above)
  • IBM 32-bit SDK for Linux on System i and System p
  • IBM Runtime Environment, Java Technology Edition 7.0 and future fixpacks (see section notes 1, 2 and 3)
64-bit:
  • IBM 64-bit SDK for Linux on iSeries and pSeries, Java 2 Technology Edition, V1.4.2 (supported on System p only) (see section note 1)
  • IBM 64-bit SDK for Linux on iSeries and pSeries, Java 2 Technology Edition, V5.0 (SR1 or above)
  • IBM 64-bit SDK for Linux on System i and System p architecture, Java Technology Edition, V6.0 (see section note 1)
  • IBM Runtime Environment, Java Technology Edition 7.0 and future fixpacks (see section notes 1, 2 and 3)

Notes:
  1. Only if the JDK is supplied with another IBM product.
  2. Java 7 not available on RHEL 4 and SLES 9.
  3. WebSphere MQ V7.0.1.6 or later is required.
SOAP Support
  • IBM 32-bit SDK for Linux on iSeries and pSeries, Java 2 Technology Edition, V1.4.2 (supported on System p only)
  • IBM 32-bit SDK for Linux on iSeries and pSeries, Java 2 Technology Edition, V5.0 (SR1 or above)
  • IBM 32-bit SDK for Linux on System i and System p architecture, Java Technology Edition, V6.0
  • IBM Runtime Environment, Java Technology Edition 7.0 and future fixpacks 32-bit only.
  • Transport for SOAP support on 32-bit only (Apache Axis 1.4) - commonly known as Axis 1 (supplied with WebSphere MQ)
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 2]:
  • 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)
  • Other application server environments may be supported [see section note 1]

Notes:
  1. For more detailed information about using WebSphere MQ with application servers see the WebSphere MQ resource adapter statement of support document.
  2. 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.
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. JDBC XA not supported.
  4. WebSphere MQ V7.0.1.1 or later is required.
Connectivity
  • IBM Communications Server for Linux V6.2(SNA)
  • 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 Community Edition (WAS CE) V1.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.
  • 26th June 2009: Added support for RHEL V5.3 and SLES V11.
  • 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.
  • 23rd January 2010: Added support for IBM DB2 9.7 for Linux, UNIX and Windows.
  • 1st April 2010: Added support for Informix Dynamic Server (IDS) V11.5.
  • 10th April 2010: Added support for Red Hat Enterprise Linux (RHEL) V5.4.
  • 20th July 2010: Clarified POWER7 support.
  • 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 8 to Operating System section .
  • 12th October 2012: Added Java 7 (1.7) support.
  • 31st January 2013: Added support for DB2 Advanced Enterprise Server Edition 10.1
  • 27th February 2013: Updated document expiry date.
  • 14th June 2013: Virtualization update.
  • 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

Product Alias/Synonym

WMQ MQ

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere MQ
Documentation

Software version:

7.0

Operating system(s):

Linux

Reference #:

7011924

Modified date:

2008-04-01

Translate my page

Machine Translation

Content navigation