Skip to main content

Software  >  WebSphere  >  WebSphere MQ Family  >  

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 (not including VMware - see the following note) 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.
  • Software support for IBM SWG products in a VMware environment.
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 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 Vista (Business, Enterprise or Ultimate Edition)
  • Microsoft Windows Vista (64-bit versions of Business, Enterprise or Ultimate Edition)
  • Microsoft Windows Embedded Point of Service 1.0

Notes:
  1. There is an open issue with the use of WebSphere MQ and MSCS in a Windows 2008 environment. This page will be updated once this has been resolved. Reference: APAR IC59261.
For C/C++ applications
  • Microsoft Visual Studio C++ 2005
For COBOL applications
For Java™ applications using the WebSphere MQ classes for Java or JMS32-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.
  • 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]
  • IBM 32-bit SDK for Windows, Java Technology Edition, V6.0 [see section notes 1 and 2]
64-bit:
  • Sun Java 2 Platform Standard Edition, Version 5.0
  • Sun Java 2 Platform Standard Edition, Version 6.0
  • IBM 64-bit SDK for WindowsAMD64/EM64T architecture, Java 2 Technology Edition, V1.4.2 [see section note 1]
  • IBM 64-bit SDK for Windows AMD64/EM64T architecture, Java 2 Technology Edition, V5.0
  • IBM 64-bit SDK for Windows AMD64/EM64T architecture, Java Technology Edition, V6.0 [see section note 1]

Notes:
  1. Only if the JDK is supplied with another IBM product.
  2. FIPS compliance is only supported on IBM SDKs.
For .NET applications
  • Microsoft .NET Framework V2.0
  • Microsoft .NET Framework V3.0
  • Microsoft .NET Framework V3.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
  • Apache Axis V1.4 (supplied with WebSphere MQ)
Windows Communications Foundation (WCF)
  • Microsoft .NET Framework V3.5
  • Microsoft Visual Studio 2008
Transactions ManagersUsing the WebSphere MQ classes for JMS, WebSphere MQ can only act in the role of a Resource Manager. A 3rd party Transaction Co-ordinator must be used, for example WebSphere Application Server.

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.
  • 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)

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 WMQ as RM.
Application ServersWhere a WebSphere MQ client application is running in one of the listed transaction manager environments, it is recommended that you contact the transaction manager vendor in the first instance for support:
  • IBM WebSphere Application Server, including the WebSphere Application Server client container, V6.0.2 (see this document for more information)
  • IBM WebSphere Application Server, including the WebSphere Application Server client container, V6.1 (see this document for more information)
  • IBM WebSphere Application Server, including the WebSphere Application Server client container, V7.0 (see this document for more information)
  • BEA WebLogic Server 9.2 (JMS only)
  • Other application server environments may be supported [see section note 1]

Notes:
  1. For more detailed information about using WebSphere MQ with application servers see the WebSphere MQ resource adapter statement of support document.
Resource Managers (when MQ is the Transaction Manager)Using the WebSphere MQ classes for JMS, WebSphere MQ can only act in the role of a Resource Manager. A 3rd party Transaction Co-ordinator must be used, for example WebSphere Application Server.

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.

Notes:
  1. Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ.
  2. Informix Dynamic Server (IDS) and Sybase Adaptive Server Enterprise (ASE) are NOT supported by the WebSphere MQ Java Classes.
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
Versions of products / components shipped with the productJDK:
  • IBM 32-bit SDK for Windows, Java 2 Technology Edition, V5.0
  • IBM 64-bit SDK for Windows AMD64/EM64T architecture, Java 2 Technology Edition, V5.0
GSKit:
  • IBM Global Security Kit V7D (32-bit)
  • IBM Global Security Kit V7D (64-bit)
Supported browsers for the WebSphere MQ information center
  • 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
Cryptography CardsRefer to the Cryptography Card List for WebSphere MQ v6 and v7 document for further information.
Other platform specificsActiveX and Visual Basic Support is only provided for WebSphere MQ V6.0 functionality.
  • Visual Basic compiler: Microsoft Visual Basic V6
Multi-instance queue managerFor 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.


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 WMQ V7.0.1.
 
 
 

Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Rate this page
Please take a moment to complete this form to help us better serve you.
This material provides me with the information I need.




This material is clear and easy to understand.




Did the information help you to achieve your goal?
What updates, improvements, or related information would you like to see in this document?
Your response will be used to improve our document content. Requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site.
Input the verification number to submit feedback:
Document information
 Product categories:
 Software
 Business Integration and Optimization
 Application Integration and Connectivity
 WebSphere MQ
 Documentation
 Operating system(s):
  Windows
 Software version:
  7.0
 Reference #:
  7011920
 IBM Group:
 Software Group
 Modified date:
 2008-04-01

Translate My Page
 
 

Rate this page

Help us improve this page. Your response will be used to improve our document content. Requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site.