System Requirements for WebSphere MQ V7.0/7.0.1 on Windows

Product documentation


Abstract

This document contains the system requirements for WebSphere MQ V7.0 on Windows.

Content

Please read first
  • The 'MQ Explorer' tooling will run on all supported Windows environments. Where used in a 64-bit windows environment, it will run in 32-bit mode only.
  • Defect support is available for virtualization environments (for VMware see here) where they relate to releases of this platform already supported by WebSphere MQ. Unless stated elsewhere in the system requirements, WebSphere MQ has not been specifically tested in virtualization environments. WebSphere MQ Support is therefore unable to assist in issues related to configuration and setup, or issues that are directly related to the virtualization environment itself.
Hardware requirements
  • 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 Systems
  • Microsoft Windows XP Professional (SP2 or later)
  • Microsoft Windows XP Professional x64 Edition
  • Microsoft Windows 7 (Professional, Business, Enterprise or Ultimate, 32-bit and 64-bit Editions) [see section note 2]
  • Microsoft Windows Server 2003 (SP1 or later) (Standard Edition or Enterprise Edition)
  • Microsoft Windows Server 2003 (SP1 or later) (Standard x64 Edition or Enterprise x64 Edition)
  • Microsoft Windows Server 2003 R2 (SP1 or later) (Standard Edition or Enterprise Edition)
  • Microsoft Windows Server 2003 R2 (SP1 or later) (Standard x64 Edition or Enterprise x64 Edition)
  • Microsoft Windows Server 2008 (Standard or Enterprise 32-bit and 64-bit Edition) [see section note 1]
  • Microsoft Windows Server 2008 R2 (Standard or Enterprise 64-bit Edition) [see section note 2]
  • Microsoft Windows Vista (Business, Enterprise or Ultimate Edition, 32-bit and 64-bit Editions)
  • Microsoft Windows Embedded Point of Service 1.0

Notes:
  1. WebSphere MQ V7.0.0.2 or later is required.
  2. WebSphere MQ V7.0.1 or later is required.
For C/C++ applications
  • Microsoft Visual Studio C++ 2005
  • Microsoft Visual Studio 2008
  • Microsoft Visual Studio 2010 [see section note 1]
  • Microsoft Visual Studio 2012 [see section note 2]

Notes:
  1. WebSphere MQ V7.0.1.4 or later is required.
  2. C and .NET applications only supported, C++ is known not to work.
For COBOL applications
For Java™ applications using the WebSphere MQ classes for Java or JMS 32-bit:
  • Java 2 Platform, Standard Edition (J2SE) V1.4.2 from Sun Microsystems, Inc.
  • Java 2 Platform, Standard Edition V5.0 (SR1 or above) from Sun Microsystems, Inc.
  • Java 2 Platform, Standard Edition V6.0 from Sun Microsystems, Inc.
  • Oracle Java SDK/JRE/JDK 7.0.5 [see section note 3]
  • IBM 32-bit SDK for Windows, Java 2 Technology Edition, V1.4.2 [see section notes 1 and 2]
  • IBM 32-bit SDK for Windows, Java 2 Technology Edition, V5.0 (SR1 or above) [see section note 1 and 2]
  • IBM 32-bit SDK for Windows, Java Technology Edition, V6.0 [see section notes 1 and 2]
  • IBM Runtime Environment, Java Technology Edition 7.0 and future Fix Packs.[see section notes 1,2 and 3]
64-bit:
  • Sun Java 2 Platform Standard Edition, Version 5.0
  • Sun Java 2 Platform Standard Edition, Version 6.0
  • Oracle Java SDK/JRE/JDK 7.0.5 [see section note 3]
  • IBM 64-bit SDK for WindowsAMD64/EM64T architecture, Java 2 Technology Edition, V1.4.2 [see section note 1 and 2]
  • IBM 64-bit SDK for Windows AMD64/EM64T architecture, Java 2 Technology Edition, V5.0 [see section note 2]
  • IBM 64-bit SDK for Windows AMD64/EM64T architecture, Java Technology Edition, V6.0 [see section note 1 and 2]
  • IBM Runtime Environment, Java Technology Edition 7.0 and future Fix Packs.[see section notes 1,2 and 3]

Notes:
  1. Only if the JDK is supplied with another IBM product.
  2. FIPS 140-2 compliance is only supported on IBM SDKs.
  3. WebSphere MQ V7.0.1.6 or later is required.
For .NET applications
  • Microsoft .NET Framework V2.0
  • Microsoft .NET Framework V3.0
  • Microsoft .NET Framework V3.5
  • Microsoft .NET Framework V4.0
  • Microsoft .NET Framework V4.5
SOAP Support
  • Microsoft Internet Information Services (for running .NET services) on Windows XP and 2003
  • Microsoft .NET Framework V2.0
  • Microsoft .NET Framework SDK V2.0 or Microsoft Visual Studio 2005 (for deploying Microsoft .NET services)
  • IBM 32-bit SDK for Windows, Java 2 Technology Edition, V1.4.2
  • IBM 32-bit SDK for Windows, Java 2 Technology Edition, V5.0 (SR1 or above)
  • IBM 32-bit SDK for Windows, Java Technology Edition, V6.0
  • IBM Runtime Environment, Java Technology Edition 7.0 and future Fix Packs. 32-bit only
  • Transport for SOAP support on 32-bit only (Apache Axis 1.4) - commonly known as Axis 1
    (supplied with WebSphere MQ)
  • Transport for SOAP support on 32-bit only (Apache Axis2 1.4 ) - commonly known as Axis2
Windows Communications Foundation (WCF)
  • Microsoft .NET Framework V3.0
  • Microsoft .NET Framework V3.5
  • Microsoft .NET Framework V4.0
Transactions Managers Using the WebSphere MQ classes for JMS, WebSphere MQ can only act in the role of a Resource Manager. A 3rd party Transaction Coordinator must be used, for example WebSphere Application Server.

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

The WebSphere MQ V7 Queue Manager can participate as a Resource Manager with the following Transaction Coordinators:
  • IBM TXSeries V6.1 and V6.2 [see section note 1]
  • IBM TXSeries V7.1 [see section note 1]
  • BEA Tuxedo V9.1
  • MTS/COM (at the same level as the operating system)
  • IBM WebSphere Application Server, including the WebSphere Application Server client container, V6.0.2 (see this document for more information)
  • IBM WebSphere Application Server, including the WebSphere Application Server client container, V6.1 (see this document for more information)
  • IBM WebSphere Application Server, including the WebSphere Application Server client container, V7.0 (see this document for more information
  • IBM WebSphere Application Server, including the WebSphere Application Server client container, V8.0 (see this document for more information

Notes:
  1. The resiliency feature of TXSeries V6.1/V6.2/V7.1 is not supported. For more details, please refer to
    XA Resiliency feature of TXSeries V6.1/V6.2/V7.1 doesn't work with WebSphere MQ as RM.
Application Servers Where a WebSphere MQ client application is running in one of the listed transaction manager environments, it is recommended that you contact the transaction manager vendor in the first instance for support.

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

Notes:
  1. For more detailed information about using WebSphere MQ with application servers see the WebSphere MQ resource adapter statement of support document.
  2. WebSphere MQ V7.0.1.1 or later is required.
  3. 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.
  4. Oracle WebLogic Server 11gR1 equals all versions 10.3.1 up to and including 10.3.6
  5. WebSphere MQ V7.0.1.8 or later is required.
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. A 3rd party Transaction Coordinator must be used, for example WebSphere Application Server.

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

Notes:
  1. Only 64-bit DB2 instances can be used with a 64-bit WebSphere MQ application.
  2. Informix Dynamic Server (IDS) and Sybase Adaptive Server Enterprise (ASE) are NOT supported by the WebSphere MQ Java Classes.
  3. WebSphere MQ V7.0.1 or later is required.
  4. For JDBC XA support, APAR IC65437 is required (shipped in WebSphere MQ V7.0.1.3).
  5. For JDBC XA support, request the 64-bit JDBC library from WebSphere MQ Service.
  6. WebSphere MQ V7.0.1.1 or later is required.
  7. WebSphere MQ V7.0.1.2 or later is required.
  8. Oracle 64-bit databases on Windows x64 require the 32-bit Oracle client.
Connectivity
  • IBM Communications Server for Windows V6.1.2
  • IBM Personal Communications for Windows V5.9 (part of IBM Host Access Client Package for Multi-platforms (HACP), V6)
  • Microsoft Host Integration Server 2006 (Provides 64-bit support)
  • Attachmate myEXTRA! Presentation Services, V7.11
  • Attachmate EXTRA! X-treme V9
  • TCP/IP (provided by the operating system; IP V6 feature provided on Windows XP with Service Pack 1 or later, Windows Server 2003 and Windows Vista)
  • NetBIOS (provided by the operating system)
  • Sequenced Package Exchange (SPX) (provided on Windows XP and 2003 only)
  • WebSphere MQ client applications are supported on the Citrix Presentation Server V4.5
SSL/TLS GSKit:
  • IBM Global Security Kit V7D (32-bit)
  • IBM Global Security Kit V7D (64-bit)

Refer to the Cryptography Card List for WebSphere MQ v6 and v7 document for further information.
Supported browsers for the WebSphere MQ information center
  • Internet Explorer (IE) 6.0, Internet (IE) 7.0
  • Mozilla 1.7
  • Firefox 1.5, Firefox 2.0
  • Konqueror (UI base mode only - meaning that only the basic functions of the information center will work, i.e. All function that supports base user activities with the content such as displaying a topic, locating a topic via the table of contents, searching for a topic and displaying it, etc are retained in base mode)
Supported application servers for the WebSphere MQ Bridge for HTTP
  • WebSphere Application Server V6.0.2.1 or later [see section note 1]
  • WebSphere Application Server V7 or later
  • WebSphere Application Server Community Edition (WAS CE) V1.1 or later [see section note 1]
  • WebSphere Application Server Community Edition (WAS CE) V2.1 or later

Notes:
  1. Only the following versions of Microsoft Windows are supported:
    • XP Professional SP2, 2003 Server SP1, and 2003 Server x64 SP1 or SP2
Other platform specifics ActiveX and Visual Basic Support is only provided for WebSphere MQ V6.0 functionality.
  • Visual Basic compiler: Microsoft Visual Basic V6
Multi-instance queue manager For multi-instance queue managers you will need a networked storage device accessed by the Common Internet File System (CIFS) protocol used by Microsoft Windows networks.

Testing and support statement for WebSphere MQ multi-instance queue managers
Virtualization Please read the read me first section in conjunction with this
  • VMWare: 3.0, 3.5, 4.0, 4.1
  • VMware ESXi 3.5, 4.0, 4.1, 5.0, 5.1 and 5.5


Change history:
  • 10th April, 2008: Added support for Windows Server 2008.
  • 25th April 2008: Added the WebSphere MQ Bridge for HTTP section.
  • 3rd June 2008: Added support for TXSeries V6.1 and V6.2.
  • 10 July 2008: In the Application Server section split the IBM WebSphere Application Server V6.0.2 and V6.1 entry into separate listings.
  • 24th September 2008: Corrected Informix Dynamic Server (IDS) V10.50 with Client SDK V2.91 to V11.10 with Client SDK V3.0.
  • 9th December 2008: Added support for Microsoft Windows Embedded Point of Service 1.0.
  • 16th December, 2008: Added Microsoft Windows Server 2008 MSCS issue note.
  • 19th December 2008: Added support for IBM WebSphere Application Server V7.0.
  • 19th December 2008: Added the Cryptography Cards section.
  • 6th March 2009: Added support for Microsoft .NET Framework V3.5.
  • 11th March 2009: Added support for WebSphere Application Server V7.
  • 11th March 2009: Added support for WebSphere Application Server Community Edition (WAS CE) V2.1.
  • 2nd June 2009: Added support for IBM TXSeries V7.1.
  • 25th August 2009: Added support for WebSphere MQ V7.0.1.
  • 11th December 2009: Added support for Microsoft Windows 7 and Windows Server 2008 R2.
  • 18th December 2009: Added support for Micro Focus Net Express V5.1.
  • 7th January 2010: Added support for Oracle 11g Release 1.
  • 23rd January 2010: Added support for IBM DB2 9.7 for Linux, UNIX and Windows.
  • 1st April 2010: Added support for Informix Dynamic Server (IDS) V11.5.
  • 20th April 2010: Added support for Oracle WebLogic Server 11gR1.
  • 5th October 2010: Added support for Microsoft Framework V4.0.
  • 13th October 2010: Added support for Oracle 11g Release 2.
  • 18th January 2011: Added support for Oracle WebLogic Server 10.3.
  • 21st April 2011: Added support for Microsoft Visual Studio 2010.
  • 11th July 2011: Added support for IBM WebSphere Application Server V8.0
  • 12th October 2012: Added Java 7 (1.7) Support.
  • 6th December 2012: Added Note 4 to Application Servers section.
  • 2nd January 2013: Added Oracle WebLogic Server 12cR1 (12.1.1) and Note 5 to Application Server section.
  • 31st January 2013: Added support for DB2 Advanced Enterprise Server Edition 10.1
  • 1st February 2013: Added clarification for Oracle Database 11g Standard/Enterprise Editions Release 1 and 2.
  • 14th June 2013: Virtualization update.
  • 15 October 2013: Added clarification to SOAP Support section.
  • 6 November 2013: Added DB2 Advanced Enterprise Server Edition 10.5
  • 29 November 2013: Added support for Microsoft .NET Framework V4.5
  • 17 December 2013: Added VMware ESXi 5.5
  • 16 January 2014: Added Windows Visual Studio 2012 for C applications only.
  • 22 July 2014: Added 140-2 to FIPS compliance comment and updated entries were comment was missing previously.
  • 3 Nov 2014: Updated expiration date.

Product Alias/Synonym

WMQ MQ

Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere MQ
Documentation

Software version:

7.0

Operating system(s):

Windows

Reference #:

7011920

Modified date:

2014-11-03

Translate my page

Machine Translation

Content navigation