See information about the latest product version
Supported databases
You can optionally configure databases to contain data that is accessed by your message flows. Databases from IBM® and other suppliers are supported at specific versions on supported operating systems.
If you run message flows that access data that is held in databases, you must install and configure a supported database. Some data types that are supported by these databases are not supported by WebSphere Message Broker; for details, see Data types of values from external databases.
In most environments, the broker and the database server must not be running on the same operating system. For details about local and remote database use, and the restrictions that apply, see Database locations.
WebSphere Message Broker supports both transactional (XA) and non-transactional connections to databases. You can define an ODBC connection, or a JDBC type 4 connection, or both, to your database instances. XA support is referred to as a globally coordinated message flow.
On a single broker, you can use ODBC XA, or JDBC XA, but not both. This restriction applies to all supported platforms, and to all database servers for which XA is supported.
The following sections give details of this support, and describe restrictions where applicable:
ODBC support
The following table lists the supported database servers for each broker platform for non-XA support. XA connections are supported by most of these servers: See the notes following the table for details.
For the latest details of the versions of the database servers that are supported, see the WebSphere Message Broker Requirements website.
Unless otherwise stated, the ODBC client code for the database is at the same version and release as the server.
Operating system | DB2®1, 2 | Informix®5 | Microsoft SQL Server | Oracle1, 3, 4 | solidDB® | Sybase1 |
---|---|---|---|---|---|---|
AIX® | Supported | Supported | Supported6 | Supported | Supported | Supported |
HP-Itanium | Supported | Supported | Supported6 | Supported | Supported | Supported |
Linux on POWER® | Supported | Supported | Supported6 | Supported | Not supported | Supported |
Linux on x86 | Supported | Supported | Supported6 | Supported | Supported | Supported |
Linux on x86-64 | Supported | Supported | Supported6 | Supported | Supported | Supported |
Linux on IBM z Systems | Supported | Supported | Supported6 | Supported | Not supported | Not supported |
i5/OS™ and OS/400®7 | Supported | Not supported | Not supported | Not supported | Not supported | Not supported |
Solaris on SPARC | Supported | Supported | Supported6 | Supported | Supported | Supported |
Solaris on x86-64 | Supported | Supported | Supported6 | Supported | Supported | Supported |
Windows 7 | Supported | Supported8 | Supported | Supported8 | Supported8 | Supported8 |
Windows 7 (64-bit) | Supported | Not supported | Supported | Supported9 | Supported8 | Not supported |
Windows XP and Server 2003 | Supported | Supported8 | Supported | Supported8 | Supported8 | Supported8 |
Windows Vista | Supported | Supported8 | Supported | Supported8 | Supported8 | Supported8 |
Windows Server 2008 | Supported | Supported8 | Supported | Supported8 | Supported8 | Supported8 |
Windows Server 2008 R2 | Supported | Not supported | Supported | Supported9 | Supported8 | Not supported |
z/OS® | Supported | Not supported | Not supported | Not supported | Not supported | Not supported |
- XA support:
Supported releases of DB2, Oracle, and Sybase can participate as a resource manager in a distributed XA transaction, and can be coordinated by WebSphere MQ as the XA Transaction Manager, unless otherwise stated in the following notes. On z/OS, all transactions are coordinated by Recoverable Resource Services (RRS).
- Additional conditions forWebSphere MQ:
- If you use WebSphere MQ Version 7 for XA coordination on Windows, you must configure the queue manager to run under the broker service user ID by specifying the -si option on the strmqm command; for example, strmqm -si QM_name
- Additional conditions for databases:
- DB2 on i5/OS and OS/400, is not supported for XA connections.
- 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.
- ODBC drivers for Oracle and Sybase on all relevant systems, and for SQL Server on Linux and UNIX systems, are supplied with WebSphere Message Broker. Alternative drivers are not supported on these systems. For other systems, and for other databases on all systems, obtain these files from your database vendor.
- Additional conditions for z/OS
- On z/OS, all transactions are globally coordinated by using RRS. As with other platforms you can choose for ODBC database operations to be committed or rolled back irrespective of the success or failure of the message flow transaction as a whole. However, only one uncoordinated ODBC database connection per thread is supported.
- Additional conditions forWebSphere MQ:
- Automatic Client Reroute for DB2 is supported on all platforms.
- If you install the Oracle Database Server on 32-bit systems, you must also install the Oracle Runtime Client.
- On all Linux, UNIX, and Windows systems, you can use Oracle RAC (Real Application Clusters) databases. For Oracle RAC XA and non-XA, failover support is limited to the Connect-Time Failover feature only.
Each broker system requires only the Client SDK; install the Dynamic Server on the system on which you create databases.
Large Objects (LOBs) are not supported.
- On Linux and UNIX systems, you can remotely access an SQL Server database on Windows by using a supplied wire protocol driver.
- You can configure message flows to access DB2 databases on i5/OS and OS/400 for user data. The message flows can run on all supported broker platforms. For further details of these restrictions, and for information about the PTFs that are required with DB2 on these operating systems, see Database locations.
- Windows 32-bit edition of WebSphere Message Broker only.
- WebSphere Message Broker for Windows 64-bit is supported in XA environments only when using WebSphere MQ 7.0.1.3 (or later) in non-Oracle RAC failover environments.
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 listed in the ODBC support table. Connections are supported from all broker platforms, including z/OS.
For XA connections, the following restrictions apply:
- On distributed platforms, only DB2 and Oracle are supported.
- On z/OS, XA connections are not supported.
JDBC type 4 drivers are not supplied with WebSphere Message Broker; obtain these files from your database vendor. For the latest details of the drivers that are supported, see the WebSphere Message Broker Requirements website.
- The driver must be a JDBC Type 4 (Pure Java™) driver.
- Global transaction coordination (XA) is not supported.
- Discoverability in the Graphical Data Mapper is not supported.
- The automatic determination of field types in Graphical Data Maps is supported only if the driver correctly and fully implements java.sql.PreparedStatement.getParameterMetaData(). For more information, see Data type considerations for mapping database content.
Limited support is restricted to ensuring that WebSphere Message Broker uses the JDBC API correctly. Where the JDBC driver is supplied by IBMand a problem is suspected with the JDBC driver, the WebSphere Message Broker team collaborates with appropriate support teams within IBM if the customer is also entitled to support for the JDBC type 4 driver they are using.