System Requirements for WebSphere Message Broker V6.1 Solaris x86-64 platform

The Configuration Manager, User Name Server and Broker requirements for Solaris x86-64 are documented below.


Configuration Manager, User Name Server and Broker Requirements:

Please read first		WebSphere Message Broker, WebSphere MQ Integrator, and Integrator Broker product READMEs 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. The Message Broker supports any JMS 1.1 provider. The minimum embedded JRE is Java 1.5. Both of these factors need to be considered when selecting a JMS provider whose client will be embedded in Message Broker. The Rules and Formatter Extension is not supported on this platform. 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. Solaris Zones support information.
Hardware Requirements		Solaris x86-64 platform: AMD64, EM64T, and compatible processors - any hardware that is explicitly compatible and fully capable of running the specified operating system, all the corresponding supporting software shown below, and any associated applications unmodified.
Operating Systems		Solaris 10 (plus SunSolve recommended Patch Cluster level), which should at least include the patch 119964-08
Databases (required for the broker component only)		Brokers can access Information Integrator data sources, for user data, on WebSphere Information Integrator for Linux, UNIX, and Windows V8.2. 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 DB2 UDB Enterprise Server Edition, V8 Fix Pack 11 and other IBM DB2 UDB V8 Fix Pack 11 editions for production purposes [see section notes 1, 3, 4 and 5] IBM DB2 V9.1 [see section notes 1, 3, 4 and 5] IBM DB2 V9.5 [see section notes 1, 3, 4 and 5] Oracle 9i Release 2 Patch Set 4 (9.2.0.5) Oracle Patch 3501955 [see section notes 2 and 4] Oracle 10g Releases 1 and 2 [see section notes 2 and 4] Sybase Adaptive Server Enterprise (ASE) V12.5 Sybase Adaptive Server Enterprise (ASE) V15 Notes: JDBC Type-4 transaction support using DB2 requires a minimum level of DB2 v9.1 Fix Pack 3 or later. Support on DB2 v8 is not available. Only the connect-time failover feature of Oracle RAC in non-XA environments is supported. Oracle RAC is supported in XA environments for Oracle 10gR2 10.2.0.4 or above, with WebSphere Message Broker V6.1.0.4. Please note that this is only supported for 64 bit execution groups for this platform. Automatic Client Reroute for DB2 is supported. Globally coordinated transaction support (‘XA’) is provided. IBM DB2 Database Server - System i support (non-XA only). a. Brokers can access DB2 Databases, for user data, on System i servers running OS/400 V5R2, V5R3 or V5R4 via DB2 Connect. b. This support is subject to the following restrictions: i. The broker database may not reside on the System i server. ii. Globally coordinated ('XA') transactions are not supported. iii. Database stored procedures on the System i server may be called, when using DB2 Connect, but not with System i5 Access for Windows. IBM DB2 Database Server - System z support: a. Brokers can access DB2 Databases, for user data, on System z servers via DB2 Connect. Supported versions of DB2 can be found here. b. This support is subject to the following restrictions: i. The broker database may not reside on the System z server.
WebSphere MQ		IBM WebSphere MQ for Solaris x86-64, V6.0 [see section note 1] IBM WebSphere MQ for Solaris x86-64, V7.0 [see section note 2] Notes: WebSphere MQ V6.0.1.0 or later is required for globally coordinated transaction support (‘XA’). WebSphere Message Broker V6.1.0.3 or later is required.
Supported Adapters		For 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 (Sun Solaris 10) Siebel (Sun Solaris 10)

• 9 October 2007: Initial release date November.
• 20 November 2007: Added note 12.
• 3 December 2007: Added Supported Adapters section and note 13.
• 10 December 2007: Added which should at least include the patch 119964-08 to the Operating Section.
• 15 February, 2008: Removed Note: Oracle Database Server requires the Oracle Runtime Client.
• 7 March 2008: Added Automatic Client Reroute for DB2 is supported.
• 11 March 2008: Added virtualization note.
• 29 May 2008: New format released (WebSphere Message Broker 6.1.0.2 information is also included).
• 1 July 2008: Replaced note 2 in Databases section.
• 23 September 2008: Added Solaris Zones support information.
• 27 November 2008: General update in support of the WebSphere Message Broker 6.1.0.3 release.
• 19 December 2008: Removed Oracle 11g Release 1.
• 4 April 2009: Added 'XA' support for DB2 9.5.
• 11th June 2009: Added support for Oracle RAC in XA environment.