Product Documentation
Abstract
This document contains system requirements for WebSphere MQ V7.5 for Multiplatforms
Content
Outline
- Hardware Requirements
- Software Requirements
- Optional Supported Software
- Application Servers
- Application Servers for the WebSphere MQ Bridge for HTTP
- Compiler
- Databases
- Java Technology
- Network Communication
- Resource Managers (when MQ is the Transaction Manager)
- Software Integration
- 4690
- Transaction Manager
- Versions of products / components shipped with the product
- Virtualization
- WebSphere MQ
Group | Notes |
---|---|
Other Hardware | 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 a WebSphere MQ Managed File Transfer (MFT) Agent accesses files on a file system (for example when performing a file transfer), the underlying file system must be POSIX-compliant and support lease-based locking. This is also true when networked file systems are used. IBM's General Parallel File System (GPFS) and Network File System version 4 (NFS v4) both satisfy this requirement. Please note that earlier versions of NFS do NOT satisfy this requirement and must not be used with WebSphere MQ MFT. |
|
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: |
|
Processor | 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. |
Operating System | Notes |
---|---|
AIX Platform listing of supported OS | |
AIX 6.1 TL5 POWER System and future OS fix packs | 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 |
AIX 7.1 POWER System and future OS fix packs | 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 |
Group | Product | Notes |
---|---|---|
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. 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. 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 |
Oracle/BEA WebLogic Server 11g Release 1 | 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 |
Oracle WebLogic Server 12cR1 (12.1.1) | Supported with WMQ used as a generic JMS provider. |
|
WebSphere Application Server 6.1 and future fix packs (overview) (support) | See this document for more information. |
|
WebSphere Application Server 7.0 and future fix packs (overview) (support) | See this document for more information. |
|
WebSphere Application Server 8.0 and future mod levels and fix packs (overview) (support) | See this document for more information. |
|
WebSphere Application Server 8.5 and future mod levels and fix packs (overview) (support) | See this document for more information. |
|
WebSphere Application Server Liberty Profile 8.5.5 and future mod levels and fix packs | APAR IC92914 is a prerequisite, See This Document for more information |
|
Application Servers for the WebSphere MQ Bridge for HTTP | WebSphere Application Server 7.0.0.5 and future fix packs (overview) (support) | |
WebSphere Application Server 8.0 and future fix packs (overview) (support) | ||
WebSphere Application Server 8.5 and future fix packs (overview) (support) | ||
WebSphere Application Server Community Edition 2.1 and future fix packs (overview) (support) | ||
Compiler | COBOL for AIX 3.1 and future fix packs (overview) (support) | |
COBOL for AIX 4.1 and future fix packs (overview) (support) | ||
COBOL for AIX 4.1.1 and future fix packs (overview) (support) | ||
Micro Focus Server Express 5.1 and future fix packs | Cobol. |
|
XL C/C++ Enterprise Edition for AIX 8.0 and future fix packs (overview) (support) | ||
XL C/C++ Enterprise Edition for AIX 9.0 and future fix packs (overview) (support) | The minimum level of IBM XL C/C++ Enterprise Edition for AIX v9.0 is 9.0.0.3. |
|
XL C/C++ for AIX 10.1 and future fix packs (overview) (support) | ||
XL C/C++ for AIX 11.1 and future fix packs (overview) (support) | ||
XL C/C++ for AIX 12.x and future fix packs (overview) (support) | ||
XL C Enterprise Edition for AIX 8.0 and future fix packs (overview) (support) | ||
XL C Enterprise Edition for AIX 9.0 and future fix packs (overview) (support) | The minimum level of IBM XL C/C++ Enterprise Edition for AIX v9.0 is 9.0.0.3. |
|
XL C for AIX 10.1 and future fix packs (overview) (support) | ||
XL C for AIX 11.1 and future fix packs (overview) (support) | ||
XL C for AIX 12.1 and future fix packs (overview) (support) | ||
Databases Databases for use with WebSphere MQ Managed File Transfer component. When using a database with the Java EE 5 database logger or WebSphere MQ Managed File Transfer web gateway, you should ensure that the Java EE 5 runtime also supports this database product and level. |
||
DB2 Advanced Enterprise Server Edition 10.5 (overview) (support) | ||
DB2 Advanced Enterprise Server Edition 10.1 (overview) (support) | ||
DB2 Advanced Enterprise Server Edition 9.7 (overview) (support) | ||
DB2 Enterprise Server Edition 9.5 (overview) (support) | ||
Oracle Database 11g Standard/Enterprise Editions Release 1 | If using an Oracle version 11 JDBC driver with the Managed File Transfer logger, in database mode, the Oracle JDBC driver level is required to be 11.2.0.3. |
|
Oracle Database 11g Standard/Enterprise Editions Release 2 | If using an Oracle version 11 JDBC driver with the Managed File Transfer logger, in database mode, the Oracle JDBC driver level is required to be 11.2.0.3. |
|
Oracle Database 12c Standard/Enterprise Editions Release 1 | Fix pack 7.5.0.7 or later is required. When using Oracle 12.1 as a database logger in Managed File Transfer, Oracle JDBC driver version 12.1.0.1.0 is required. |
|
Java Technology For Java applications using the WebSphere MQ classes for Java or JMS. The MQ Java/JMS clients need to run in a full Java Runtime Environment, with all the function of a Java SE Environment. WebSphere MQ Advanced Message Security component policies are supported for Java applications using bindings on any supported Java runtime. Support for Java applications using client connections are limited to those running under a supported Java runtime. WebSphere MQ Managed File Transfer capabilities are only supported when used in conjunction with the Java environment supplied as part of the WebSphere MQ product. |
IBM Runtime Environment, Java Technology Edition 5.0 and future fix packs | FIPS 140-2 compliance is only supported on IBM JREs. AMS support for applications using client connections is only supported on IBM JRE. 32-bit and 64-bit are supported. Transport for SOAP support on 32-bit only (Apache Axis 1.4) - commonly known as Axis 1 |
IBM Runtime Environment, Java Technology Edition 6.0 and future fix packs | FIPS 140-2 compliance is only supported on IBM JREs. AMS support for applications using client connections is only supported on IBM JRE. 32-bit and 64-bit are supported. Transport for SOAP support on 32-bit only (Apache Axis 1.4) - commonly known as Axis 1 |
|
IBM Runtime Environment, Java Technology Edition 7.0 and future fix packs | FIPS 140-2 compliance is only supported on IBM JREs. AMS support for applications using client connections is only supported on IBM JRE. 32-bit and 64-bit are supported. Transport for SOAP support on 32-bit only (Apache Axis 1.4) - commonly known as Axis 1 |
|
IBM Runtime Environment, Java Technology Edition 8.0 and future fix packs | Fix pack 7.5.0.7 or later is required. AMS support for applications using client connections is not supported. 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 |
|
Network Communication TCP/IP: IPv4 and IPv6 provided by the operating system. SNA LU6.2: As specified opposite. NetBIOS: Provided with the operating system on Windows. SPX: Sequence Package Exchange provided with Windows XP and 2003 operating systems. FTP/FTPS/SFTP standards compliant server (UNIX or Windows style file format): Required to run the WebSphere MQ Managed File Transfer protocol bridge agent. |
Communications Server for AIX 6.3 and future fix packs (overview) (support) | SNA LU6.2 Services for AIX. |
Communications Server for AIX V6.4 and future fix packs (overview) (support) | SNA LU6.2 Services for AIX. |
|
Resource Managers (when MQ is the Transaction Manager) 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. Using the WebSphere MQ classes for Java, WebSphere MQ can act as a Transaction Co-ordinator, using the QMgr.begin() call. When using the WebSphere MQ classes for Java, WebSphere MQ can not act as a Resource Manager within a JTA transaction. |
DB2 Advanced Enterprise Server Edition 10.5 and future fix packs (overview) (support) | Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ. |
DB2 Advanced Enterprise Server Edition 10.1 and future fix packs (overview) (support) | Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ. |
|
DB2 Advanced Enterprise Server Edition 9.7 and future fix packs (overview) (support) | Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ. |
|
DB2 Enterprise Server Edition 9.5 and future fix packs (overview) (support) | Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ. |
|
Informix Client Software Development Kit 3.50 and future fix packs (overview) (support) | Fix pack 6 or later is required. |
|
Informix Client Software Development Kit 3.70.xC1 and future fix packs (overview) (support) | ||
Informix Client Software Development Kit 4.10 and future fix packs | ||
Informix Dynamic Server Enterprise Edition 11.10 and future fix packs | Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java. |
|
Informix Dynamic Server Enterprise Edition 11.50 and future fix packs | Fix pack 3 or later is required. Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java. |
|
Informix Dynamic Server Enterprise Edition 11.70 and future fix packs | Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java. |
|
Informix Dynamic Server 12.10 and future fix packs | Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java. |
|
Oracle Database 11g Standard/Enterprise Editions Release 1 | ||
Oracle Database 11g Standard/Enterprise Editions Release 2 | ||
Oracle Database 12c Standard/Enterprise Editions Release 1 | Fix Pack 5 or later is required if using JDBC. |
|
Oracle Database 12c Standard/Enterprise Editions Release 2 | Fix Pack 8 or later is required. Oracle Database 12c Standard/Enterprise Editions Release 2 is NOT supported by the WebSphere MQ classes for Java. |
|
Sybase Adaptive Server Enterprise 15.0 and future fix packs | Sybase Adapter Server Enterprise (ASE) is NOT supported by the WebSphere MQ classes for Java. |
|
Sybase Adaptive Server Enterprise 15.5 | Sybase Adapter Server Enterprise (ASE) is NOT supported by the WebSphere MQ classes for Java. |
|
Software Integration Prerequisite to transfer files to a Sterling Connect:Direct node as the source or destination of a transfer through the WebSphere Managed File Transfer Sterling Connect:Direct bridge component. This capability is only available on operating systems where WebSphere MQ Managed File Transfer component is supported. |
Sterling Connect:Direct for UNIX 4.1 and future fix packs (overview) (support) |
You may run a Sterling Connect:Direct bridge agent on the following operating systems:
The Sterling Connect:Direct bridge can transfer files to and from Sterling Connect:Direct nodes running on the following operating systems:
|
4690 From WebSphere MQ V7.5.0.2 onwards Manager File Transfer supports IBM 4690 as a client platform. |
IBM 4690 Operating System Release Version 6 Release 2 | Supported version of Java: IBM Runtime Environment, Java Technology Edition 6.0 and future fix packs |
IBM 4690 Operating System Release Version 6 Release 3 | Supported version of Java: IBM Runtime Environment, Java Technology Edition 6.0 and future fix packs |
|
Transaction Manager 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. |
Oracle Tuxedo 10.3 and future fix packs | |
Oracle Tuxedo 11g R1 | ||
Oracle Tuxedo 12c R1 | ||
TXSeries for Multiplatforms V6.2 and future fix packs (overview) (support) | The resiliency feature of TXSeries is not supported. For more details, please refer to |
|
TXSeries for Multiplatforms V7.1.0.0 and future fix packs (overview) (support) | 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. |
TXSeries for Multiplatforms V8.1.0.0 and future fix packs | WMQ 7.5.0.3 is required 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. |
TXSeries for Multiplatforms V8.2.0.0 and future fix packs | WMQ 7.5.0.8 is required 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. |
|
WebSphere Application Server 6.1 and future releases, mod levels and fix packs (overview) (support) | ||
Versions of products / components shipped with the product | IBM Global Security Kit (GSKit) 8.0.0.n and future mod levels and fix packs | Refer to MQ 7.5 cryptographic hardware support for further information. |
WebSphere MQ Telemetry 7.5 (overview) (support) | The WebSphere MQ V7.5 Telemetry feature operates on a subset of the WebSphere MQ supported environments. Please see the System Requirements for WebSphere MQ V7.5 Telemetry document for further information. |
|
Virtualization |
Please see notes in Other Hardware Section for detailed support statement. |
|
WebSphere MQ For multiple installations of WebSphere MQ to coexist they must be at a specific level, or above. In a coexistence environment there may be multiple installations of V7.1, or above, but only one may be at V7.0.1. |
WebSphere MQ 7.0.1.6 and future fix packs (overview) (support) | |
WebSphere MQ 7.1 and future fix packs (overview) (support) |
Outline
- Hardware Requirements
- Software Requirements
- Optional Supported Software
- Application Servers
- Application Servers for the WebSphere MQ Bridge for HTTP
- Compiler
- Databases
- Java Technology
- Network Communication
- Resource Managers (when MQ is the Transaction Manager)
- Software Integration
- 4690
- Transaction Manager
- Versions of products / components shipped with the product
- WebSphere MQ
Group | Notes |
---|---|
Other Hardware | 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. |
When a WebSphere MQ Managed File Transfer (MFT) Agent accesses files on a file system (for example when performing a file transfer), the underlying file system must be POSIX-compliant and support lease-based locking. This is also true when networked file systems are used. IBM's General Parallel File System (GPFS) and Network File System version 4 (NFS v4) both satisfy this requirement. Please note that earlier versions of NFS do NOT satisfy this requirement and must not be used with WebSphere MQ MFT. |
|
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: |
|
Processor | 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 |
Operating System | Notes |
---|---|
HP Platform listing of supported OS | |
HP-UX 11i v3 IA64 and future OS fix packs |
Before installing on HP-UX 11i v3 (11.31) see technote 1270591 |
Group | Product | Notes |
---|---|---|
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. 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. 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 |
Oracle/BEA WebLogic Server 11g Release 1 | 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 |
Oracle WebLogic Server 12cR1 (12.1.1) | Supported with WMQ used as a generic JMS provider. |
|
WebSphere Application Server 6.1 and future fix packs (overview) (support) | See this document for more information. |
|
WebSphere Application Server 7.0 and future fix packs (overview) (support) | See this document for more information. |
|
WebSphere Application Server 8.0 and future mod levels and fix packs (overview) (support) | See this document for more information. |
|
WebSphere Application Server 8.5 and future mod levels and fix packs (overview) (support) | See this document for more information. |
|
WebSphere Application Server Liberty Profile 8.5.5 and future mod levels and fix packs | APAR IC92914 is a prerequisite, See This Document for more information |
|
Application Servers for the WebSphere MQ Bridge for HTTP | WebSphere Application Server 7.0.0.5 and future fix packs (overview) (support) | |
WebSphere Application Server 8.0 and future fix packs (overview) (support) | ||
WebSphere Application Server 8.5 and future fix packs (overview) (support) | ||
WebSphere Application Server Community Edition 2.1 and future fix packs (overview) (support) | ||
Compiler | HP aCC A.06.16 and future fix packs | 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. |
Micro Focus Server Express 5.1 and future fix packs | Cobol. |
|
Databases Databases for use with WebSphere MQ Managed File Transfer component. When using a database with the Java EE 5 database logger or WebSphere MQ Managed File Transfer web gateway, you should ensure that the Java EE 5 runtime also supports this database product and level. |
||
DB2 Advanced Enterprise Server Edition 10.5 (overview) (support) | ||
DB2 Advanced Enterprise Server Edition 10.1 (overview) (support) | ||
DB2 Advanced Enterprise Server Edition 9.7 (overview) (support) | ||
DB2 Enterprise Server Edition 9.5 (overview) (support) | ||
Oracle Database 11g Standard/Enterprise Editions Release 2 | If using an Oracle version 11 JDBC driver with the Managed File Transfer logger, in database mode, the Oracle JDBC driver level is required to be 11.2.0.3. |
|
Oracle Database 12c Standard/Enterprise Editions Release 1 | Fix pack 7.5.0.7 or later is required. When using Oracle 12.1 as a database logger in Managed File Transfer, Oracle JDBC driver version 12.1.0.1.0 is required. |
|
Java Technology For Java applications using the WebSphere MQ classes for Java or JMS. The MQ Java/JMS clients need to run in a full Java Runtime Environment, with all the function of a Java SE Environment. WebSphere MQ Advanced Message Security component policies are supported for Java applications using bindings on any supported Java runtime. Support for Java applications using client connections are limited to those running under a supported Java runtime. WebSphere MQ Managed File Transfer capabilities are only supported when used in conjunction with the Java environment supplied as part of the WebSphere MQ product. |
HP Java SDK/JRE/JDK 5.0 and future mod levels and fix packs | 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. |
HP Java SDK/JRE/JDK 6.0 and future mod levels and fix packs | 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. |
|
HP Java SDK/JRE/JDK 7.0 and future fix packs | 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. |
|
HP Java SDK/JRE/JDK 8.0 and future fix packs | Fix pack 7.5.0.7 or later is required. AMS support for applications using client connections is not supported. 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. |
|
IBM Runtime Environment, Java Technology Edition 5.0.10 and future mod levels and fix packs | 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. AMS support for applications using client connections is only supported on IBM JRE. 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 |
|
IBM Runtime Environment, Java Technology Edition 6.0 and future fix packs | 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. AMS support for applications using client connections is only supported on IBM JRE. 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 |
|
IBM Runtime Environment, Java Technology Edition 7.0 and future fix packs | 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. AMS support for applications using client connections is only supported on IBM JRE. 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 |
|
IBM Runtime Environment, Java Technology Edition 8.0 and future fix packs | Fix pack 7.5.0.7 or later is required. This is the IBM-modified version of the HP SDK for J2SE HP-UX 11i platform. AMS support for applications using client connections is not supported. 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 |
|
Network Communication TCP/IP: IPv4 and IPv6 provided by the operating system. SNA LU6.2: As specified opposite. NetBIOS: Provided with the operating system on Windows. SPX: Sequence Package Exchange provided with Windows XP and 2003 operating systems. FTP/FTPS/SFTP standards compliant server (UNIX or Windows style file format): Required to run the WebSphere MQ Managed File Transfer protocol bridge agent. |
HP SNAplus2 7.0 | SNA LU6.2 Services for HP. |
Resource Managers (when MQ is the Transaction Manager) 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. Using the WebSphere MQ classes for Java, WebSphere MQ can act as a Transaction Co-ordinator, using the QMgr.begin() call. When using the WebSphere MQ classes for Java, WebSphere MQ can not act as a Resource Manager within a JTA transaction. |
DB2 Advanced Enterprise Server Edition 10.5 and future fix packs (overview) (support) | Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ. |
DB2 Advanced Enterprise Server Edition 10.1 and future fix packs (overview) (support) | Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ. |
|
DB2 Advanced Enterprise Server Edition 9.7 and future fix packs (overview) (support) | Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ. |
|
DB2 Enterprise Server Edition 9.5 and future fix packs (overview) (support) | Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ. |
|
Informix Client Software Development Kit 3.50 and future fix packs (overview) (support) | Fix pack 6 or later is required. |
|
Informix Client Software Development Kit 3.70.xC1 and future fix packs (overview) (support) | ||
Informix Client Software Development Kit 4.10 and future fix packs | ||
Informix Dynamic Server Enterprise Edition 11.10 and future fix packs | Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java. |
|
Informix Dynamic Server Enterprise Edition 11.50 and future fix packs | Fix pack 3 or later is required. Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java. |
|
Informix Dynamic Server Enterprise Edition 11.70 and future fix packs | Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java. |
|
Informix Dynamic Server 12.10 and future fix packs | Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java. |
|
Oracle Database 11g Standard/Enterprise Editions Release 2 | ||
Oracle Database 12c Standard/Enterprise Editions Release 1 | Fix Pack 5 or later is required if using JDBC. |
|
Oracle Database 12c Standard/Enterprise Editions Release 2 | Fix Pack 8 or later is required. Oracle Database 12c Standard/Enterprise Editions Release 2 is NOT supported by the WebSphere MQ classes for Java. |
|
Sybase Adaptive Server Enterprise 15.0 and future fix packs | Sybase Adapter Server Enterprise (ASE) is NOT supported by the WebSphere MQ classes for Java. |
|
Software Integration Prerequisite to transfer files to a Sterling Connect:Direct node as the source or destination of a transfer through the WebSphere Managed File Transfer Sterling Connect:Direct bridge component. This capability is only available on operating systems where WebSphere MQ Managed File Transfer component is supported. |
Sterling Connect:Direct for UNIX 4.1 and future fix packs (overview) (support) |
You may run a Sterling Connect:Direct bridge agent on the following operating systems:
The Sterling Connect:Direct bridge can transfer files to and from Sterling Connect:Direct nodes running on the following operating systems:
|
4690 From WebSphere MQ V7.5.0.2 onwards Manager File Transfer supports IBM 4690 as a client platform. |
IBM 4690 Operating System Release Version 6 Release 2 | Supported version of Java: IBM Runtime Environment, Java Technology Edition 6.0 and future fix packs |
IBM 4690 Operating System Release Version 6 Release 3 | Supported version of Java: IBM Runtime Environment, Java Technology Edition 6.0 and future fix packs |
|
Transaction Manager 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. |
Oracle Tuxedo 10.3 | |
Oracle Tuxedo 11g R1 | ||
Oracle Tuxedo 12c R1 | ||
TXSeries for Multiplatforms V6.2 and future fix packs (overview) (support) | The resiliency feature of TXSeries is not supported. For more details, please refer to |
|
TXSeries for Multiplatforms V7.1.0.0 and future fix packs (overview) (support) | 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. |
TXSeries for Multiplatforms V8.1.0.0 and future fix packs | WMQ 7.5.0.3 is required 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. |
TXSeries for Multiplatforms V8.2.0.0 and future fix packs | WMQ 7.5.0.8 is required 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. |
|
WebSphere Application Server 6.1 and future releases, mod levels and fix packs (overview) (support) | ||
Versions of products / components shipped with the product | IBM Global Security Kit (GSKit) 8.0.0.n and future mod levels and fix packs | Refer to MQ 7.5 cryptographic hardware support for further information. |
WebSphere MQ For multiple installations of WebSphere MQ to coexist they must be at a specific level, or above. In a coexistence environment there may be multiple installations of V7.1, or above, but only one may be at V7.0.1. |
WebSphere MQ 7.0.1.6 and future fix packs (overview) (support) | |
WebSphere MQ 7.1 and future fix packs (overview) (support) |
Tab navigation
- IBM Retail Environment for SUSE Linux
- Red Flag
- Red Hat Enterprise Linux (RHEL)
- Red Hat Enterprise Linux (RHEL) Server
- SUSE Linux Enterprise Point of Service (NLPOS/SLEPOS)
- SUSE Linux Enterprise Server (SLES)
- Ubuntu
Outline
- Hardware Requirements
- Software Requirements
- Optional Supported Software
- Application Servers
- Application Servers for the WebSphere MQ Bridge for HTTP
- Application Servers for WebSphere MQ Managed File Transfer component
- Compiler
- Databases
- Java Technology
- Network Communication
- Resource Managers (when MQ is the Transaction Manager)
- Software Integration
- 4690
- Transaction Manager
- Versions of products / components shipped with the product
- Virtualization
- Cloud Platform
- Web Browsers
- WebSphere MQ
Group | Notes |
---|---|
Other Hardware | 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 a WebSphere MQ Managed File Transfer (MFT) Agent accesses files on a file system (for example when performing a file transfer), the underlying file system must be POSIX-compliant and support lease-based locking. This is also true when networked file systems are used. IBM's General Parallel File System (GPFS) and Network File System version 4 (NFS v4) both satisfy this requirement. Please note that earlier versions of NFS do NOT satisfy this requirement and must not be used with WebSphere MQ MFT. |
|
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: |
|
Processor | 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.
|
Operating System | Notes |
---|---|
Linux Platform listing of supported OS | |
IBM Retail Environment for SUSE Linux v2 x86-32 and future OS fix packs | WebSphere MQ Managed File Transfer and WebSphere MQ Advanced Message Security components are not supported on this platform. |
Red Flag 5.0 DC Server x86-32 and future OS fix packs | WebSphere MQ Managed File Transfer and WebSphere MQ Advanced Message Security components are not supported on this platform. |
Red Hat Enterprise Linux (RHEL) 5 Advanced Platform POWER System and future OS fix packs | SELinux must be disabled. |
Red Hat Enterprise Linux (RHEL) 5 Advanced Platform System z and future OS fix packs | SELinux must be disabled. |
Red Hat Enterprise Linux (RHEL) 5 Advanced Platform x86-32 and future OS fix packs | SELinux must be disabled. |
Red Hat Enterprise Linux (RHEL) 5 Advanced Platform x86-64 and future OS fix packs | SELinux must be disabled. |
Red Hat Enterprise Linux (RHEL) Server 5 POWER System and future OS fix packs | SELinux must be disabled. |
Red Hat Enterprise Linux (RHEL) Server 5 System z and future OS fix packs | SELinux must be disabled. |
Red Hat Enterprise Linux (RHEL) Server 5 x86-32 and future OS fix packs | SELinux must be disabled. |
Red Hat Enterprise Linux (RHEL) Server 5 x86-64 and future OS fix packs | SELinux must be disabled. |
Red Hat Enterprise Linux (RHEL) Server 6 POWER System and future OS fix packs | For versions older than 7.5.0.4, SELinux must be disabled. For 7.5.0.4 and later fix packs SELinux may be enabled. If SELinux is enabled then it must be configured as described in the MQ SELinux support requirements. |
Red Hat Enterprise Linux (RHEL) Server 6 System z and future OS fix packs | For versions older than 7.5.0.4, SELinux must be disabled. For 7.5.0.4 and later fix packs SELinux may be enabled. If SELinux is enabled then it must be configured as described in the MQ SELinux support requirements. |
Red Hat Enterprise Linux (RHEL) Server 6 x86-32 and future OS fix packs | For versions older than 7.5.0.4, SELinux must be disabled. For 7.5.0.4 and later fix packs SELinux may be enabled. If SELinux is enabled then it must be configured as described in the MQ SELinux support requirements. |
Red Hat Enterprise Linux (RHEL) Server 6 x86-64 and future OS fix packs | For versions older than 7.5.0.4, SELinux must be disabled. For 7.5.0.4 and later fix packs SELinux may be enabled. If SELinux is enabled then it must be configured as described in the MQ SELinux support requirements. |
Red Hat Enterprise Linux (RHEL) Server 7 POWER System and future OS fix packs | For versions older than 7.5.0.5, SELinux must be disabled. For 7.5.0.5 and later fix packs SELinux may be enabled. If SELinux is enabled then it must be configured as described in the MQ SELinux support requirements. |
Red Hat Enterprise Linux (RHEL) Server 7 System z and future OS fix packs | For versions older than 7.5.0.5, SELinux must be disabled. For 7.5.0.5 and later fix packs SELinux may be enabled. If SELinux is enabled then it must be configured as described in the MQ SELinux support requirements. |
Red Hat Enterprise Linux (RHEL) Server 7 x86-32 and future OS fix packs | For versions older than 7.5.0.5, SELinux must be disabled. For 7.5.0.5 and later fix packs SELinux may be enabled. If SELinux is enabled then it must be configured as described in the MQ SELinux support requirements. |
Red Hat Enterprise Linux (RHEL) Server 7 x86-64 and future OS fix packs | For versions older than 7.5.0.5, SELinux must be disabled. For 7.5.0.5 and later fix packs SELinux may be enabled. If SELinux is enabled then it must be configured as described in the MQ SELinux support requirements. |
SUSE Linux Enterprise Point of Service (NLPOS/SLEPOS) 11 x86-32 and future OS fix packs | WebSphere MQ Managed File Transfer and WebSphere MQ Advanced Message Security components are not supported on this platform. |
SUSE Linux Enterprise Server (SLES) 10 SP1 POWER System and future OS fix packs | |
SUSE Linux Enterprise Server (SLES) 10 SP1 System z and future OS fix packs | |
SUSE Linux Enterprise Server (SLES) 10 SP3 x86-32 and future OS fix packs | |
SUSE Linux Enterprise Server (SLES) 10 SP3 x86-64 and future OS fix packs | |
SUSE Linux Enterprise Server (SLES) 11 POWER System and future OS fix packs | |
SUSE Linux Enterprise Server (SLES) 11 System z and future OS fix packs | |
SUSE Linux Enterprise Server (SLES) 11 x86-32 and future OS fix packs | |
SUSE Linux Enterprise Server (SLES) 11 x86-64 and future OS fix packs | |
SUSE Linux Enterprise Server (SLES) 12 System z and future OS fix packs | (7.5.0.5 needed) |
SUSE Linux Enterprise Server (SLES) 12 x86-64 and future OS fix packs | (7.5.0.5 needed) |
Ubuntu 10.04 LTS x86-32 and future OS fix packs | (7.5.0.2 needed) 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. |
Ubuntu 12.04 LTS x86-32 and future OS fix packs | (7.5.0.2 needed) 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. |
Ubuntu 10.04 LTS x86-64 and future OS fix packs | (7.5.0.2 needed) 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. |
Ubuntu 12.04 LTS x86-64 and future OS fix packs | (7.5.0.2 needed) 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. |
Group | Product | Notes |
---|---|---|
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. 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. 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 |
Oracle/BEA WebLogic Server 10g Release 3 10.3 and future fix packs | Linux for System x (x86-64) platforms only. Supported with WMQ used as a generic JMS provider. |
Oracle/BEA WebLogic Server 11g Release 1 | 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 |
|
Oracle WebLogic Server 12cR1 (12.1.1) | Linux for System x platforms only. Supported with WMQ used as a generic JMS provider. |
|
WebSphere Application Server 6.1 and future fix packs (overview) (support) | See this document for more information. |
|
WebSphere Application Server 7.0 and future fix packs (overview) (support) | See this document for more information. |
|
WebSphere Application Server 8.0 and future mod levels and fix packs (overview) (support) | See this document for more information. |
|
WebSphere Application Server 8.5 and future mod levels and fix packs (overview) (support) | See this document for more information. |
|
WebSphere Application Server Liberty Profile 8.5.5 and future mod levels and fix packs | APAR IC92914 is a prerequisite, See This Document for more information |
|
Application Servers for the WebSphere MQ Bridge for HTTP | WebSphere Application Server 7.0.0.5 (overview) (support) | Only supported on the Linux for System p and Linux for System x. |
WebSphere Application Server 8.0 and future fix packs (overview) (support) | Only supported on the Linux for System p and Linux for System x. |
|
WebSphere Application Server 8.5 and future fix packs (overview) (support) | Only supported on the Linux for System p and Linux for System x. |
|
WebSphere Application Server Community Edition 2.1 and future fix packs (overview) (support) | Only supported on Linux for System p and Linux for System x. |
|
Application Servers for WebSphere MQ Managed File Transfer component This capability is only available on operating systems where WebSphere MQ Managed File Transfer component is supported. |
WebSphere Application Server 7.0.0.11 and future fix packs (overview) (support) | |
WebSphere Application Server Community Edition 2.1 (overview) (support) | You must apply APAR IC72511 to WebSphere MQ before installing the WebSphere MQ JCA Resource Adapter. |
|
WebSphere Application Server - Express 7.0.0.11 and future fix packs (overview) (support) | ||
Compiler | GNU C Compiler (gcc) and g++ 4.1.2 and future fix packs | 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. |
GNU C Compiler (gcc) and g++ 4.3 and future fix packs | 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. |
|
GNU C Compiler (gcc) and g++ 4.4.4 and future fix packs | Only supported on RHEL 6 and RHEL 7. 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. |
|
Micro Focus Server Express 5.1 and future fix packs | Cobol. |
|
Databases Databases for use with WebSphere MQ Managed File Transfer component. When using a database with the Java EE 5 database logger or WebSphere MQ Managed File Transfer web gateway, you should ensure that the Java EE 5 runtime also supports this database product and level. |
||
DB2 Advanced Enterprise Server Edition 10.5 (overview) (support) | ||
DB2 Advanced Enterprise Server Edition 10.1 (overview) (support) | ||
DB2 Advanced Enterprise Server Edition 9.7 (overview) (support) | ||
DB2 Enterprise Server Edition 9.5 (overview) (support) | ||
Oracle Database 10g Standard Edition Release 2 | Only supported on Linux for System p and Linux for System z. If using an Oracle version 11 JDBC driver with the Managed File Transfer logger, in database mode, the Oracle JDBC driver level is required to be 11.2.0.3. |
|
Oracle Database 11g Standard/Enterprise Editions Release 1 | Only supported on Linux for System x. If using an Oracle version 11 JDBC driver with the Managed File Transfer logger, in database mode, the Oracle JDBC driver level is required to be 11.2.0.3. |
|
Oracle Database 11g Standard/Enterprise Editions Release 2 | Only supported on Linux for System x. If using an Oracle version 11 JDBC driver with the Managed File Transfer logger, in database mode, the Oracle JDBC driver level is required to be 11.2.0.3. |
|
Oracle Database 12c Standard/Enterprise Editions Release 1 | Fix pack 7.5.0.7 or later is required. When using Oracle 12.1 as a database logger in Managed File Transfer, Oracle JDBC driver version 12.1.0.1.0 is required. |
|
Java Technology For Java applications using the WebSphere MQ classes for Java or JMS. The MQ Java/JMS clients need to run in a full Java Runtime Environment, with all the function of a Java SE Environment. WebSphere MQ Advanced Message Security component policies are supported for Java applications using bindings on any supported Java runtime. Support for Java applications using client connections are limited to those running under a supported Java runtime. WebSphere MQ Managed File Transfer capabilities are only supported when used in conjunction with the Java environment supplied as part of the WebSphere MQ product. |
IBM Runtime Environment, Java Technology Edition 5.0.10 and future mod levels and fix packs | Only supported if the SDK is supplied with another IBM product. FIPS 140-2 compliance is only supported on IBM JREs. AMS support for applications using client connections is only supported on IBM JRE. 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:
64-bit SDK is supported on:
|
IBM Runtime Environment, Java Technology Edition 6.0 and future fix packs | Only supported if the SDK is supplied with another IBM product. FIPS 140-2 compliance is only supported on IBM JREs. AMS support for applications using client connections is only supported on IBM JRE. 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:
64-bit SDK is supported on:
|
|
IBM Runtime Environment, Java Technology Edition 7.0 and future fix packs | Only supported if the SDK is supplied with another IBM product. FIPS 140-2 compliance is only supported on IBM JREs. AMS support for applications using client connections is only supported on IBM JRE. 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:
64-bit SDK is supported on:
|
IBM Runtime Environment, Java Technology Edition 8.0 and future fix packs | Fix pack 7.5.0.7 or later is required. AMS support for applications using client connections is not supported. 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
32-bit SDK is supported on::
64-bit SDK is supported on:
|
Oracle Java SDK/JRE/JDK 7.0.5 | 32-bit SDK is supported on:
64-bit SDK is supported on:
|
|
Oracle Java SDK/JRE/JDK 8.0 | Fix pack 7.5.0.7 or later is required. AMS support for applications using client connections is not supported. 32-bit SDK is supported on:
64-bit SDK is supported on:
|
|
Oracle JRockit 6 | Only supported on Linux for System x. Only supported when being used in conjunction with Oracle/BEA WebLogic Server. 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 |
|
Sun Java SDK/JRE/JDK 5.0/1.5 | 32-bit SDK is supported on:
64-bit SDK is supported on:
|
|
Sun Java SDK/JRE/JDK 6.0/1.6 | 32-bit SDK is supported on:
64-bit SDK is supported on:
|
|
Resource Managers (when MQ is the Transaction Manager) 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. Using the WebSphere MQ classes for Java, WebSphere MQ can act as a Transaction Co-ordinator, using the QMgr.begin() call. When using the WebSphere MQ classes for Java, WebSphere MQ can not act as a Resource Manager within a JTA transaction. |
DB2 Advanced Enterprise Server Edition 10.5 and future fix packs (overview) (support) | Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ. |
DB2 Advanced Enterprise Server Edition 10.1 and future fix packs (overview) (support) | Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ. |
|
DB2 Advanced Enterprise Server Edition 9.7 and future fix packs (overview) (support) | Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ. |
|
DB2 Enterprise Server Edition 9.5 and future fix packs (overview) (support) | Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ. |
|
Informix Client Software Development Kit 3.50 and future fix packs (overview) (support) | Fix pack 6 or later is required. |
|
Informix Client Software Development Kit 3.70.xC1 and future fix packs (overview) (support) | ||
Informix Client Software Development Kit 4.10 and future fix packs | ||
Informix Dynamic Server Enterprise Edition 11.10 and future fix packs | Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java. |
|
Informix Dynamic Server Enterprise Edition 11.50 and future fix packs | Fix pack 3 or later is required. Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java. |
|
Informix Dynamic Server Enterprise Edition 11.70 and future fix packs | Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java. |
|
Informix Dynamic Server 12.10 and future fix packs | Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java. |
|
Oracle Database 10g Standard Edition Release 2 and future fix packs | Only supported on Linux for System p and Linux for System z. |
|
Oracle Database 11g Standard/Enterprise Editions Release 1 | Only supported on Linux for System x. |
|
Oracle Database 11g Standard/Enterprise Editions Release 2 | Only supported on Linux for System x and System z. |
|
Oracle Database 12c Standard/Enterprise Editions Release 1 | Only supported on Linux for System x and System z. Fix Pack 5 or later is required if using JDBC. |
|
Oracle Database 12c Standard/Enterprise Editions Release 2 | Fix Pack 8 or later is required. Only supported on Linux for System x and System z. Oracle Database 12c Standard/Enterprise Editions Release 2 is NOT supported by the WebSphere MQ classes for Java. |
|
Sybase Adaptive Server Enterprise 15.0 | 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. |
|
Sybase Adaptive Server Enterprise 15.5 | 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. |
|
Software Integration Prerequisite to transfer files to a Sterling Connect:Direct node as the source or destination of a transfer through the WebSphere Managed File Transfer Sterling Connect:Direct bridge component. This capability is only available on operating systems where WebSphere MQ Managed File Transfer component is supported. |
Sterling Connect:Direct for UNIX 4.1 and future fix packs (overview) (support) | Only supported on the Linux for System p and Linux for System z. You may run a Sterling Connect:Direct bridge agent on the following operating systems:
The Sterling Connect:Direct bridge can transfer files to and from Sterling Connect:Direct nodes running on the following operating systems:
|
4690 From WebSphere MQ V7.5.0.2 onwards Manager File Transfer supports IBM 4690 as a client platform. |
IBM 4690 Operating System Release Version 6 Release 2 | Supported version of Java: IBM Runtime Environment, Java Technology Edition 6.0 and future fix packs |
IBM 4690 Operating System Release Version 6 Release 3 | Supported version of Java: IBM Runtime Environment, Java Technology Edition 6.0 and future fix packs |
|
Transaction Manager 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. |
Oracle Tuxedo 10.3 | Only supported on Linux for System x |
Oracle Tuxedo 11g R1 | Only supported on Linux for System x |
|
Oracle Tuxedo 12c R1 | Only supported on Linux for System x |
|
TXSeries for Multiplatforms V8.1.0.0 and future fix packs InterimServiceFix1 must be applied | WMQ 7.5.0.3 is required 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. |
|
TXSeries for Multiplatforms V8.2.0.0 and future fix packs | WMQ 7.5.0.8 is required 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. |
|
WebSphere Application Server 6.1 and future releases, mod levels and fix packs (overview) (support) | ||
Versions of products / components shipped with the product | IBM Global Security Kit (GSKit) 8.0.0.n | Refer to MQ 7.1 cryptographic hardware support for further information. 32-bit only support on:
32-bit and 64-bit support on:
|
WebSphere MQ Explorer 7.5 (overview) (support) | MQ Explorer is only supported on x86-32 and x86-64 platforms MQ Explorer is not supported on the following x86 platforms:
MQ Explorer is supported when added to the following compatible Eclipse-based products:
|
|
WebSphere MQ Telemetry 7.5 (overview) (support) | The WebSphere MQ V7.5 Telemetry feature operates on a subset of the WebSphere MQ supported environments. Please see the System Requirements for WebSphere MQ V7.5 Telemetry document for further information. |
|
Virtualization |
|
Please see notes in Other Hardware Section for detailed support statement. |
Cloud Platform Supported cloud products, in addition to the virtualization notes at the top of the page. |
Microsoft Azure | WebSphere MQ 7.5.0.4 or later required All RHEL, SUSE, x86-64 operating systems which are supported by Websphere MQ 7.5.0.4 and above are supported as guest operating systems. The WebSphere MQ image is available in the Microsoft Azure catalog http://azure.microsoft.com |
Web Browsers Supported web browsers for WebSphere MQ Managed File Transfer web gateway administrative console and sample web application. |
Mozilla Firefox 3.0 and future mod levels and fix packs | Only supported version 3.0 - 3.5. |
WebSphere MQ For multiple installations of WebSphere MQ to coexist they must be at a specific level, or above. In a coexistence environment there may be multiple installations of V7.1, or above, but only one may be at V7.0.1. |
WebSphere MQ 7.0.1.6 and future fix packs (overview) (support) | |
WebSphere MQ 7.1 and future fix packs (overview) (support) |
Outline
- Hardware Requirements
- Software Requirements
- Optional Supported Software
- Application Servers
- Application Servers for the WebSphere MQ Bridge for HTTP
- Compiler
- Databases
- Java Technology
- Network Communication
- Resource Managers (when MQ is the Transaction Manager)
- Software Integration
- 4690
- Transaction Manager
- Versions of products / components shipped with the product
- WebSphere MQ
Group | Notes |
---|---|
Other Hardware | 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 |
When a WebSphere MQ Managed File Transfer (MFT) Agent accesses files on a file system (for example when performing a file transfer), the underlying file system must be POSIX-compliant and support lease-based locking. This is also true when networked file systems are used. IBM's General Parallel File System (GPFS) and Network File System version 4 (NFS v4) both satisfy this requirement. Please note that earlier versions of NFS do NOT satisfy this requirement and must not be used with WebSphere MQ MFT. |
|
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: |
|
Processor | 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. |
Operating System | Notes | ||
---|---|---|---|
Solaris Platform listing of supported OS | |||
Solaris 10 SPARC and future OS fix packs | WebSphere MQ Telemetry is not supported on this platform. |
||
Solaris 10 x86-64 and future OS fix packs | WebSphere MQ Telemetry is not supported on this platform. |
||
Solaris 11 SPARC and future OS fix packs | Only supported using Java 1(6) or Java 1(7) WebSphere MQ Telemetry is not supported on this platform. |
||
Solaris 11 x86-64 and future OS fix packs | Only supported using Java 1(6) or Java 1(7) WebSphere MQ Telemetry is not supported on this platform. |
Group | Product | Notes |
---|---|---|
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. 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. 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 |
Oracle/BEA WebLogic Server 10g Release 3 10.3 | Solaris SPARC only. Supported with WMQ used as a generic JMS provider. |
Oracle/BEA WebLogic Server 11g Release 1 | 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 |
|
Oracle WebLogic Server 12cR1 (12.1.1) | Supported with WMQ used as a generic JMS provider. |
|
WebSphere Application Server 6.1 and future fix packs (overview) (support) | See this document for more information. |
|
WebSphere Application Server 7.0 and future fix packs (overview) (support) | See this document for more information. |
|
WebSphere Application Server 8.0 and future mod levels and fix packs (overview) (support) | See this document for more information. |
|
WebSphere Application Server 8.5 and future mod levels and fix packs (overview) (support) | See this document for more information. |
|
WebSphere Application Server Liberty Profile 8.5.5 and future mod levels and fix packs | APAR IC92914 is a prerequisite, See This Document for more information |
|
Application Servers for the WebSphere MQ Bridge for HTTP | WebSphere Application Server 7.0.0.5 and future fix packs (overview) (support) | Only supported on the Solaris SPARC platform. |
WebSphere Application Server 8.0 and future fix packs (overview) (support) | Only supported on the Solaris SPARC platform. |
|
WebSphere Application Server 8.5 and future fix packs (overview) (support) | Only supported on the Solaris SPARC platform. |
|
WebSphere Application Server Community Edition 2.1 and future fix packs (overview) (support) | Only supported on the Solaris SPARC platform. |
|
Compiler | Micro Focus Server Express 5.1 and future fix packs | Solaris x86-64: SSL/TLS 32-bit COBOL client applications are not FIPS 140-2 compliant. |
Sun Studio 12 | C and C++. Solaris x86-64: SSL/TLS 32-bit C and C++ client applications are not FIPS 140-2 compliant. |
|
Sun Studio 10, C++ Compiler 5.7 and future fix packs | C and C++. Solaris x86-64: SSL/TLS 32-bit C and C++ client applications are not FIPS 140-2 compliant. |
|
Sun Studio 11, C++ Compiler 5.8 and future fix packs | C and C++. Solaris x86-64: SSL/TLS 32-bit C and C++ client applications are not FIPS 140-2 compliant. |
|
Sun Studio 9, C++ Compiler 5.6 and future fix packs | Only supported on the Solaris SPARC platform. C and C++. |
|
Databases Databases for use with WebSphere MQ Managed File Transfer component. When using a database with the Java EE 5 database logger or WebSphere MQ Managed File Transfer web gateway, you should ensure that the Java EE 5 runtime also supports this database product and level. |
||
DB2 Advanced Enterprise Server Edition 10.5 (overview) (support) | ||
DB2 Advanced Enterprise Server Edition 10.1 (overview) (support) | ||
DB2 Advanced Enterprise Server Edition 9.7 (overview) (support) | ||
DB2 Enterprise Server Edition 9.5 (overview) (support) | ||
Oracle Database 11g Standard/Enterprise Editions Release 1 | If using an Oracle version 11 JDBC driver with the Managed File Transfer logger, in database mode, the Oracle JDBC driver level is required to be 11.2.0.3. |
|
Oracle Database 11g Standard/Enterprise Editions Release 2 | If using an Oracle version 11 JDBC driver with the Managed File Transfer logger, in database mode, the Oracle JDBC driver level is required to be 11.2.0.3. |
|
Oracle Database 12c Standard/Enterprise Editions Release 1 | Fix pack 7.5.0.7 or later is required. When using Oracle 12.1 as a database logger in Managed File Transfer, Oracle JDBC driver version 12.1.0.1.0 is required. |
|
Java Technology For Java applications using the WebSphere MQ classes for Java or JMS. The MQ Java/JMS clients need to run in a full Java Runtime Environment, with all the function of a Java SE Environment. WebSphere MQ Advanced Message Security component policies are supported for Java applications using bindings on any supported Java runtime. Support for Java applications using client connections are limited to those running under a supported Java runtime. WebSphere MQ Managed File Transfer capabilities are only supported when used in conjunction with the Java environment supplied as part of the WebSphere MQ product. |
IBM Runtime Environment, Java Technology Edition 5.0.1 and future fix packs | FIPS 140-2 compliance is only supported on IBM JREs. AMS support for applications using client connections is only supported on IBM JRE. 32-bit and 64-bit support. Transport for SOAP support on 32-bit only (Apache Axis 1.4) - commonly known as Axis 1 |
IBM Runtime Environment, Java Technology Edition 6.0 and future fix packs | FIPS 140-2 compliance is only supported on IBM JREs. AMS support for applications using client connections is only supported on IBM JRE. 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 |
|
IBM Runtime Environment, Java Technology Edition 7.0 and future fix packs | FIPS 140-2 compliance is only supported on IBM JREs. AMS support for applications using client connections is only supported on IBM JRE. 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 |
|
IBM Runtime Environment, Java Technology Edition 8.0 and future fix packs | Fix pack 7.5.0.7 or later is required. AMS support for applications using client connections is not supported. 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 |
|
Oracle Java SDK/JRE/JDK 7.0.5 | 32-bit and 64-bit support. |
|
Oracle Java SDK/JRE/JDK 8.0 | Fix pack 7.5.0.7 or later is required. 32-bit and 64-bit support. AMS support for applications using client connections is not supported. |
|
Oracle JRockit 6 | Only supported on the Solaris SPARC platform. Only supported when being used in conjunction with Oracle/BEA WebLogic server. |
|
Sun Java SDK/JRE/JDK 5.0/1.5 | 32-bit and 64-bit support. |
|
Sun Java SDK/JRE/JDK 6.0/1.6 | 32-bit and 64-bit support. |
|
Network Communication TCP/IP: IPv4 and IPv6 provided by the operating system. SNA LU6.2: As specified opposite. NetBIOS: Provided with the operating system on Windows. SPX: Sequence Package Exchange provided with Windows XP and 2003 operating systems. FTP/FTPS/SFTP standards compliant server (UNIX or Windows style file format): Required to run the WebSphere MQ Managed File Transfer protocol bridge agent. |
Data Connection SNAP-IX 7.0 | Only supported on the Solaris SPARC platform. SNA LU6.2 Services for Solaris. |
Resource Managers (when MQ is the Transaction Manager) 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. Using the WebSphere MQ classes for Java, WebSphere MQ can act as a Transaction Co-ordinator, using the QMgr.begin() call. When using the WebSphere MQ classes for Java, WebSphere MQ can not act as a Resource Manager within a JTA transaction. |
DB2 Advanced Enterprise Server Edition 10.5 and future fix packs (overview) (support) | Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ. |
DB2 Advanced Enterprise Server Edition 10.1 and future fix packs (overview) (support) | Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ. |
|
DB2 Advanced Enterprise Server Edition 9.7 and future fix packs (overview) (support) | Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ. |
|
DB2 Enterprise Server Edition 9.5 and future fix packs (overview) (support) | Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ. |
|
Informix Client Software Development Kit 3.50 and future fix packs (overview) (support) | Fix pack 6 or later is required. |
|
Informix Client Software Development Kit 3.70.xC1 and future fix packs (overview) (support) | ||
Informix Client Software Development Kit 4.10 and future fix packs | ||
Informix Dynamic Server Enterprise Edition 11.10 and future fix packs | Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java. |
|
Informix Dynamic Server Enterprise Edition 11.50 and future fix packs | Fix pack 3 or later is required. Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java. |
|
Informix Dynamic Server Enterprise Edition 11.70 and future fix packs | Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java. |
|
Informix Dynamic Server 12.10 and future fix packs | Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java. |
|
Oracle Database 11g Standard/Enterprise Editions Release 1 | ||
Oracle Database 11g Standard/Enterprise Editions Release 2 | ||
Oracle Database 12c Standard/Enterprise Editions Release 1 | Fix Pack 5 or later is required if using JDBC. |
|
Oracle Database 12c Standard/Enterprise Editions Release 2 | Fix Pack 8 or later is required. Oracle Database 12c Standard/Enterprise Editions Release 2 is NOT supported by the WebSphere MQ classes for Java. |
|
Sybase Adaptive Server Enterprise 15.0 and future fix packs | Sybase Adapter Server Enterprise (ASE) is NOT supported by the WebSphere MQ classes for Java. |
|
Sybase Adaptive Server Enterprise 15.5 | Sybase Adapter Server Enterprise (ASE) is NOT supported by the WebSphere MQ classes for Java. |
|
Software Integration Prerequisite to transfer files to a Sterling Connect:Direct node as the source or destination of a transfer through the WebSphere Managed File Transfer Sterling Connect:Direct bridge component. This capability is only available on operating systems where WebSphere MQ Managed File Transfer component is supported. |
Sterling Connect:Direct for UNIX 4.1 and future fix packs (overview) (support) |
You may run a Sterling Connect:Direct bridge agent on the following operating systems:
The Sterling Connect:Direct bridge can transfer files to and from Sterling Connect:Direct nodes running on the following operating systems:
|
4690 From WebSphere MQ V7.5.0.2 onwards Manager File Transfer supports IBM 4690 as a client platform. |
IBM 4690 Operating System Release Version 6 Release 2 | Supported version of Java: IBM Runtime Environment, Java Technology Edition 6.0 and future fix packs |
IBM 4690 Operating System Release Version 6 Release 3 | Supported version of Java: IBM Runtime Environment, Java Technology Edition 6.0 and future fix packs |
|
Transaction Manager 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. |
Oracle Tuxedo 10.3 | Only supported on the Solaris SPARC platform. |
Oracle Tuxedo 11g R1 | ||
Oracle Tuxedo 12c R1 | ||
TXSeries for Multiplatforms V6.2 and future releases, mod levels and fix packs (overview) (support) | 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. |
|
TXSeries for Multiplatforms V7.1.0.0 and future releases, mod levels and fix packs (overview) (support) | 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. |
TXSeries for Multiplatforms V8.1.0.0 and future fix packs | WMQ 7.5.0.3 is required 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. |
TXSeries for Multiplatforms V8.2.0.0 and future fix packs | WMQ 7.5.0.8 is required 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. |
|
WebSphere Application Server 6.1 and future releases, mod levels and fix packs (overview) (support) | ||
Versions of products / components shipped with the product | IBM Global Security Kit (GSKit) 8.0.0.n and future mod levels and fix packs | Refer to MQ 7.5 cryptographic hardware support for further information. |
WebSphere MQ For multiple installations of WebSphere MQ to coexist they must be at a specific level, or above. In a coexistence environment there may be multiple installations of V7.1, or above, but only one may be at V7.0.1. |
WebSphere MQ 7.0.1.6 and future fix packs (overview) (support) | |
WebSphere MQ 7.1 and future fix packs (overview) (support) |
Tab navigation
- Windows 7
- Windows 8
- Windows 8.1
- Windows Embedded Point of Service (WEPOS)
- Windows Server 2003
- Windows Server 2008
- Windows Server 2012
- Windows Server 2012 R2
- Windows Vista
- Windows XP
Outline
- Hardware Requirements
- Software Requirements
- Optional Supported Software
- .NET
- Application Servers
- Application Servers for the WebSphere MQ Bridge for HTTP
- Application Servers for WebSphere MQ Managed File Transfer component
- Compiler
- Databases
- Java Technology
- Network Communication
- Resource Managers (when MQ is the Transaction Manager)
- SOAP Support
- Software Integration
- 4690
- Transaction Manager
- Versions of products / components shipped with the product
- Virtualization
- Cloud Platform
- Web Browsers
- WebSphere MQ
Group | Notes |
---|---|
Other Hardware | 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. |
When a WebSphere MQ Managed File Transfer (MFT) Agent accesses files on a file system (for example when performing a file transfer), the underlying file system must be POSIX-compliant and support lease-based locking. This is also true when networked file systems are used. IBM's General Parallel File System (GPFS) and Network File System version 4 (NFS v4) both satisfy this requirement. Please note that earlier versions of NFS do NOT satisfy this requirement and must not be used with WebSphere MQ MFT. |
|
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: |
|
Processor | 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. |
Operating System | Notes | |
---|---|---|
Windows Platform listing of supported OS | ||
Windows 7 Enterprise x86-32 | ||
Windows 7 Enterprise x86-64 | ||
Windows 7 Professional x86-32 | ||
Windows 7 Professional for Embedded Systems x86-32 and future OS fix packs | WebSphere MQ Managed File Transfer and WebSphere MQ Advanced Message Security components are not supported on this platform. | |
Windows 7 Professional x86-64 | ||
Windows 7 Ultimate x86-32 | ||
Windows 7 Ultimate x86-64 | ||
Windows 8 Enterprise x86-32 and future OS fix packs | To support Windows 8 you must install the 7.5.0.1 manufacturing refresh of MQ 7.5 and cannot simply install 7.5.0.0 and apply a CSD to take it to 7.5.0.1 | |
Windows 8 Enterprise x86-64 and future OS fix packs | To support Windows 8 you must install the 7.5.0.1 manufacturing refresh of MQ 7.5 and cannot simply install 7.5.0.0 and apply a CSD to take it to 7.5.0.1 | |
Windows 8 Professional x86-32 and future OS fix packs | To support Windows 8 you must install the 7.5.0.1 manufacturing refresh of MQ 7.5 and cannot simply install 7.5.0.0 and apply a CSD to take it to 7.5.0.1 | |
Windows 8 Professional x86-64 and future OS fix packs | To support Windows 8 you must install the 7.5.0.1 manufacturing refresh of MQ 7.5 and cannot simply install 7.5.0.0 and apply a CSD to take it to 7.5.0.1 | |
Windows 8.1 Enterprise x86-32 and future OS fix packs | To support Windows 8.1 you must install the 7.5.0.1 manufacturing refresh of MQ 7.5 and cannot simply install 7.5.0.0 and apply a CSD to take it to 7.5.0.1 | |
Windows 8.1 Enterprise x86-64 and future OS fix packs | To support Windows 8.1 you must install the 7.5.0.1 manufacturing refresh of MQ 7.5 and cannot simply install 7.5.0.0 and apply a CSD to take it to 7.5.0.1 | |
Windows 8.1 Professional x86-32 and future OS fix packs | To support Windows 8.1 you must install the 7.5.0.1 manufacturing refresh of MQ 7.5 and cannot simply install 7.5.0.0 and apply a CSD to take it to 7.5.0.1 | |
Windows 8.1 Professional x86-64 and future OS fix packs | To support Windows 8.1 you must install the 7.5.0.1 manufacturing refresh of MQ 7.5 and cannot simply install 7.5.0.0 and apply a CSD to take it to 7.5.0.1 | |
Windows Embedded Point of Service (WEPOS) 1.0 x86-32 and future OS fix packs | WebSphere MQ Managed File Transfer and WebSphere MQ Advanced Message Security components are not supported on this platform. | |
Windows Server 2003 R2 Enterprise Edition x86-32 and future OS fix packs | ||
Windows Server 2003 R2 Enterprise Edition x86-64 and future OS fix packs | ||
Windows Server 2003 R2 Standard Edition x86-32 and future OS fix packs | ||
Windows Server 2003 R2 Standard Edition x86-64 and future OS fix packs | ||
Windows Server 2003 SP1 Enterprise Edition x86-32 and future OS fix packs | ||
Windows Server 2003 SP1 Enterprise Edition x86-64 and future OS fix packs | ||
Windows Server 2003 SP1 Standard Edition x86-32 and future OS fix packs | ||
Windows Server 2003 SP1 Standard Edition x86-64 and future OS fix packs | ||
Windows Server 2008 Datacenter Edition x86-64 and future OS fix packs | ||
Windows Server 2008 R2 Datacenter Edition x86-64 and future OS fix packs | ||
Windows Server 2008 Enterprise Edition x86-32 | ||
Windows Server 2008 Enterprise Edition x86-64 | ||
Windows Server 2008 R2 Enterprise Edition x86-64 and future OS fix packs | ||
Windows Server 2008 R2 Standard Edition x86-64 and future OS fix packs | ||
Windows Server 2008 Standard Edition x86-32 | ||
Windows Server 2008 Standard Edition x86-64 | ||
Windows Server 2012 Standard Edition x86-64 and future OS fix packs | To support Windows 2012 Server you must install the 7.5.0.1 manufacturing refresh of MQ 7.5 and cannot simply install 7.5.0.0 and apply a CSD to take it to 7.5.0.1. Limitations exist when using MQ 7.5 with Microsoft Cluster Service on Windows Server 2012. Please see the following technote for more information: http://www-01.ibm.com/support/docview.wss?uid=swg21903498 |
|
Windows Server 2012 Datacenter Edition x86-64 and future OS fix packs | To support Windows 2012 Server you must install the 7.5.0.1 manufacturing refresh of MQ 7.5 and cannot simply install 7.5.0.0 and apply a CSD to take it to 7.5.0.1. Limitations exist when using MQ 7.5 with Microsoft Cluster Service on Windows Server 2012. Please see the following technote for more information: http://www-01.ibm.com/support/docview.wss?uid=swg21903498 |
|
Windows Server 2012 R2 Standard Edition x86-64 and future OS fix packs | To support Windows 2012 Server R2 you must install the 7.5.0.1 manufacturing refresh of MQ 7.5 and cannot simply install 7.5.0.0 and apply a CSD to take it to 7.5.0.1. Limitations exist when using MQ 7.5 with Microsoft Cluster Service on Windows Server 2012 R2. Please see the following technote for more information: http://www-01.ibm.com/support/docview.wss?uid=swg21903498 |
|
Windows Server 2012 R2 Datacenter Edition x86-64 and future OS fix packs | To support Windows 2012 R2 Server you must install the 7.5.0.1 manufacturing refresh of MQ 7.5 and cannot simply install 7.5.0.0 and apply a CSD to take it to 7.5.0.1. Limitations exist when using MQ 7.5 with Microsoft Cluster Service on Windows Server 2012 R2. Please see the following technote for more information: http://www-01.ibm.com/support/docview.wss?uid=swg21903498 |
|
Windows Vista Business x86-32 | ||
Windows Vista Business x86-64 | ||
Windows Vista Enterprise x86-32 | ||
Windows Vista Enterprise x86-64 | ||
Windows Vista Ultimate x86-32 | ||
Windows Vista Ultimate x86-64 | ||
Windows XP Professional x86-64 | ||
Windows XP SP2 Professional x86-32 and future OS fix packs |
Group | Product | Notes |
---|---|---|
.NET WebSphere MQ Advanced Message Security component is not fully supported in fully managed .NET applications. |
Microsoft .NET Framework 2.0 and future fix packs | MQ classes for .NET Transport for SOAP Message Service Client for .NET (XMS) |
Microsoft .NET Framework 3.0 and future fix packs | MQ classes for .NET Transport for SOAP Message Service Client for .NET (XMS) Windows Communication Foundation (WCF) |
|
Microsoft .NET Framework 3.5 and future fix packs | MQ classes for .NET Transport for SOAP Message Service Client for .NET (XMS) Windows Communication Foundation (WCF) |
|
Microsoft .NET Framework 4.0 and future fix packs | MQ classes for .NET Message Service Client for .NET (XMS) Windows Communication Foundation (WCF) |
|
Microsoft .NET Framework 4.5 and future fix packs | MQ classes for .NET Message Service Client for .NET (XMS) Windows Communication Foundation (WCF) |
|
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. 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. 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 |
Oracle/BEA WebLogic Server 10g Release 3 10.3 | Supported with WMQ used as a generic JMS provider. |
Oracle/BEA WebLogic Server 11g Release 1 | 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 |
|
Oracle WebLogic Server 12cR1 (12.1.1) | Supported with WMQ used as a generic JMS provider. |
|
WebSphere Application Server 6.1 and future fix packs (overview) (support) | See this document for more information. |
|
WebSphere Application Server 7.0 and future fix packs (overview) (support) | See this document for more information. |
|
WebSphere Application Server 8.0 and future mod levels and fix packs (overview) (support) | See this document for more information. |
|
WebSphere Application Server 8.5 and future mod levels and fix packs (overview) (support) | See this document for more information. |
|
WebSphere Application Server Liberty Profile 8.5.5 and future mod levels and fix packs | APAR IC92914 is a prerequisite, See This Document for more information |
|
Application Servers for the WebSphere MQ Bridge for HTTP | WebSphere Application Server 7.0.0.5 and future fix packs (overview) (support) | |
WebSphere Application Server 8.0 and future fix packs (overview) (support) | ||
WebSphere Application Server 8.5 and future fix packs (overview) (support) | ||
WebSphere Application Server Community Edition 2.1 and future fix packs (overview) (support) | ||
Application Servers for WebSphere MQ Managed File Transfer component This capability is only available on operating systems where WebSphere MQ Managed File Transfer component is supported. |
WebSphere Application Server 7.0.0.11 and future fix packs (overview) (support) | |
WebSphere Application Server Community Edition 2.1 (overview) (support) | You must apply APAR IC72511 to WebSphere MQ before installing the WebSphere MQ JCA Resource Adapter. |
|
WebSphere Application Server - Express 7.0.0.11 and future fix packs (overview) (support) | ||
Compiler | Micro Focus Server Express 5.1 and future fix packs | Cobol. |
Microsoft Visual Basic 6 | ActiveX and Visual Basic support is only provided for WebSphere MQ V6.0 functionality |
|
Microsoft Visual Studio 2005 and future fix packs | C and C++ applications Transport for SOAP MQ classes for .NET Message Service Client for .NET (XMS) |
|
Microsoft Visual Studio 2008 and future fix packs | C and C++ applications. Transport for SOAP. Windows Communication Foundation (WCF). MQ classes for .NET. Message Service Client for .NET (XMS). |
|
Microsoft Visual Studio 2010 and future fix packs | C and C++ applications. Windows Communication Foundation (WCF). MQ classes for .NET. Message Service Client for .NET (XMS). |
|
Microsoft Visual Studio 2012 and future fix packs | 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). |
|
Microsoft Visual Studio 2013 and future fix packs | 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). |
|
Databases Databases for use with WebSphere MQ Managed File Transfer component. When using a database with the Java EE 5 database logger or WebSphere MQ Managed File Transfer web gateway, you should ensure that the Java EE 5 runtime also supports this database product and level. |
||
DB2 Advanced Enterprise Server Edition 10.5 (overview) (support) | Only 64-bit DB2 instances can be used with a 64-bit WebSphere MQ application. |
|
DB2 Advanced Enterprise Server Edition 10.1 (overview) (support) | Only 64-bit DB2 instances can be used with a 64-bit WebSphere MQ application. |
|
DB2 Advanced Enterprise Server Edition 9.7 (overview) (support) | Only 64-bit DB2 instances can be used with a 64-bit WebSphere MQ application. |
|
DB2 Enterprise Server Edition 9.5 and future fix packs (overview) (support) | Only 64-bit DB2 instances can be used with a 64-bit WebSphere MQ application. |
|
Oracle Database 11g Standard/Enterprise Editions Release 1 | If using an Oracle version 11 JDBC driver with the Managed File Transfer logger, in database mode, the Oracle JDBC driver level is required to be 11.2.0.3. |
|
Oracle Database 11g Standard/Enterprise Editions Release 2 | If using an Oracle version 11 JDBC driver with the Managed File Transfer logger, in database mode, the Oracle JDBC driver level is required to be 11.2.0.3. |
|
Oracle Database 12c Standard/Enterprise Editions Release 1 | Fix pack 7.5.0.7 or later is required. When using Oracle 12.1 as a database logger in Managed File Transfer, Oracle JDBC driver version 12.1.0.1.0 is required. |
|
Java Technology For Java applications using the WebSphere MQ classes for Java or JMS. The MQ Java/JMS clients need to run in a full Java Runtime Environment, with all the function of a Java SE Environment. WebSphere MQ Advanced Message Security component policies are supported for Java applications using bindings on any supported Java runtime. Support for Java applications using client connections are limited to those running under a supported Java runtime. WebSphere MQ Managed File Transfer capabilities are only supported when used in conjunction with the Java environment supplied as part of the WebSphere MQ product. |
IBM Runtime Environment, Java Technology Edition 5.0 and future fix packs | FIPS 140-2 compliance is only supported on IBM JREs. AMS support for applications using client connections is only supported on IBM JRE. 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 |
IBM Runtime Environment, Java Technology Edition 6.0 and future fix packs | FIPS 140-2 compliance is only supported on IBM JREs. AMS support for applications using client connections is only supported on IBM JRE. 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 |
|
IBM Runtime Environment, Java Technology Edition 7.0 and future fix packs | FIPS 140-2 compliance is only supported on IBM JREs. AMS support for applications using client connections is only supported on IBM JRE. 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 |
|
IBM Runtime Environment, Java Technology Edition 8.0 and future fix packs | Fix pack 7.5.0.7 or later is required. AMS support for applications using client connections is not supported. 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 |
|
Oracle Java SDK/JRE/JDK 7.0.5 | 32-bit and 64-bit support. |
|
Oracle Java SDK/JRE/JDK 8.0 | Fix pack 7.5.0.7 or later is required. 32-bit and 64-bit support. AMS support for applications using client connections is not supported. |
|
Oracle JRockit 6 | Only supported when being used in conjunction with Oracle/BEA WebLogic server. |
|
Sun Java SDK/JRE/JDK 5.0 update 1 | 32-bit and 64-bit support. |
|
Sun Java SDK/JRE/JDK 6.0/1.6 | 32-bit and 64-bit support. |
|
Network Communication TCP/IP: IPv4 and IPv6 provided by the operating system. SNA LU6.2: As specified opposite. NetBIOS: Provided with the operating system on Windows. SPX: Sequence Package Exchange provided with Windows XP and 2003 operating systems. FTP/FTPS/SFTP standards compliant server (UNIX or Windows style file format): Required to run the WebSphere MQ Managed File Transfer protocol bridge agent. |
IBM Communications Server 6.1.2 and future fix packs | |
Microsoft Host Integration Server 2009 | ||
Microsoft Host Integration Server 2010 and future fix packs | Provides 64-bit support. |
|
Personal Communications 6.0 and future fix packs (overview) (support) | Part of IBM Host Access Client Package for Multi-Platforms (HACP) v7. |
|
Resource Managers (when MQ is the Transaction Manager) 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. Using the WebSphere MQ classes for Java, WebSphere MQ can act as a Transaction Co-ordinator, using the QMgr.begin() call. When using the WebSphere MQ classes for Java, WebSphere MQ can not act as a Resource Manager within a JTA transaction. |
DB2 Advanced Enterprise Server Edition 10.5 and future fix packs (overview) (support) | Only 64-bit DB2 instances can be used with a 64-bit WebSphere MQ application. |
DB2 Advanced Enterprise Server Edition 10.1 and future fix packs (overview) (support) | Only 64-bit DB2 instances can be used with a 64-bit WebSphere MQ application. |
|
DB2 Advanced Enterprise Server Edition 9.7 and future fix packs (overview) (support) | Only 64-bit DB2 instances can be used with a 64-bit WebSphere MQ application. |
|
DB2 Enterprise Server Edition 9.5 and future fix packs (overview) (support) | Only 64-bit DB2 instances can be used with a 64-bit WebSphere MQ application. |
|
Informix Client Software Development Kit 3.50 and future fix packs (overview) (support) | Fix pack 6 or later is required. |
|
Informix Client Software Development Kit 3.70.xC1 and future fix packs (overview) (support) | ||
Informix Client Software Development Kit 4.10 and future fix packs | ||
Informix Dynamic Server Enterprise Edition 11.10 and future fix packs | Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java. |
|
Informix Dynamic Server Enterprise Edition 11.50 and future fix packs | Fix pack 3 or later is required. Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java. |
|
Informix Dynamic Server Enterprise Edition 11.70 and future fix packs | Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java. |
|
Informix Dynamic Server 12.10 and future fix packs | Informix Dynamic Server (IDS) is NOT supported by the WebSphere MQ classes for Java. |
|
Oracle Database 11g Standard/Enterprise Editions Release 1 | Oracle 64-bit databases on Windows x64 require the 32-bit Oracle client. |
|
Oracle Database 11g Standard/Enterprise Editions Release 2 | Oracle 64-bit databases on Windows x64 require the 32-bit Oracle client. |
|
Oracle Database 12c Standard/Enterprise Edition2 Release 1 | Oracle 64-bit databases on Windows x64 require the 32-bit Oracle client. Fix Pack 5 or later and APAR IT10748 is required if using JDBC. |
|
Oracle Database 12c Standard/Enterprise Editions Release 2 | Fix Pack 8 or later is required. Oracle Database 12c Standard/Enterprise Editions Release 2 is NOT supported by the WebSphere MQ classes for Java. |
|
Sybase Adaptive Server Enterprise 15.0 and future fix packs | Sybase Adapter Server Enterprise (ASE) is NOT supported by the WebSphere MQ classes for Java. |
|
Sybase Adaptive Server Enterprise 15.5 | Sybase Adapter Server Enterprise (ASE) is NOT supported by the WebSphere MQ classes for Java. |
|
SOAP Support | Microsoft Internet Information Services 5.1 and future releases, mod levels and fix packs | For running .NET services. |
Software Integration Prerequisite to transfer files to a Sterling Connect:Direct node as the source or destination of a transfer through the WebSphere Managed File Transfer Sterling Connect:Direct bridge component. This capability is only available on operating systems where WebSphere MQ Managed File Transfer component is supported. |
Sterling Connect:Direct for Microsoft Windows 4.6 and future fix packs (overview) (support) | You may run a Sterling Connect:Direct bridge agent on the following operating systems:
The Sterling Connect:Direct bridge can transfer files to and from Sterling Connect:Direct nodes running on the following operating systems:
|
4690 From WebSphere MQ V7.5.0.2 onwards Manager File Transfer supports IBM 4690 as a client platform. |
IBM 4690 Operating System Release Version 6 Release 2 | Supported version of Java: IBM Runtime Environment, Java Technology Edition 6.0 and future fix packs |
IBM 4690 Operating System Release Version 6 Release 3 | Supported version of Java: IBM Runtime Environment, Java Technology Edition 6.0 and future fix packs |
|
Transaction Manager 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. |
Oracle Tuxedo 10.3 and future fix packs | |
Oracle Tuxedo 11g R1 | ||
Oracle Tuxedo 12c R1 | ||
TXSeries for Multiplatforms V6.2 and future fix packs (overview) (support) | The resiliency feature of TXSeries is not supported. For more details, please refer to |
|
TXSeries for Multiplatforms V7.1.0.0 and future fix packs (overview) (support) | 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. |
TXSeries for Multiplatforms V8.1.0.0 and future fix packs | WMQ 7.5.0.3 is required 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. |
TXSeries for Multiplatforms V8.2.0.0 and future fix packs | WMQ 7.5.0.8 is required 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. |
|
WebSphere Application Server 6.1 and future releases, mod levels and fix packs (overview) (support) | ||
Versions of products / components shipped with the product | IBM Global Security Kit (GSKit) 8.0.0.n and future mod levels and fix packs | Refer to MQ 7.5 cryptographic hardware support for further information. |
WebSphere MQ Explorer 7.5 (overview) (support) | 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:
|
|
WebSphere MQ Telemetry 7.5 (overview) (support) | The WebSphere MQ V7.5 Telemetry feature operates on a subset of the WebSphere MQ supported environments. Please see the System Requirements for WebSphere MQ V7.5 Telemetry document for further information. |
|
Virtualization |
|
Please see notes in Other Hardware Section for detailed support statement. |
Cloud Platform Supported cloud products, in addition to the virtualization notes at the top of the page. |
Microsoft Azure | WebSphere MQ 7.5.0.4 or later required All Windows x86-64 operating systems which are supported by Websphere MQ 7.5.0.4 and above are supported as guest operating systems. The WebSphere MQ image is available in the Microsoft Azure catalog http://azure.microsoft.com |
Web Browsers Supported web browsers for WebSphere MQ Managed File Transfer web gateway administrative console and sample web application. |
Microsoft Internet Explorer 7.0 | |
Mozilla Firefox 3.0 and future mod levels and fix packs | Only supported version 3.0 - 3.5. |
|
WebSphere MQ For multiple installations of WebSphere MQ to coexist they must be at a specific level, or above. In a coexistence environment there may be multiple installations of V7.1, or above, but only one may be at V7.0.1. |
WebSphere MQ 7.0.1.6 and future fix packs (overview) (support) | |
WebSphere MQ 7.1 and future fix packs (overview) (support) |
Notes
Original Publication Date
15 June 2012
Product Synonym
WMQ MQ
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg27027462