IBM Support

System Requirements for WebSphere MQ V7.0/7.0.1 on i5/OS

Product documentation


Abstract

This document contains the system requirements for WebSphere MQ V7.0 on i5/OS.

Content

Please read first
  • The 'MQ Explorer' will not run on this platform.
Hardware requirements
Operating Systems

Notes:
  1. Please refer to technote Details for WebSphere MQ V7 on IBM i 6.1
  2. Please refer to technote Details for WebSphere MQ V701 installation on IBM i 7.1
  3. WebSphere MQ V7.0.1.2 or later is required.
For C/C++ applications
For COBOL applications
For Java™ applications using the WebSphere MQ classes for Java or JMS IBM i5/OS V5R4:

IBM i 6.1:

IBM i 7.1:

Notes:
  1. WebSphere MQ V7.0.1.6 or later is required.
For RPG applications
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 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.

The WebSphere MQ V7 Queue Manager can participate as a Resource Manager with the following Transaction Coordinators:
  • 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
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 2]:
  • 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

Notes:
  1. For more detailed information about using WebSphere MQ with application servers see the WebSphere MQ resource adapter statement of support document.
  2. 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.
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.
Connectivity
  • TCP/IP (Provided with the operating system)

For SSL the following are mandatory:
SSL/TLS GSKit:

Refer to the Cryptography Card List for WebSphere MQ v6 and v7 document for further information.
Supported application servers for the WebSphere MQ Bridge for HTTP
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 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


Change history:

Product Alias/Synonym

WMQ MQ

Document information

More support for: WebSphere MQ
Documentation

Software version: 7.0

Operating system(s): IBM i

Reference #: 7011923

Modified date: 01 April 2008