Skip to main content

Software  >  WebSphere  >  WebSphere Message Broker product Line  >  

System Requirements for WebSphere Message Broker V6.0 for z/OS, WebSphere Message Broker with Rules and Formatter Extension V6.0 for z/OS, and WebSphere Event Broker V6.0 for z/OS

 Product documentation
 
Abstract
This document contains system requirements for the WebSphere Broker V6 products on z/OS.
 
 
Content

Note: Refer to the Program Directory for more specific information.


The following products or equivalents are supported at the specified minimum levels:


Configuration Manager Requirements:

Operating Systems
  • IBM z/OS V1R5 (5694-A01), with PTF for APAR OA11699, at RSU0507 or later (for the target system).
  • IBM SMP/E for z/OS V3R1 or later (SMP/E PTF for APAR IR48947 is required for the driving system.)
Hardware Requirements
  • Any server capable of running one of the listed IBM z/OS releases
WebSphere MQ
  • IBM WebSphere MQ V5.3.1 for z/OS (5655-F10) (plus PTF for APAR PQ80677), including the FMID for MQ Java™ Classes.
  • IBM WebSphere MQ for z/OS, V6.0
  • IBM WebSphere MQ for z/OS, V7.0 [see note 6]
XML Toolkit
  • XML Toolkit V1.8 for z/OS
JDKBroker requires either: or



Broker Requirements:

Operating Systems
  • IBM z/OS V1R5 (5694-A01), with PTF for APAR OA11699, at RSU0507 or later (for the target system).
  • IBM SMP/E for z/OS V3R1 or later. (SMP/E PTF for APAR IR48947 is required for the driving system.)
Hardware Requirements
  • Any server capable of running one of the listed IBM z/OS releases
WebSphere MQ
  • IBM WebSphere MQ V5.3.1 for z/OS (5655-F10) (plus PTF for APAR PQ80677), including the FMID for MQ Java Classes.
  • IBM WebSphere MQ for z/OS, V6.0
  • IBM WebSphere MQ for z/OS, V7.0 plus FMID JMS7008 (MQ connectivity), plus PTFs for APARs PK69317, PK70759 and PK73269 [see note 6]
XML Toolkit
  • XML Toolkit V1.8 for z/OS
JDKBroker requires either: or
Databases
  • IBM DB2 Universal Database V7.1 (5675-DB2) at RSU0409 and PUT0402
  • IBM DB2 Universal Database (5625-DB2) V8.1, at RSU0609 or later, plus FMID JDB8817 (ODBC support), plus PTFs for APAR PQ 84976 and PK37248
  • or later version of IBM DB2 Universal Database

Notes:

  1. Before installing any new products, ensure that you review their current Preventative Service Planning (PSP) information.
  2. Brokers can access Information Integrator databases, for user data, on WebSphere Information Integrator Classic Federation for z/OS V8.2, providing direct SQL connectivity with z/OS data sources: IMS, VSAM, ISAM, sequential files, CA-IDMS, CA-Datacom, Software AG ADABAS, and DB2. WebSphere Information Integrator Classic Federation v8.2 is supported when using a CAF connection only, and therefore this support does not include two-phase-commit. Please note that all broker datasources will be either CAF or RRSAF. When CAF is used, database operations are not coordinated by RRS. This includes any updates to the brokers database as well as user databases.
  3. Where patches for a product are specified, this means that these patches were required to resolve problems found during testing and should therefore be considered as the minimum necessary maintenance level. Further maintenance should be applied in accordance with the guidance of the relevant software manufacturer.
  4. The Message Broker supports any JMS 1.1 provider. The JRE required is Java 1.4.2, but it is not embedded. Both of these factors need to be considered when selecting a JMS provider whose client will be embedded in Message Broker.
  5. Automatic Client Reroute for DB2 is supported.
  6. WebSphere Message Broker V6.0.0.9 or later is required.


Change History
  • 20 December 2005: Added note 3.
  • 22 June 2006: Added note 4.
  • 7 July 2006: Added "The following products or equivalents are supported at the specified minimum levels:"
  • 1 November 2006: Corrected note 4 - The JRE required is Java 1.4.2 but it is not embedded.
  • 18 May 2007: Added "Program Directory" and "or later release of WMQ and DB2" notes.
  • 21 December 2007: Updated IBM DB2 Universal Database (5625-DB2) V8.1, at RSU0609 or later, plus FMID JDB8817 (ODBC support), plus PTFs for APAR PQ 84976 and PK37248 statement.
  • 25 February 2008: Added Automatic Client Reroute for DB2 is supported.
  • 30 June 2009: Added support for 31-bit SDK for z/OS, Java 2 Technology Edition.
  • 15 July 2009: Added support for IBM WebSphere MQ for z/OS, V7.0.
 
Related information
All WebSphere Brokers System requirements
WebSphere Brokers Recommended Updates
WebSphere broker libraries
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Business IntegrationWebSphere Event BrokerDocumentationz/OS6.0
Business IntegrationWebSphere Message Broker with Rules and Formatter ExtensionWorkbench - Generalz/OS6.0
 
 

Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Rate this page
Please take a moment to complete this form to help us better serve you.
This material provides me with the information I need.




This material is clear and easy to understand.




Did the information help you to achieve your goal?
What updates, improvements, or related information would you like to see in this document?
Your response will be used to improve our document content. Requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site.
Input the verification number to submit feedback:
Document information
 Product categories:
 Software
 Business Integration and Optimization
 Application Integration and Connectivity
 WebSphere Message Broker
 Documentation
 Operating system(s):
  z/OS
 Software version:
  6.0
 Reference #:
  7006594
 IBM Group:
 Software Group
 Modified date:
 2007-06-05

Translate My Page
 
 

Rate this page

Help us improve this page. Your response will be used to improve our document content. Requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site.