This topic contains sections marked as revised for this release
A broker requires access to a database to store operational and state data. You must create the database before you create the broker and specify the name of the database on the mqsicreatebroker command. The command creates tables to hold the broker data; these tables are listed in Database contents.
Multiple brokers within a single instance can access the same database, if appropriate, because the tables that are created are qualified by the broker name. Brokers in different installation locations on the same system cannot share a database.
The following table, and the accompanying notes, indicate the minimum levels of database products that are supported on each operating system. Some datatypes supported by these databases are not supported by WebSphere Message Broker; for details see Datatype support.
You can also configure message flows that access user databases. The support provided is the same as for broker databases, shown in the table below.
In most environments, the broker does not have to be running on the same operating system as the database server. For details about local and remote database use, and the restrictions that apply, see Database locations.
Database support is shown below; for the latest details on all supported platforms, visit the WebSphere Message Broker Requirements Web site.
Operating system | DB21 | Microsoft SQL Server | Oracle1+2 | Sybase1 | Informix1+3 |
---|---|---|---|---|---|
AIX | 8.24 |
2000 SP3a5 |
9i Release 2 Patch Set 4 |
12.5 |
Dynamic Server V9.4 |
HP-UX (Integrity platform) | 8.24 |
Not applicable | 10G Release 2 |
Not supported | Not supported |
HP-UX (PA-RISC platform) | 8.24 |
2000 SP3a5 |
9i Release 2 Patch Set 4 |
12.5 |
Dynamic Server V9.4 Client SDK V2.90 |
Linux (POWER platform) | 8.24 |
Not applicable | 9i Release 2 Patch Set 4 |
12.5 |
Dynamic Server V9.4 Client SDK V2.90 |
Linux (x86 platform) | 8.24+7 |
2000 SP3a5 |
9i Release 2 Patch Set 4 |
12.5 |
Dynamic Server V9.4 Client SDK V2.90 |
Linux (zSeries platform) | 8.24 |
Not applicable | 9i Release 2 Patch Set 4 |
Not supported | Dynamic Server V9.4 Client SDK V2.90 |
OS/4008 | 8.23 |
Not applicable | Not applicable | Not applicable | Not applicable |
Solaris (SPARC platform) | 8.24+9 |
2000 SP3a5 |
9i Release 2 Patch Set 4 |
12.5 |
Dynamic Server V9.4 Client SDK V2.90 with |
Solaris (x86-64 platform) | 8.24+9 |
Not applicable | 10G Release 1 |
12.5 |
Not supported |
Windows | 8.24+10 |
2000 SP3a5 |
9i Release 2 Patch Set 4 |
12.5 |
Dynamic Server V9.4 |
z/OS | 8.111 |
Not applicable | Not supported | Not applicable | Not supported |
WebSphere MQ Version 6.0.1 or later is required for globally coordinated transaction support (XA).
If you use WebSphere MQ Version 6 as a transaction manager, all datasources that are connected to DB2 from message flows in both 32-bit and 64-bit execution groups must connect to 64-bit DB2 instances.
XA coordination with 64-bit execution groups is available only with DB2 and Oracle.
XA coordination for messages in the MRM domain on Windows requires DB2 Version 8 FixPak 10 or later.
If you deploy message flows that access databases, you can define the message flows to be coordinated so that updates to those databases are synchronized with updates to other resources.
The client SDK only is required on each broker system; install the Dynamic Server on the system on which you create databases.
Large Objects (LOBs) are not supported.
DB2 Version 8.2 is functionally equivalent to Version 8.1 FixPak 7.