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
  • IBM System i, 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
  • IBM i5/OS V5R3M0 plus PTF SI21688
  • IBM i5/OS V5R4M0
  • IBM i5/OS V6R1M0 [see section note 1]
  • IBM i V7R1M0 [see section notes 2 and 3]

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
  • Integrated Language Environment facilities are provided as part of IBM WebSphere Development Studio for IBM System i.
  • IBM WebSphere Studio Development Suite for System i 5722WDS
  • ILE C: 5722WDS Option 51
  • ILE C++: 5722WDS Option 52
For COBOL applications
  • Integrated Language Environment facilities are provided as part of IBM WebSphere Development Studio for IBM System i.
  • IBM WebSphere Studio Development Suite for System i 5722WDS
  • ILE COBOL: 5722WDS Option 41
For Java™ applications using the WebSphere MQ classes for Java or JMS IBM i5/OS V5R4:
  • Java Developer Kit 1.4 (Classic) 5722JV1 (option 6)
  • Java Developer Kit 5.0 (Classic) 5722JV1 (option 7)
  • Java SE 5.0 32bit (J9) 5722JV1 (option 8) [see section note 1]
  • Java Developer Kit 6 (Classic) 5722JV1 (option 10)
  • Java SE 6 32bit (J9) 5722JV1 (option 11) [see section note 1]

IBM i 6.1:
  • Java Developer Kit 1.4 (Classic) 5761JV1 (option 6)
  • Java Developer Kit 5.0 (Classic) 5761JV1 (option 7)
  • Java SE 5.0 32bit (J9) 5761JV1 (option 8) [see section note 1]
  • Java SE 5.0 64bit (J9) 5761JV1 (option 9) [see section note 1]
  • Java Developer Kit 6 (Classic) 5761JV1 (option 10)
  • Java SE 6 32bit (J9) 5761JV1 (option 11) [see section note 1]
  • Java SE 6 64bit (J9) 5761JV1 (option 12) [see section note 1]

IBM i 7.1:
  • Java SE 5.0 32bit (J9) 5761JV1 (option 8) [see section note 1]
  • Java SE 5.0 64bit (J9) 5761JV1 (option 9) [see section note 1]
  • Java SE 6 32bit (J9) 5761JV1 (option 11) [see section note 1]
  • Java SE 6 64bit (J9) 5761JV1 (option 12) [see section note 1]

Notes:
  1. WebSphere MQ V7.0.1.6 or later is required.
For RPG applications
  • Integrated Language Environment facilities are provided as part of IBM WebSphere Development Studio for IBM System i
  • IBM WebSphere Studio Development Suite for System i 5722WDS
  • ILE RPG: 5722WDS Option 31
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 CICS Transaction Server for i5/OS
  • 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
  • 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.
  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.
  • IBM DB2 Universal Database provided by the level of operating system
Connectivity
  • SNA (Provided with the operating system)
  • TCP/IP (Provided with the operating system)
    • IP V6 feature support is also provided

For SSL the following are mandatory:
  • 5722SS1 Option 34: Digital Certificate Manager
  • 5722AC3 *BASE: Crypto Access Provider 128-bit
  • 5722DG1 *BASE : IBM HTTP Server to manage certificates through DCM
SSL/TLS GSKit:
  • Not applicable. SSL is provided with the operating system.

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
  • WebSphere Application Server V6.0.2.1 or later
  • WebSphere Application Server V7 or later
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:
  • 25th April 2008: Added the WebSphere MQ Bridge for HTTP section.
  • 10th July 2008: In the Application Server section split the IBM WebSphere Application Server V6.0.2 and V6.1 entry into separate listings.
  • 10th November 2008: Added support for IBM WebSphere Application Server, including the WebSphere Application Server client container, V7.0.
  • 19th December 2008: Added support for IBM WebSphere Application Server V7.0.
  • 19th December 2008: Added the Cryptography Cards section.
  • 9th February 2009: Added section note 1 to IBM i5/OS V6R1M0.
  • 11th March 2009: Added support for WebSphere Application Server V7.
  • 25th August 2009: Added support for WMQ V7.0.1.
  • 6th January 2010: Added support for Multi-instance queue managers.
  • 7th July 2010: Added support for IBM i V7R1M0.
  • 11th July 2011: Added support for IBM WebSphere Application Server V8.0.
  • 25th August 2011: General update to Java section.
  • 27th February 2012: Updating expiration date.
  • 26th February 2014: Updating 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):

i5/OS

Reference #:

7011923

Modified date:

2008-04-01

Translate my page

Machine Translation

Content navigation