Product Documentation
Abstract
This document contains the system requirements for WebSphere MQ V7.0 on i5/OS.
Content
|
Please read first | ||
| Hardware requirements |
| |
| Operating Systems |
Notes:
| |
| 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: | |
| 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:
| |
| 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]:
Notes:
| |
| 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 |
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:
- 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":{"code":"SSFKSJ","label":"WebSphere MQ"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Documentation","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Product Synonym
WMQ MQ
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg27011923