System requirements for WebSphere Message Broker Hypervisor Edition 7.0

Product documentation


Abstract

This document contains the system requirements for WebSphere Message Broker Hypervisor Edition 7.0.

Content

Please read first

Mandatory Requirements
- Message Broker Toolkit for Application Development
- Message Broker Explorer for Administration
- Message Broker Runtime

Optional Requirements
- Embedded application software
- Additional applications that can be used/connected



Please read first

General Information
  • Please refer to the WebSphere Message Broker README for the latest information on this environment.
  • 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.
  • 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.



Mandatory Requirements


Message Broker Toolkit for Application Development
Hardware Requirements AMD64 and EM64T technology-compatible PC hardware, capable of running the required level of a compatible operating system with enough storage to meet the requirements of the WebSphere Message Broker Toolkit.
Operating Systems
  • Red Hat Enterprise Linux (RHEL) 5.5 or later update
Installation Manager


Message Broker Explorer for Administration
Hardware Requirements AMD64 and EM64T technology-compatible PC hardware, capable of running the required level of a compatible operating system with enough storage to meet the requirements of the WebSphere Message Broker Explorer.
Operating Systems
  • Red Hat Enterprise Linux (RHEL) 5.5 or later update
Application Software


Message Broker Runtime Environment
Hardware Requirements AMD64 and EM64T technology-compatible PC hardware, capable of running the required level of a compatible operating system with enough storage to meet the requirements of the WebSphere Message Broker.
Operating Systems
  • Red Hat Enterprise Linux (RHEL) 5.5 or later update
Application Software
Virtualization Environment
  • VMWare ESX v4.0
  • WebSphere Cloudburst v2.0.0.1


Optional Requirements

Embedded application software
Supported Adapters WebSphere Message Broker Version 7.0 supports SAP, Siebel and PeopleSoft WebSphere Adapters Version 7.0. For more information about the hardware and software requirements of WebSphere Adapters, see Supported software for IBM WebSphere Adapters and IBM WebSphere Business Integration Adapters.
WebSphere Service Registry & Repository
Notes:
  1. Support is provided when using 6.1 compatibility URLs.
    Documentation for the "compatibility URLs" mentioned can be found at: WebSphere Service Registry and Repository - Web service interface URLs
WebSphere Transaction Extender for Integration Servers
WebSphere Application Server
Notes:
  1. This is required when using SOAP nodes with the JMS transport when interfacing with WebSphere Application Server.
WebSphere MQ File Transfer Edition
CICS Transaction Server


Additional applications that can be used/connected
Databases


Automatic Client Reroute for DB2 is supported.

Globally coordinated transaction support (‘XA’) is supported.

IBM DB2 Database Server - System i support:
  • Brokers can access DB2 Databases on System i servers running OS/400 V5R3, V5R4 or V6R1 via DB2 Connect or System i for Windows.
  • This support is subject to the following restrictions:
    • Globally coordinated 'XA' transactions are not supported.
    • Database stored procedures on the System i server may be called, when using DB2 Connect, but not with System i Access for Windows.
IBM DB2 Database Server - System z support:
  • Brokers can access DB2 Databases on System z servers via DB2 Connect. Supported versions of DB2 can be found here.
Brokers can access Information Integrator data sources, for user data, on WebSphere Information Integrator V9.1 for Linux, UNIX, and Windows.

Brokers can access, via JDBC only, Information Integrator data sources for user data on WebSphere Information Integrator Classic Federation (IICF) for z/OS, where the WebSphere IICF client code is provided for the Message Broker platform.
  • IBM solidDB 6.5 (plus Fix Pack 2) [see section note 1]

Notes:
  1. WebSphere Message Broker 7.0.0.1 or later is required.
  • Oracle 10g Release 2
  • Oracle 11g Release 1
  • Oracle 11g Release 2 [see section note 1]

Globally coordinated transaction support (‘XA’) is supported.

This support is subject to the following restrictions:
    • Only the connect-time failover feature of Oracle RAC is supported.
    • Oracle RAC is supported in XA environments for Oracle 10g Release 2 (plus Patch Set 4 or later) and Oracle 11g Release 1.

Notes:
  1. WebSphere Message Broker V7.0.0.1 or later is required.
  • Sybase Adaptive Server Enterprise (ASE) V15.0
  • Microsoft SQL Server 2005 (plus Service Pack 1)
  • Microsoft SQL Server 2008

This support is subject to the following restrictions:
  1. Large objects (LOBs) are not supported.
  2. Stored procedures are supported with Informix Client SDK V3.50 with FC4 Fix Pack.
JMS Providers The JMSInput and JMSOutput nodes are compatible with any JMS provider that conforms to the Java Message Service Specification, version 1.1.
JDBC type 4 support For non-XA transactions, you can create a JDBC type 4 connection from a broker to all the database servers that are supported.

For JDBC XA connections, the following restriction applies:
  1. Only DB2 and Oracle are supported.

For JDBC type 4 connections to DB2, the following restriction applies:
  1. You need either DB2 Version 9.1 with Fix Pack 3 or later, or DB2 9.5.

JDBC type 4 drivers are not supplied with WebSphere Message Broker; obtain these files from your database vendor. The following drivers are supported:
  • IBM DB2 Driver for JDBC and SQLJ Version 9.1 and 9.5
  • IBM solidDB JDBC Driver 2.0
  • Microsoft SQL Server 2005 JDBC driver 1.1 for use with Microsoft SQL Server 2005
  • Microsoft SQL Server 2005 JDBC driver 1.2 for use with Microsoft SQL Server 2008
  • Oracle 10gR2 or 11gR1 JDBC Driver
  • Sybase jConnect for JDBC 6.05
  • IBM Informix JDBC 3.50.JC3
Business Process Automation and Monitoring
Integration
Security The runtime security manager interacts with the following external security providers:

Notes:
  1. WS-Trust 1.3 compliant Security Token Servers, for valuation and issuance of tokens, are only supported on TFIM 6.2.
System Management
Troubleshooting
Development Repositories
  • All products supported by Eclipse 3.4.1 or later
Compilers If you develop user-defined extensions in C or Java, you need the appropriate supported software:
  • GNU gcc, Version 4.1 or later
  • Java Version 6 (also known as Java 1.6) SR6 or later Service Release
Browsers
  • Mozilla Firefox 2.x and 3.x
  • Microsoft Internet Explorer 6.x with SP1, 7.x and 8.x
Adobe Flash Player If you want to start the Quick Tour from the information center in the WebSphere Message Broker Toolkit, you must install Adobe Flash Player Version 8.0 or later. You can freely download from the Adobe website an Adobe Flash Player plug-in for the Web browsers that are supported by the WebSphere Message Broker Toolkit.


Change history:
30th November 2010: WebSphere Message Broker Hypervisor Edition 7.0 release.

Product Alias/Synonym

WMB MB

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Message Broker
Documentation

Software version:

7.0

Operating system(s):

Linux

Reference #:

7020483

Modified date:

2010-12-14

Translate my page

Machine Translation

Content navigation