The multi-instance queue manager feature requires networked storage for the queue manager's data. This can be provided by a networked storage device (such as NAS) or a cluster file system. 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.

See Testing and support statement for WebSphere MQ multi-instance queue managers for further information.

Virtualization. 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
• WebSphere MQ support position regarding Solaris zones
• Installing WebSphere MQ in AIX Workload Partitions
• Server Virtualization Policy for IBM Software

IBM Power 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.

AIX platform with 64-bit hardware; 32-bit and 64-bit WebSphere MQ APIs are supported.

Users of SSL/TLS require C++ runtime version 9.0.0.8 or later.

AIX HIPER APAR IZ84729 or IZ85204 must be Installed to run on AIX 6.1 Technology Level 06

Users of SSL/TLS require C++ runtime version 9.0.0.8 or later.

AIX HIPER APAR IZ84576 must be Installed to run on AIX 7.1 Technology Level 00

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.

For more detailed information about using WebSphere MQ with application servers see the WebSphere MQ resource adapter statement of support document.

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

Supported with WMQ used as a generic JMS provider.

Oracle WebLogic Server 11gR1 equals all versions 10.3.1 up to and including 10.3.6

Supported with WMQ used as a generic JMS provider.

See this document for more information.

See this document for more information.

See this document for more information.

Cobol.

The minimum level of IBM XL C/C++ Enterprise Edition for AIX v9.0 is 9.0.0.3.

The minimum level of IBM XL C/C++ Enterprise Edition for AIX v9.0 is 9.0.0.3.

FIPS 140-2 compliance is only supported on IBM JREs.

32-bit and 64-bit are supported.

Transport for SOAP support on 32-bit only (Apache Axis 1.4) - commonly known as Axis 1

FIPS 140-2 compliance is only supported on IBM JREs.

32-bit and 64-bit are supported.

Transport for SOAP support on 32-bit only (Apache Axis 1.4) - commonly known as Axis 1

FIPS 140-2 compliance is only supported on IBM JREs.

32-bit and 64-bit are supported.

Transport for SOAP support on 32-bit only (Apache Axis 1.4) - commonly known as Axis 1

Fix pack 7.1.0.7 or later is required.

FIPS 140-2 compliance is only supported on IBM JREs.

32-bit and 64-bit are supported.

Transport for SOAP support on 32-bit only (Apache Axis 1.4) - commonly known as Axis 1

SNA LU6.2 Services for AIX.

SNA LU6.2 Services for AIX.

Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ.

Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ.

Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ.

Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ.

Fix pack 6 or later is required.

Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java.

Fix pack 3 or later is required.

Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java.

Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java.

Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java.

Sybase Adapter Server Enterprise (ASE) is NOT supported by the WebSphere MQ classes for Java.

Sybase Adapter Server Enterprise (ASE) is NOT supported by the WebSphere MQ classes for Java.

Using the WebSphere MQ classes for JMS, WebSphere MQ can only act in the role of a Resource Manager. The WebSphere MQ classes for JMS can only participate in global transactions when accessed through the Java EE Connector Architecture (JCA) resource adapter, which can only be used with a suitable application server environment.

For more detailed information on the use of the resource adapter with application servers, see the Application Server section above, and the WebSphere MQ resource adapter statement of support document.

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

COM+/MTS provided with Microsoft Windows may also be used as a Transaction Manager.

The resiliency feature of TXSeries is not supported. For more details, please refer to
XA Resiliency feature of TXSeries doesn't work with WMQ as RM.

The resiliency feature of TXSeries is not supported. For more details, please refer to XA Resiliency feature of TXSeries doesn't work with WMQ as RM.

The WebSphere MQ V7.1 Telemetry feature operates on a subset of the WebSphere MQ supported environments. Please see the System Requirements for WebSphere MQ V7.1 Telemetry document for further information.

Refer to MQ 7.1 cryptographic hardware support for further information.

Please see notes in Other Hardware Section for detailed support statement.

Required for Coexistence with WebSphere MQ V7.1.

The multi-instance queue manager feature requires networked storage for the queue manager's data. This can be provided by a networked storage device (such as NAS) or a cluster file system. 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.

See Testing and support statement for WebSphere MQ multi-instance queue managers for further information.

ONC B.11.31.08 and libc cumulative patch PHCO_36900 or superseding patch is required for multi-instance queue manager support.

Virtualization. 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
• WebSphere MQ support position regarding Solaris zones
• Installing WebSphere MQ in AIX Workload Partitions
• Server Virtualization Policy for IBM Software

Itanium systems - any hardware that is explicitly compatible and fully capable of running the specified operating systems, all the corresponding supported software shown below, and any associated applications unmodified. Both 32-bit and 64-bit MQ APIs are supported and the OS must be capable of running 64-bit applications.

HP-UX PA-RISC is NOT supported

Before installing on HP-UX 11i v3 (11.31) see technote 1270591

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.

For more detailed information about using WebSphere MQ with application servers see the WebSphere MQ resource adapter statement of support document.

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

Supported with WMQ used as a generic JMS provider.

Oracle WebLogic Server 11gR1 equals all versions 10.3.1 up to and including 10.3.6

Supported with WMQ used as a generic JMS provider.

See this document for more information.

See this document for more information.

See this document for more information.

For applications using the WebSphere MQ C++ classes, both the standard and classic runtimes are supported.

Users of SSL/TLS client applications must link with the POSIX threads library.

Cobol.

32-bit and 64-bit are supported.

The Java Runtime Environment must be run with the following parameter set: -XX:+UseGetTimeOfDay, see What might happen in MQ if UseGetTimeOfDay is not set for more information.

pthread cumulative patch PHCO_34718 is required to resolve an intermittent core dump when running Java applications. The id of the problem is JAGref78055.

32-bit and 64-bit are supported.

The Java Runtime Environment must be run with the following parameter set: -XX:+UseGetTimeOfDay, see What might happen in MQ if UseGetTimeOfDay is not set for more information.

pthread cumulative patch PHCO_34718 is required to resolve an intermittent core dump when running Java applications. The id of the problem is JAGref78055.

Patches from HP must be applied depending on the operating system version being used:  HP-UX 11i V3 - patch is PHSS_40538.

32-bit and 64-bit are supported.

The Java Runtime Environment must be run with the following parameter set: -XX:+UseGetTimeOfDay, see What might happen in MQ if UseGetTimeOfDay is not set for more information.

pthread cumulative patch PHCO_34718 is required to resolve an intermittent core dump when running Java applications. The id of the problem is JAGref78055.

Patches from HP must be applied depending on the operating system version being used:  HP-UX 11i V3 - patch is PHSS_40538.

Fix pack 7.1.0.7 or later is required.

32-bit and 64-bit are supported.

The Java Runtime Environment must be run with the following parameter set: -XX:+UseGetTimeOfDay, see What might happen in MQ if UseGetTimeOfDay is not set for more information.

pthread cumulative patch PHCO_34718 is required to resolve an intermittent core dump when running Java applications. The id of the problem is JAGref78055.

Patches from HP must be applied depending on the operating system version being used:  HP-UX 11i V3 - patch is PHSS_40538.

This is the IBM-modified version of the HP SDK for J2SE HP-UX 11i platform.

FIPS 140-2 compliance is only supported on IBM JREs.

The Java Runtime Environment must be run with the following parameter set: -XX:+UseGetTimeOfDay, see What might happen in MQ if UseGetTimeOfDay is not set for more information.

pthread cumulative patch PHCO_34718 is required to resolve an intermittent core dump when running Java applications. The id of the problem is JAGref78055.

32-bit and 64-bit SDK are supported.

Transport for SOAP support on 32-bit only (Apache Axis 1.4) - commonly known as Axis 1

This is the IBM-modified version of the HP SDK for J2SE HP-UX 11i platform.

Only supported if the JDK is supplied with another IBM product.

FIPS 140-2 compliance is only supported on IBM JREs.

The Java Runtime Environment must be run with the following parameter set: -XX:+UseGetTimeOfDay, see What might happen in MQ if UseGetTimeOfDay is not set for more information.

pthread cumulative patch PHCO_34718 is required to resolve an intermittent core dump when running Java applications. The id of the problem is JAGref78055.

32-bit and 64-bit JDK are supported.

Transport for SOAP support on 32-bit only (Apache Axis 1.4) - commonly known as Axis 1

This is the IBM-modified version of the HP SDK for J2SE HP-UX 11i platform.

Only supported if the JDK is supplied with another IBM product.

FIPS 140-2 compliance is only supported on IBM JREs.

The Java Runtime Environment must be run with the following parameter set: -XX:+UseGetTimeOfDay, see What might happen in MQ if UseGetTimeOfDay is not set for more information.

pthread cumulative patch PHCO_34718 is required to resolve an intermittent core dump when running Java applications. The id of the problem is JAGref78055.

32-bit and 64-bit JDK are supported.

Transport for SOAP support on 32-bit only (Apache Axis 1.4) - commonly known as Axis 1

Fix pack 7.1.0.7 or later is required.

This is the IBM-modified version of the HP SDK for J2SE HP-UX 11i platform.

Only supported if the JDK is supplied with another IBM product.

FIPS 140-2 compliance is only supported on IBM JREs.

The Java Runtime Environment must be run with the following parameter set: -XX:+UseGetTimeOfDay, see What might happen in MQ if UseGetTimeOfDay is not set for more information.

pthread cumulative patch PHCO_34718 is required to resolve an intermittent core dump when running Java applications. The id of the problem is JAGref78055.

32-bit and 64-bit JDK are supported.

Transport for SOAP support on 32-bit only (Apache Axis 1.4) - commonly known as Axis 1

SNA LU6.2 Services for HP.

Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ.

Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ.

Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ.

Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ.

Fix pack 6 or later is required.

Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java.

Fix pack 3 or later is required.

Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java.

Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java.

Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java.

Sybase Adapter Server Enterprise (ASE) is NOT supported by the WebSphere MQ classes for Java.

Using the WebSphere MQ classes for JMS, WebSphere MQ can only act in the role of a Resource Manager. The WebSphere MQ classes for JMS can only participate in global transactions when accessed through the Java EE Connector Architecture (JCA) resource adapter, which can only be used with a suitable application server environment.

For more detailed information on the use of the resource adapter with application servers, see the Application Server section above, and the WebSphere MQ resource adapter statement of support document.

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

COM+/MTS provided with Microsoft Windows may also be used as a Transaction Manager.

The resiliency feature of TXSeries is not supported. For more details, please refer to
XA Resiliency feature of TXSeries doesn't work with WMQ as RM.

The resiliency feature of TXSeries is not supported. For more details, please refer to XA Resiliency feature of TXSeries doesn't work with WMQ as RM.

Refer to MQ 7.1 cryptographic hardware support for further information.

Required for Coexistence with WebSphere MQ V7.1.

Security: SSL/TLS is provided with the operating system, support requires:

• 5722SS1 Option 34: Digital Certificate Manager.
• 5722DG1 *Base: IBM HTTP Server to manage certificates through DCM.

Refer to the IBM Global Security Kit, Version 8 - PKCS#11 device integration document for further information.

The multi-instance queue manager feature requires networked storage for the queue manager's data. This can be provided by networked storage (such as NAS). The storage must be accessed by a network file system protocol which is POSIX-compliant and supports lease-based locking. Only IBM i NetServer is supported on this platform.

See Testing and support statement for WebSphere MQ multi-instance queue managers for further information.

Virtualization. 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
• WebSphere MQ support position regarding Solaris zones
• Installing WebSphere MQ in AIX Workload Partitions
• Server Virtualization Policy for IBM Software

IBM System i, 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.

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.

For more detailed information about using WebSphere MQ with application servers see the WebSphere MQ resource adapter statement of support document.

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

See this document for more information.

See this document for more information.

See this document for more information.

Only supported on IBM i 6.1.

Provides Integrated Language Environment facilities for: C, C++, COBOL, RPG.

Supported on IBM i 6.1 only

Option 10 of product 5761JV1 *Base

Supported on IBM i 6.1 only

Option 7 of product 5761JV1 *Base

32-bit: Option 9 of product 5761JV1 *Base

64-bit: Option 10 of product 5761JV1 *Base

32-bit: Option 11 of product 5761JV1 *Base

64-bit: Option 12 of product 5761JV1 *Base

IBM DB2 Universal Database as provided by the Operating System.

IBM DB2 Universal Database as provided by the Operating System.

Using the WebSphere MQ classes for JMS, WebSphere MQ can only act in the role of a Resource Manager. The WebSphere MQ classes for JMS can only participate in global transactions when accessed through the Java EE Connector Architecture (JCA) resource adapter, which can only be used with a suitable application server environment.

For more detailed information on the use of the resource adapter with application servers, see the Application Server section above, and the WebSphere MQ resource adapter statement of support document.

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

COM+/MTS provided with Microsoft Windows may also be used as a Transaction Manager.

Please see notes in Other Hardware Section for detailed support statement.

The multi-instance queue manager feature requires networked storage for the queue manager's data. This can be provided by a networked storage device (such as NAS) or a cluster file system. 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.

See Testing and support statement for WebSphere MQ multi-instance queue managers for further information.

Migration of 32-bit x86 queue managers to the 64-bit x86-64 MQ product is not supported at the same release. So a queue manager created or started using the 32-bit x86 MQ V7 product can not be started using the 64-bit x86-64 MQ product. 

No migration is supported from any 64-bit x86-64 MQ product to any x86-32 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

RHEL Compatible OS. 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.

Virtualization. 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
• WebSphere MQ support position regarding Solaris zones
• Installing WebSphere MQ in AIX Workload Partitions
• Server Virtualization Policy for IBM Software

Linux for System x (32-bit) x86 compatible PC hardware, including x86-64 processors, capable of running the required level of a compatible operating system with enough storage to meet the combines requirements of the programming prerequisites, WebSphere MQ, the access methods and the application programs.

Linux for System x (64-bit) AMD64, EMT64, and compatible processors - any hardware that is explicitly compatible and fully capable of tunning the specified operating system, all the corresponding supporting software shown below, and any associated applications unmodified.

Linux for System p 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. Power 7 systems are supported when the guidance in IBM Developer Kits support for IBM Power7 systems is adhered to.

Linux for System z IBM System z9/10 or IBM eServer (or equivalent) 64-bit processor - 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.

• 32-bit: Platforms with 32-bit hardware, 64-bit versions are NOT supported.
• 64-bit: Platforms with 64-bit hardware, WebSphere MQ requires a 64-bit kernel. 32-bit and 64-bit WebSphere MQ APIs are supported.

SELinux must be disabled.

SELinux must be disabled.

SELinux must be disabled.

SELinux must be  disabled.

SELinux  must be disabled.

SELinux  must be disabled.

SELinux must  be disabled.

SELinux must  be disabled.

SELinux  must be disabled.

SELinux  must be disabled.

SELinux must  be disabled.

SELinux must  be disabled.

(7.1.0.6 needed)

(7.1.0.6 needed)

(7.1.0.3 needed) Hardware platform: x86-32: 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.

(7.1.0.3 needed) Hardware platform: x86-32: 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.

(7.1.0.3 needed) Hardware platform: x86-64: 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.

(7.1.0.3 needed) Hardware platform: x86-64: 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.

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.

For more detailed information about using WebSphere MQ with application servers see the WebSphere MQ resource adapter statement of support document.

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

Linux for System x (x86-64) platforms only.

Supported with WMQ used as a generic JMS provider.

Linux for System x platforms only.

Supported with WMQ used as a generic JMS provider.

Oracle WebLogic Server 11gR1 equals all versions 10.3.1 up to and including 10.3.6

Linux for System x platforms only.

Supported with WMQ used as a generic JMS provider.

See this document for more information.

See this document for more information.

See this document for more information.

Only supported on the Linux for System p and Linux for System x.

Only supported on the Linux for System p and Linux for System x.

Only supported on the Linux for System p and Linux for System x.

Only supported on Linux for System p and Linux for System x.

Only supported on RHEL 5 and SLES 10.

If you need to use SSL/TLS in a C++ application then you must link the application against the libstdc++.so.6 runtime library. This is becasue the version of the GSKit SSL/TLS libraries supplied with MQ depends on libstdc++.so.6 and this GSkit version is not compatible with other C++ runtime library versions. MQ C++ applications built against the GCC 4.x C++ runtime libraries comply with this restriction and will be able to use SSL/TLS.

SLES 10 requires a minimum libstdc++.so library version of 6.0.8 for using SSL/TLS in client applications.

Only supported on SLES 11.

If you need to use SSL/TLS in a C++ application then you must link the application against the libstdc++.so.6 runtime library. This is becasue the version of the GSKit SSL/TLS libraries supplied with MQ depends on libstdc++.so.6 and this GSkit version is not compatible with other C++ runtime library versions. MQ C++ applications built against the GCC 4.x C++ runtime libraries comply with this restriction and will be able to use SSL/TLS.

Only supported on RHEL 6.

If you need to use SSL/TLS in a C++ application then you must link the application against the libstdc++.so.6 runtime library. This is becasue the version of the GSKit SSL/TLS libraries supplied with MQ depends on libstdc++.so.6 and this GSkit version is not compatible with other C++ runtime library versions. MQ C++ applications built against the GCC 4.x C++ runtime libraries comply with this restriction and will be able to use SSL/TLS.

GSKit requires a minimum glibc version of 2.12-1.7.el6_05 or later for using SSL/TLS in client applications.

Cobol.

Only supported if the SDK is supplied with another IBM product.

FIPS 140-2 compliance is only supported on IBM JREs.

Transport for SOAP support on 32-bit only (Apache Axis 1.4) - commonly known as Axis 1

Transport for SOAP support on 32-bit only (Apache Axis2 1.4 ) - commonly known as Axis2 - x86 only

32-bit SDK is supported on:

• Linux for System x (x86  and x86-64)
• Linux for System p
• Linux for System z

64-bit SDK is supported on:

• Linux for System x (x86-64)
• Linux for System p
• Linux for System z

Only supported if the SDK is supplied with another IBM product.

FIPS 140-2 compliance is only supported on IBM JREs.

Transport for SOAP support on 32-bit only (Apache Axis 1.4) - commonly known as Axis 1

Transport for SOAP support on 32-bit only (Apache Axis2 1.4 ) - commonly known as Axis2 - x86 only

32-bit SDK is supported on:

• Linux for System x (x86  and x86-64)
• Linux for System p
• Linux for System z

64-bit SDK is supported on:

• Linux for System x (x86-64)
• Linux for System p
• Linux for System z

Only supported if the SDK is supplied with another IBM product.

FIPS 140-2 compliance is only supported on IBM JREs.

Transport for SOAP support on 32-bit only (Apache Axis 1.4) - commonly known as Axis 1

Transport for SOAP support on 32-bit only (Apache Axis2 1.4 ) - commonly known as Axis2 - x86 only

32-bit SDK is supported on:

• Linux for System x (x86  and x86-64)
• Linux for System p
• Linux for System z

64-bit SDK is supported on:

• Linux for System x (x86-64)
• Linux for System p
• Linux for System z

Fix pack 7.1.0.7 or later is required.

Only supported if the SDK is supplied with another IBM product.

FIPS 140-2 compliance is only supported on IBM JREs.

Transport for SOAP support on 32-bit only (Apache Axis 1.4) - commonly known as Axis 1

Transport for SOAP support on 32-bit only (Apache Axis2 1.4 ) - commonly known as Axis2 - x86 only

32-bit SDK is supported on:

• Linux for System x (x86  and x86-64)
• Linux for System p
• Linux for System z

64-bit SDK is supported on:

• Linux for System x (x86-64)
• Linux for System p
• Linux for System z

Only supported on Linux for System x.

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

32-bit SDK is supported on:

• Linux for System x (x86 and x86-64)

64-bit SDK is supported on:

• Linux for System x (x86-64)

32-bit SDK is supported on:

• Linux for System x (x86 and x86-64)

64-bit SDK is supported on:

• Linux for System x (x86-64)

32-bit SDK is supported on:

• Linux for System x (x86 and x86-64)

64-bit SDK is supported on:

• Linux for System x (x86-64)

Fix pack 7.1.0.7 is required.

32-bit SDK is supported on:

• Linux for System x (x86 and x86-64)

64-bit SDK is supported on:

• Linux for System x (x86-64)

Only supported on Linux for System p and Linux for System x 32-bit platforms.

SNA LU6.2 Services for Linux.

Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ.

Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ.

Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ.

Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ.

Fix pack 6 or later is required.

Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java.

Fix pack 3 or later is required.

Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java.

Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java.

Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java.

Only supported on Linux for System p and Linux for System z.

Only supported on Linux for System x.

Only supported on Linux for System x and System z.

Only supported on Linux for System x and System z.

Only supported on Linux for System x and System z.

Only supported on Linux for System p and Linux for System x.

Sybase Adapter Server Enterprise (ASE) is NOT supported by the WebSphere MQ classes for Java.

Only supported on Linux for System x and Linux for System p.

Sybase Adapter Server Enterprise (ASE) is NOT supported by the WebSphere MQ classes for Java.

Using the WebSphere MQ classes for JMS, WebSphere MQ can only act in the role of a Resource Manager. The WebSphere MQ classes for JMS can only participate in global transactions when accessed through the Java EE Connector Architecture (JCA) resource adapter, which can only be used with a suitable application server environment.

For more detailed information on the use of the resource adapter with application servers, see the Application Server section above, and the WebSphere MQ resource adapter statement of support document.

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

COM+/MTS provided with Microsoft Windows may also be used as a Transaction Manager.

Only supported on Linux for System x

Only supported on Linux for System x

Only supported on Linux for System x

The WebSphere MQ V7.1 Telemetry feature operates on a subset of the WebSphere MQ supported environments. Please see the System Requirements for WebSphere MQ V7.1 Telemetry document for further information.

Refer to MQ 7.1 cryptographic hardware support for further information.

32-bit only support on:

• Linux for System x (32-bit) platforms

32-bit and 64-bit support on:

• Linux for System p
• Linux for System x (64-bit) platforms
• Linux for System z

MQ Explorer is only supported on x86-32 and x86-64 platforms

MQ Explorer is not supported on the following x86 platforms:

• IBM Retail Environment for SUSE
• Red Flag 5.0 DC Server
• SUSE Linux Enterprise Point of Service (NLPOS/SLEPOS)

MQ Explorer is supported when added to the following compatible Eclipse-based products:

• IBM Rational Application Developer for WebSphere Software V8.0.3 or later fix pack. 32-bit install only on x86-32 platforms and 64-bit install only on x86-64 platforms.

Please see notes in Other Hardware Section for detailed support statement.

Required for Coexistence with WebSphere MQ V7.1.

The multi-instance queue manager feature requires networked storage for the queue manager's data. This can be provided by a networked storage device (such as NAS) or a cluster file system. 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.

See Testing and support statement for WebSphere MQ multi-instance queue managers for further information.

When using NFS v4 on Solaris 10 SPARC, patch 147440-13 is required. This patch supersedes IDR 145513 revision 3 and patch 147268-01 which is no longer supported.

When using NFS v4 on Solaris 10 x86-64, patch 147441-13 is required. This patch supersedes IDR 145514 revision 3 and patch 147269-01 which is no longer supported.​

Virtualization. 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
• WebSphere MQ support position regarding Solaris zones
• Installing WebSphere MQ in AIX Workload Partitions
• Server Virtualization Policy for IBM Software

Solaris SPARC. Solaris operating environments: 64-bit SPARC 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.

Solaris x86-64 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.

WebSphere MQ requires a 64-bit kernel; 32-bit and 64-bit MQ APIs are supported.

Only supported using Java 1(6) or Java 1(7)

Only supported using Java 1(6) or Java 1(7)

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.

For more detailed information about using WebSphere MQ with application servers see the WebSphere MQ resource adapter statement of support document.

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

Solaris SPARC only.

Supported with WMQ used as a generic JMS provider.

Supported with WMQ used as a generic JMS provider.

Oracle WebLogic Server 11gR1 equals all versions 10.3.1 up to and including 10.3.6

Supported with WMQ used as a generic JMS provider.

See this document for more information.

See this document for more information.

See this document for more information.

Only supported on the Solaris SPARC platform.

Only supported on the Solaris SPARC platform.

Only supported on the Solaris SPARC platform.

Only supported on the Solaris SPARC platform.

Solaris x86-64: SSL/TLS 32-bit COBOL client applications are not FIPS 140-2 compliant.

C and C++.

Solaris x86-64: SSL/TLS 32-bit C and C++ client applications are not FIPS 140-2 compliant.

C and C++.

Solaris x86-64: SSL/TLS 32-bit C and C++ client applications are not FIPS 140-2 compliant.

C and C++.

Solaris x86-64: SSL/TLS 32-bit C and C++ client applications are not FIPS 140-2 compliant.

Only supported on the Solaris SPARC platform.

C and C++.

FIPS 140-2 compliance is only supported on IBM JREs.

32-bit and 64-bit support.

Transport for SOAP support on 32-bit only (Apache Axis 1.4) - commonly known as Axis 1

FIPS 140-2 compliance is only supported on IBM JREs.

Only if the JDK is supplied with another IBM product.

32-bit and 64-bit support.

Transport for SOAP support on 32-bit only (Apache Axis 1.4) - commonly known as Axis 1

FIPS 140-2 compliance is only supported on IBM JREs.

Only if the JDK is supplied with another IBM product.

32-bit and 64-bit support.

Transport for SOAP support on 32-bit only (Apache Axis 1.4) - commonly known as Axis 1

Fix pack 7.1.0.7 or later is required.

FIPS 140-2 compliance is only supported on IBM JREs.

Only if the JDK is supplied with another IBM product.

32-bit and 64-bit support.

Transport for SOAP support on 32-bit only (Apache Axis 1.4) - commonly known as Axis 1

32-bit and 64-bit support.

32-bit and 64-bit support.

32-bit and 64-bit support.

Fix pack 7.1.0.7 or later is required.

32-bit and 64-bit support.

Only supported on the Solaris SPARC platform.

SNA LU6.2 Services for Solaris.

Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ.

Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ.

Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ.

Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ.

Fix pack 6 or later is required.

Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java.

Fix pack 3 or later is required.

Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java.

Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java.

Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java.

Sybase Adapter Server Enterprise (ASE) is NOT supported by the WebSphere MQ classes for Java.

Sybase Adapter Server Enterprise (ASE) is NOT supported by the WebSphere MQ classes for Java.

Using the WebSphere MQ classes for JMS, WebSphere MQ can only act in the role of a Resource Manager. The WebSphere MQ classes for JMS can only participate in global transactions when accessed through the Java EE Connector Architecture (JCA) resource adapter, which can only be used with a suitable application server environment.

For more detailed information on the use of the resource adapter with application servers, see the Application Server section above, and the WebSphere MQ resource adapter statement of support document.

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

COM+/MTS provided with Microsoft Windows may also be used as a Transaction Manager.

Only supported on the Solaris SPARC  platform.

Only supported on the Solaris SPARC platform.

The resiliency feature of TXSeries is not supported. For more details, please refer to XA Resiliency feature of TXSeries doesn't work with WMQ as RM.

Only supported on the Solaris SPARC platform.

The resiliency feature of TXSeries is not supported. For more details, please refer to XA Resiliency feature of TXSeries doesn't work with WMQ as RM.

Refer to MQ 7.1 cryptographic hardware support for further information.

Required for Coexistence with WebSphere MQ V7.1.

The multi-instance queue manager feature requires networked storage (such as NAS) for the queue manager's data, accessed by the Common Internet File System (CIFS) protocol used by Microsoft Windows networks.

See Testing and support statement for WebSphere MQ multi-instance queue managers for further information.

Virtualization. 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
• WebSphere MQ support position regarding Solaris zones
• Installing WebSphere MQ in AIX Workload Partitions
• Server Virtualization Policy for IBM Software

x86 and x86-64 (also known as x64) technology-compatible PC hardware, 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. Note that Itanium 64-bit is not supported.

MQ classes for .NET 

Transport for SOAP

Message Service Client for .NET (XMS)

MQ classes for .NET 

Transport for SOAP

Message Service Client for .NET (XMS)

Windows Communication Foundation (WCF)

MQ classes for .NET 

Transport for SOAP

Message Service Client for .NET (XMS)

Windows Communication Foundation (WCF)

MQ classes for .NET 

Message Service Client for .NET (XMS)

Windows Communication Foundation (WCF)

MQ classes for .NET 

Message Service Client for .NET (XMS)

Windows Communication Foundation (WCF)

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.

For more detailed information about using WebSphere MQ with application servers see the WebSphere MQ resource adapter statement of support document.

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

Supported with WMQ used as a generic JMS provider.

Supported with WMQ used as a generic JMS provider.

Oracle WebLogic Server 11gR1 equals all versions 10.3.1 up to and including 10.3.6

Supported with WMQ used as a generic JMS provider.

See this document for more information.

See this document for more information.

See this document for more information.

Cobol.

ActiveX and Visual Basic support is only provided for WebSphere MQ V6.0 functionality

C and C++ applications

Transport for SOAP

MQ classes for .NET

Message Service Client for .NET (XMS)

C and C++ applications.

Transport for SOAP.

Windows Communication Foundation (WCF).

MQ classes for .NET.

Message Service Client for .NET (XMS).

C and C++ applications.

Windows Communication Foundation (WCF).

MQ classes for .NET.

Message Service Client for .NET (XMS).

C and .NET applications only supported, C++ is known not to work..

Windows Communication Foundation (WCF).

MQ classes for .NET.

Message Service Client for .NET (XMS).

C and .NET applications only supported, C++ is known not to work..

Windows Communication Foundation (WCF).

MQ classes for .NET.

Message Service Client for .NET (XMS).

FIPS 140-2 compliance is only supported on IBM JREs.

32-bit and 64-bit are supported.

Transport for SOAP support on 32-bit only (Apache Axis 1.4) - commonly known as Axis 1

Transport for SOAP support on 32-bit only (Apache Axis2 1.4 ) - commonly known as Axis2

FIPS 140-2 compliance is only supported on IBM JREs.

32-bit and 64-bit support.

Transport for SOAP support on 32-bit only (Apache Axis 1.4) - commonly known as Axis 1

Transport for SOAP support on 32-bit only (Apache Axis2 1.4 ) - commonly known as Axis2

FIPS 140-2 compliance is only supported on IBM JREs.

32-bit and 64-bit support.

Transport for SOAP support on 32-bit only (Apache Axis 1.4) - commonly known as Axis 1

Transport for SOAP support on 32-bit only (Apache Axis2 1.4 ) - commonly known as Axis2

Fix pack 7.10.7 is required.

FIPS 140-2 compliance is only supported on IBM JREs.

32-bit and 64-bit support.

Transport for SOAP support on 32-bit only (Apache Axis 1.4) - commonly known as Axis 1

Transport for SOAP support on 32-bit only (Apache Axis2 1.4 ) - commonly known as Axis2

32-bit and 64-bit support.

32-bit and 64-bit support.

32-bit and 64-bit support.

Fix pack 7.1.0.7 or later is required.

32-bit and 64-bit support.

Provides 64-bit support.

Part of IBM Host Access Client Package for Multi-Platforms (HACP) v7.

Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ.

Only 64-bit DB2 instances can be used with a 64-bit WebSphere MQ application.

Only 64-bit DB2 instances can be used with a 64-bit WebSphere MQ application.

Only 64-bit DB2 instances can be used with a 64-bit WebSphere MQ application.

Fix pack 6 or later is required.

Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java.

Fix pack 3 or later is required.

Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java.

Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java.

Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java.

Oracle 64-bit databases on Windows x64 require the 32-bit Oracle client

Oracle 64-bit databases on Windows x64 require the 32-bit Oracle client

Oracle 64-bit databases on Windows x64 require the 32-bit Oracle client

Oracle 64-bit databases on Windows x64 require the 32-bit Oracle client

Sybase Adapter Server Enterprise (ASE) is NOT supported by the WebSphere MQ classes for Java.

Sybase Adapter Server Enterprise (ASE) is NOT supported by the WebSphere MQ classes for Java.

For running .NET services.

Using the WebSphere MQ classes for JMS, WebSphere MQ can only act in the role of a Resource Manager. The WebSphere MQ classes for JMS can only participate in global transactions when accessed through the Java EE Connector Architecture (JCA) resource adapter, which can only be used with a suitable application server environment.

For more detailed information on the use of the resource adapter with application servers, see the Application Server section above, and the WebSphere MQ resource adapter statement of support document.

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

COM+/MTS provided with Microsoft Windows may also be used as a Transaction Manager.

The resiliency feature of TXSeries is not supported. For more details, please refer to
XA Resiliency feature of TXSeries doesn't work with WMQ as RM.

The resiliency feature of TXSeries is not supported. For more details, please refer to XA Resiliency feature of TXSeries doesn't work with WMQ as RM.

The WebSphere MQ V7.1 Telemetry feature operates on a subset of the WebSphere MQ supported environments. Please see the System Requirements for WebSphere MQ V7.1 Telemetry document for further information.

Refer to MQ 7.1 cryptographic hardware support for further information.

MQ Explorer is supported on the supported Windows platforms except Windows Embedded Point of Service (WEPOS).

MQ Explorer is supported when added to the following compatible Eclipse-based products:

• IBM Rational Application Developer for WebSphere Software V8.0.3 or later fix pack. 32-bit install only.

Please see notes in Other Hardware Section for detailed support statement.

Required for Coexistence with WebSphere MQ V7.1.