| 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.
|
| 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.
|
| Operating Systems | | - Red Hat Enterprise Linux (RHEL) V4.0
- Red Hat Enterprise Linux (RHEL) V5.0 to V5.3 [see section note 1]
- SUSE Linux Enterprise Server (SLES) V9 with Service Pack 1 or later
- SUSE Linux Enterprise Server (SLES) V10 with Service Pack 1 or later
- SUSE Linux Enterprise Server (SLES) V11 [see section note 1]
Notes: - WebSphere MQ V7.0.0.2 or later is required.
|
| 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]
- GNU C Compiler (gcc) and g++ V3.4 (RedHat/4) [see section note 1]
- GNU C Compiler (gcc) and g++ V4.1 (RedHat/5) [see section note 1]
Notes: - 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.
|
| For COBOL applications | | - Micro Focus Server Express V4.0, V5.0 and V5.1 [see section note 1]
Notes: - 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
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)
Notes: - Only if the JDK is supplied with another IBM product.
|
| 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
- Apache Axis V1.4 (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: - 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)
- BEA WebLogic Server 9.2 (JMS only)
- Other application server environments may be supported [see section note 1]
Notes: - For more detailed information about using WebSphere MQ with application servers see the WebSphere MQ resource adapter statement of support document.
|
| Resource Managers (when MQ is the Transaction Manager) | |
Notes: - Informix Dynamic Server (IDS) and Sybase Adaptive Server Enterprise (ASE) are NOT supported by the WebSphere MQ Java Classes.
|
| Connectivity | | - IBM Communications Server for Linux V6.2(SNA)
- TCP/IP (IPv4 and IPv6 provided by the operating system)
|
| Versions of products / components shipped with the product | | JDK: - IBM 32-bit SDK for Linux on iSeries and pSeries, Java 2 Technology Edition, V5.0
- IBM 64-bit SDK for Linux on iSeries and pSeries, Java 2 Technology Edition, V5.0
GSKit: - IBM Global Security Kit V7D (32-bit)
- IBM Global Security Kit V7D (64-bit)
|
| 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
|
| Cryptography Cards | | Refer to the Cryptography Card List for WebSphere MQ v6 and v7 document for further information. |
| 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.
- Multi-instance queue managers are not supported on RHEL V4.
|
