System Requirements for WebSphere MQ V7.0/7.0.1 on Solaris x86-64

Product documentation


Abstract

This document contains the system requirements for WebSphere MQ V7.0 on Solaris x86-64.

Content

Please read first
  • Sun platform with 64-bit hardware, 32-bit and 64-bit WebSphere MQ APIs are supported and the OS must have a 64-bit kernel.
  • On platforms where WebSphere MQ provides a 64-bit product, both 32-bit and 64-bit MQ APIs are supported and the OS must be capable of running 64-bit applications.
  • The 'MQ Explorer' will not run on this platform.
  • Defect support is available for virtualization environments where they relate to releases of this platform already supported by WebSphere MQ. Unless stated elsewhere in the system requirements, WebSphere MQ has not been specifically tested in virtualization environments. WebSphere MQ Support is therefore unable to assist in issues related to configuration and setup, or issues that are directly related to the virtualization environment itself.
  • Solaris Zones support information.
Hardware requirements
  • 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.
Operating Systems
  • Sun Solaris V10 (with SunSolve-recommended Patch Cluster level)
  • Solaris 11 [see section note 1 and 2]

Notes:
  1. WebSphere MQ V7.0.1 or later is required.
  2. Only supported using Java 1(6) or Java 1(7)
For C/C++ applications Sun ONE Studio 10 Enterprise Edition for Solaris (C and C++)
  • Sun ONE Studio 11 Enterprise Edition for Solaris (C and C++)
  • Sun Studio 12 [see section note 1]

Notes:
  1. WebSphere MQ V7.0.1 or later is required.
For COBOL applications
  • Micro Focus Server Express V5.0 and V5.1 [see section note 1]

Notes:
  1. For V5.1, WebSphere MQ V7.0.1 or later is required.
For Java™ applications using the WebSphere MQ classes for Java or JMS Java 5 and above is required when using CCSID 943 to connect to a Queue Manager when using a non-IBM JRE, For more details, please refer to APAR IZ71306.

32-bit:
  • Sun Java 2 Platform Standard Edition, Version 1.4.2
  • 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 32-bit SDK for Solaris, Java 2 Technology Edition, V1.4.2 [see section notes 1 and 2]
  • IBM 32-bit SDK for Solaris, Java 2 Technology Edition V5.0 (SR1 or above) [see section note 2]
  • IBM 32-bit SDK for Solaris on Intel architecture, 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 Solaris, Java 2 Technology Edition V5.0 (SR1 or above) [see section note 2]
  • IBM 64-bit SDK for Solaris on AMD64/EM64T architecture, 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]

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.​
SOAP Support
  • IBM 32-bit SDK for Solaris, Java 2 Technology Edition, V1.4.2
  • IBM 32-bit SDK for Solaris, Java 2 Technology Edition V5.0 (SR1 or above)
  • IBM 32-bit SDK for Solaris on Intel architecture, 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 1Apache Axis V1.4 (supplied with WebSphere MQ)
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:
  • BEA Tuxedo V9.1
  • Oracle Tuxedo 11gR1 [see section note 1]
  • 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. WebSphere MQ V7.0.1.1 or later is required.
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)
  • Other application server environments may be supported [see section note 1]
  • Oracle WebLogic Server 11gR1 (JMS only) [see section note 2 and 4]
  • 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 7.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 7.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. Informix Dynamic Server (IDS) and Sybase Adaptive Server Enterprise (ASE) are NOT supported by the WebSphere MQ Java Classes.
  2. WebSphere V7.0.0.2 or later is required.
  3. WebSphere MQ V7.0.1 or later is required.
  4. WebSphere MQ V7.0.1.1 or later is required.
Connectivity
  • TCP/IP (IPv4 and IPv6 provided by the operating system)
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
  • 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)
Multi-instance queue manager WebSphere MQ V7.0.1.1 introduces multi-instance queue managers on this platform. For this you will need a networked storage such as a 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) satisfies this requirement. Please note that earlier versions of NFS do NOT satisfy this requirement and must not be used with multi-instance queue managers.

Testing and support statement for WebSphere MQ multi-instance queue managers

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.

Change History:
  • 10th July 2008: In the Application Server section split the IBM WebSphere Application Server V6.0.2 and V6.1 entry into separate listings.
  • 23rd September 2008: Added Solaris Zones support information.
  • 24th September 2008: Corrected Informix Dynamic Server (IDS) V10.50 with Client SDK V2.91 to V11.10 with Client SDK V3.0.
  • 19th December 2008: Added support for IBM WebSphere Application Server V7.0.
  • 19th December 2008: Added the Cryptography Cards section.
  • 25th August 2009: Added support for Oracle 11g Release 1.
  • 25th August 2009: Added support for WMQ V7.0.1.
  • 20th October 2009: Added support for Sun Studio12.
  • 20th October 2009: Added support for Micro Focus Server Express V5.1.
  • 6th January 2010: Added support for Multi-instance queue managers.
  • 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.
  • 8th April 2010: Added support for Oracle 11g Release 2.
  • 2nd July 2010: Added support for Oracle Tuxedo 11gR1.
  • 2nd July 2010: Added support for Oracle WebLogic Server 11gR1.
  • 17th May 2011: Clarified support for multi-instance queue managers.
  • 11th July 2011: Added support for IBM WebSphere Application Server V8.0
  • 11th October 2011: Updated Multi-Instance Queue Manager section with current patch details.
  • 14th March 2012: Updated Multi-Instance Queue Manager section with current patch details.
  • 12th October 2012: Added Java 7 (1.7) Support.
  • 30th November: Added missing transaction manager details.
  • 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.
  • 11th January 2013: Added support for Solaris 11.
  • 31st January 2013: Added support for DB2 Advanced Enterprise Server Edition 10.1
  • 1st February 2013: Added clarification to Oracle Database 11g Standard/Enterprise Editions Release 2
  • 5th July 2013: Added comment regarding level of Java support to Solaris 11 statements.
  • 15 October 2013: Added clarification to SOAP Support section.
  • 6 November: Added DB2 Advanced Enterprise Server Edition 10.5
  • 22 July 2014: Added 140-2 to FIPS compliance is only supported on IBM JREs comment.
  • 10 Nov 2014: Updated expiry 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):

Solaris

Reference #:

7011921

Modified date:

2014-11-11

Translate my page

Machine Translation

Content navigation