Skip to main content

Software  >  WebSphere  >  WebSphere Message Broker product Line  >  

System Requirements for WebSphere Message Broker V6.1 for z/OS

 Product documentation
 
Abstract
This document contains system requirements for the WebSphere Broker V6.1 products on z/OS.
 
 
Content
The Configuration Manager, User Name Server and Broker requirements for the following products or equivalents are supported at the specified minimum levels.

Configuration Manager, User Name Server and Broker Requirements:

Please read first
  • WebSphere Message Broker, WebSphere MQ Integrator, and Integrator Broker product READMEs
  • Before installing any new products, ensure that you review their current Preventative Service Planning (PSP) information.
  • 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.
  • Message Broker supports any JMS 1.1 provider, and requires a minimum JRE level of Java 1.5. Both of these factors need to be considered when selecting a JMS provider whose client will be embedded in Message Broker.
  • Defect support is available for virtualization environments where they relate to releases of this platform already supported by WebSphere Message Broker. Unless stated elsewhere in the system requirements, WebSphere Message Broker has not been specifically tested in virtualization environments. WebSphere Message Broker 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
  • Any server capable of running one of the listed IBM z/OS releases
Operating Systems
  • IBM z/OS V1R7 (5694-A01), at RSU0609 or later, plus PTFs for APARs PK34716 and PK34041.
  • IBM SMP/E for z/OS (5655-G44) V3R3 or later
XML Toolkit
  • XML Toolkit (5655-J51) V1.9 for z/OS
Java
  • 31-bit SDK for z/OS, Java 2 Technology Edition, V5 (SR5 or later service release)
Databases
(required for the broker component only)
Brokers can access Information Integrator data sources, for user data, on WebSphere Information Integrator Classic Federation for z/OS V8.2, providing connectivity with z/OS data sources: IMS, VSAM, ISAM, sequential files, CA-IDMS, CA-Datacom, Software AG ADABAS, and DB2.

Brokers can connect directly to WebSphere Information Integrator Classic Federation for z/OS V8.2 by JDBC only.

Brokers can connect indirectly to WebSphere Information Integrator Classic Federation for z/OS V8.2 though an intermediate DB2 system on z/OS. When using this configuration, only an ODBC CAF connection is supported between the broker and DB2, and therefore this support does not include two-phase-commit.

Please note that all broker ODBC data sources will be either CAF or RRSAF. When CAF is used, database operations are not coordinated by RRS. This includes any updates to the broker database as well as user databases.

  • IBM DB2 Universal Database (5625-DB2) V8.1, at RSU0609 or later, plus FMID JDB8817 (ODBC support), plus PTFs for APAR PK37248 [see section note 1
  • DB2 V9.1 or later, plus FMID JDB9917 (ODBC support), plus PTFs for APAR PK41943 [see section note 1]

Notes:
  1. Automatic Client Reroute for DB2 is supported.
WebSphere MQ
Notes:
  1. WebSphere Message Broker V6.1.0.3 or later is required.
Supported AdaptersFor specific enterprise information system (EIS) product versions supported by the v6.1 WebSphere Adapters embedded in WebSphere Message Broker please refer to the software requirements page at: Supported software for IBM WebSphere Adapters and IBM WebSphere Business Integration Adapters
  • SAP (z/OS V1R7)
Rules and Formatter ExtensionPlease refer to the Rules and Formatter Extension installation readme for a list of supported databases.

Change History

  • 12 October 2007: Initial release date November.
  • 20 November 2007: Changed Operating Systems, WebSphere MQ and Databases information.
  • 3 December 2007: Added Supported Adapters section and note 6.
  • 10 December 2007: Changed Operating System and Databases sections.
  • 7 March 2008: Added Automatic Client Reroute for DB2 is supported.
  • 29 May 2008: New format released (WMB 6.1.0.2 information is also included).
  • 27 June 2008: Clarified the Java 5 support includes the associated service releases.
  • 27 November 2008: General update in support of the WMB 6.1.0.3 release.
 
Related information
WebSphere Broker detailed system requirements
 
 
 

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.1
 Reference #:
  7010523
 IBM Group:
 Software Group
 Modified date:
 2007-10-25

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.