Supported databases

A broker requires a database to contain operational and state data. Multiple brokers within a single instance can access the same database, if appropriate, because all tables are qualified by the broker name. Brokers in different installation locations on the same system cannot share a database.

The broker tables are created when you invoke the mqsicreatebroker command. The tables that are created are listed in Database contents.

The following table indicates which levels of database are supported on which operating systems. In most situations, the broker that accesses the database does not have to be running on the same operating system as the database server. For details about local and remote database use, and existing restrictions, see Database locations.

Operating system DB2®1 Microsoft SQL Server Oracle1 Sybase

AIX

8.22

Not applicable

Start of change

9i Rel 2 Patch Set 4
(9.2.0.5, patch 3501955)

End of change

10G

12.5

HP-UX

8.22

Not applicable

Start of change

9i Rel 2 Patch Set 4
(9.2.0.5, patch 3501955)

End of change

10G

12.5

Linux (x86 platform)

8.22

Not applicable

Start of change

9i Rel 2 Patch Set 4
(9.2.0.5, patch 3501955)

End of change

10G

12.5

Linux (zSeries platform)

8.22

Not applicable

Not supported

Not supported

OS/4003

8.22

Not applicable

Not applicable

Not applicable

Solaris

8.22

Not applicable

Start of change

9i Rel 2 Patch Set 4
(9.2.0.5, patch 3501955)

End of change

10G

12.5

Windows

8.22+4

2000 SP3a

Start of change

9i Rel 2 Patch Set 4
(9.2.0.5, patch 3501955)

End of change

10G

12.5

z/OS

7.15

8.15

Not applicable

Not supported

Not applicable

Notes:
  1. Start of changeSupported releases of DB2 and Oracle can participate as a Resource Manager in a distributed XA transaction, and can be coordinated by WebSphere MQ as the XA Transaction Manager.End of change In WebSphere Event Broker, this is referred to as supporting a globally coordinated message flow. On z/OS, all transactions are coordinated by Recoverable Resource Services (RRS).

    XA coordination for messages in the MRM domain on Windows requires DB2 Version 8.2 FixPak 10 or later.

  2. Check the readme.html file for your product to check if a fix pack or other fix is required.
  3. You can use the embedded Derby database for verification, evaluation, and test purposes only. Derby refers to IBM Cloudscape™ Version 10.0, a database product that is built on the Derby database from the Apache Software Foundation. Cloudscape does not modify Derby in any way, but provides additional function including installers. Derby database support is embedded in the broker component on Windows only. For a production system, you might want to install and configure your chosen enterprise database.
  4. On z/OS, DB2 is a mandatory requirement. You must create a unique database for each broker. See the Program Directory for WebSphere Event Broker for z/OS or the Program Directory for WebSphere Rules and Formatter Option for z/OS for further details.
Related concepts
Derby databases on Windows
Related tasks
Finding the latest information
Related reference
Database locations
Database contents
Supported processors
Operating system requirements
Additional software prerequisites