IBM Support

System Requirements for WebSphere MQ V7.0/7.0.1 on HP-UX PA-RISC

Product Documentation


Abstract

This document contains the system requirements for WebSphere MQ V7.0 on HP-UX PA-RISC.

Content

Please read first


  • HP-UX (PA-RISC) with 64-bit hardware, 32-bit and 64-bit WebSphere MQ APIs are supported and the operating system must have a 64-bit kernel.
  • 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.
Hardware requirements
  • HP PA-RISC 64-bit 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.
Operating Systems
  • HP-UX 11i V2 (11.23)
  • HP-UX 11i V3 (11.31) [see section note 1]

Notes:
  1. Before installing on HP-UX 11i V3 (11.31) see technote 1270591.
For C/C++ applications
  • For applications using the WebSphere MQ C++ classes, both the classic and standard runtimes are supported.
  • HP C/ANSI Developer Bundle for HP-UX 11i2
  • HP aC++ A.03.65 [see section note 1]
  • HP aC++ A.03.67 [see section note 1]
  • HP aC++ A.03.70 [see section note 1]
  • HP aC++ A.03.73 [see section note 1]
  • HP aC++ A.03.74 [see section note 2]
  • HP aC++ A.03.77
  • HP aC++ A.03.80

Notes:
  1. Supported on HP-UX 11i V2 only.
  2. Supported on HP-UX 11i V3 only.
For COBOL applications
  • Micro Focus Server Express V4.0, 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:
  • HP-UX SDK for the Java platform and JDK V1.4.2 (32 and 64 bit)
  • HP SDK for J2SE HP-UX 11i platform, adapted by IBM for IBM software V1.4.2 [see section notes 1 and 2]
  • HP SDK for J2SE HP-UX 11i platform, adapted by IBM for IBM software V5.0 (SR1 or above) [see section notes 2 and 3]
  • HP JDK for JSE HP-UX 11i platform, adapted by IBM for IBM Software, V6 for 32-bit PA-RISC [see section notes 1 and 2]
  • HP JDK V5.0 [see section notes 3 and 4]
  • HP JDK V6.0 [see section notes 4 and 5]
64-bit:
  • HP-UX SDK for the Java platform and JDK V1.4.2 (32 and 64 bit)
  • HP 64-bit SDK for J2SE HP-UX 11i platform, adapted by IBM for IBM software V1.4.2 for 64-bit PA-RISC [see section notes 1 and 2]
  • HP 64-bit SDK for J2SE HP-UX 11i platform, adapted by IBM for IBM software V5.0 for 64-bit PA-RISC (SR1 or above) [see section notes 2 and 3]
  • HP JDK for JSE HP-UX 11i platform, adapted by IBM for IBM Software, V6 for 64-bit PA-RISC [see section notes 1 and 2]
  • HP JDK V5.0 [see section notes 3 and 4]
  • HP JDK V6.0 [see section notes 4 and 5]

Notes:
  1. Only if the JDK is supplied with another IBM product.
  2. FIPS compliance is only supported on IBM adapted SDKs.
  3. The Java Runtime Environment must be run with the following parameter set: -XX:+UseGetTimeOfDay
  4. WMQ v7.0.1.0 or later is required.
  5. Patches from HP must be applied depending on the operating system version being used:
  • HP-UX 11i V3 - patch is PHSS-37202 (see here)
  • HP-UX 11i V2 - patch is PHSS-37201 (see here)
SOAP Support
  • HP SDK for J2SE HP-UX 11i platform, adapted by IBM for IBM software V1.4.2 (32 bit only)
  • HP SDK for J2SE HP-UX 11i platform, adapted by IBM for IBM software V5.0 (SR1 or above) (32 bit only)
  • HP JDK for JSE HP-UX 11i platform, adapted by IBM for IBM Software , V6 for 32-bit PA-RISC
  • IBM Runtime Environment, Java Technology Edition 7.0 and future Fix Packs.
  • Transport for SOAP support on 32-bit only (Apache Axis 1.4) - commonly known as Axis 1 (supplied with WebSphere MQ) (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:
  • IBM TXSeries V6.1 and V6.2 [see section note 1]
  • IBM TXSeries V7.1 [see section note 1]
  • BEA Tuxedo V9.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. 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 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, including the WebSphere Application Server client container, V7.0 (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 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 64-bit WebSphere MQ.
  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. JDBC XA not supported.
  5. WebSphere MQ V7.0.1.1 or later is required.
Connectivity
  • HP SNAplus2 Version 7 (SNA)
  • TCP/IP (provided by the operation system); IPv6 feature support is available with HP's Transport Optional Upgrade Release (TOUR)
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
  • 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

Notes:
  1. A CPU processor speed of 440 Mhz or faster is required.
Multi-instance queue manager
WebSphere MQ V7.0.1 introduces Multi-instance queue managers. For this you will need a networked storage device (such as a NAS). 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
  • ONC B.11.31.08 required for multi-instance queue manager support.
  • For HP-UX 11.31 libc cumulative patch PHCO_36900 or superseding patch is required.


Change history:
  • 25th April 2008: Added the WebSphere MQ Bridge for HTTP section.
  • 2nd May 2008: Clarified C/C++ support
  • 3rd June 2008: Added support for TXSeries V6.1 and V6.2.
  • 10th 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.
  • 19th December 2008: Added support for IBM WebSphere Application Server V7.0.
  • 19th December 2008: Added the Cryptography Cards section.
  • 11th March 2009: Added support for WebSphere Application Server V7.
  • 13th March 2009: Added the technote 1270591 reference in the Operating Systems section.
  • 2nd June 2009: Added support for IBM TXSeries V7.1.
  • 17th July 2009: Added the Java Runtime Environment '-XX:+UseGetTimeOfDay' note in the Java applications section.
  • 25th August 2009: Added support for WMQ V7.0.1.
  • 11th September 2009: Added support for HP JDK for JSE HP-UX 11i platform, adapted by IBM for IBM Software, V6 for 32-bit and 64-bit PA-RISC.
  • 30th September 2009: Added support for HP JDK V5.0 and V6.0.
  • 20th October 2009: Added support for Micro Focus Server Express V5,1.
  • 23rd January 2010: Added support for Oracle 11g Release 1.
  • 1st April 2010: Added support for Informix Dynamic Server (IDS) V11.5.
  • 2nd July 2010: Added support for Oracle WebLogic Server 11gR1.
  • 11th July 2011: Added support for IBM WebSphere Application Server V8.0.
  • 29th February 2012: Updated document expiration date.
  • 6th December 2012: Added Note 4 to Application Servers section.
  • 2nd January: Added Oracle WebLogic Server 12cR1 (12.1.1) and Note 5 to Application Server section.
  • 31st January: Added support for DB2 10.1 Advanced Enterprise Server Edition 10.1
  • 1 February: Added clarification to Oracle Database 11g Standard/Enterprise Editions Release 1
  • 15 October 2013: Added clarification to SOAP support section.
  • 6 November 2013: Added DB2 Advanced Enterprise Server Edition 10.5
  • 31 Jan 2014: Fixing broken link.
  • 3 Nov 2014: Updated expiration date.

[{"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Documentation","Platform":[{"code":"PF010","label":"HP-UX"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Product Synonym

WMQ MQ

Document Information

Modified date:
17 June 2018

UID

swg27011927