A broker domain requires databases to support its brokers. (The Configuration Manager and the User Name Server have
no requirement for database access.) In addition,
your brokers can host message flows that access user databases.
You
can choose to create and configure these databases on the local system, or
on a remote system, subject to the following restrictions:
- You can use a local or remote database for the broker tables, with the
exception that a remote database cannot be accessed on z/OS® or OS/400®.
- You can use a local or remote database for user data, subject
to the following operating system restrictions:
- Database on OS/400
-
- Database support on iSeries™ (OS/400) is DB2® only.
- You must have installed OS/400 Version 5.2, Version 5.3, or Version
5.4 on the iSeries server.
- On Linux, UNIX,
and Windows you can connect using DB2
Connect™. On Windows only you can
also use iSeries Access
for Windows.
- Globally coordinated (XA) transactions are not supported.
- Message flows that include Rules and Formatter Extension nodes cannot
access a database on OS/400.
- You can call stored procedures only if access to the remote database is
provided by DB2
Connect.
- Database on z/OS
-
- Database support on zSeries (z/OS)
is DB2 only.
- You must use DB2
Connect on Linux, UNIX,
and Windows.
- Large database objects (LOBs) are supported with DB2 for z/OS V7.1
at RSU0409 or later.
- Message flows that include Rules and Formatter Extension nodes cannot
access a database on z/OS.
For further details, see the Program Directory for WebSphere Message Broker for z/OS or
the Program Directory for WebSphere Message Broker with
Rules and Formatter for z/OS.
- WebSphere® Information
Integrator Support
- Message flows on all distributed systems brokers can access databases
on WebSphere Information
Integrator for Linux, UNIX,
and Windows Version 8.2.
- Message flows on z/OS brokers can access WebSphere Information Integrator Classic
Federation for z/OS Version 8.2. This
support provides direct SQL connectivity with the following z/OS data
sources:
- IMS™
- VSAM
- ISAM
- Sequential files
- CA-IDMS
- CA-Datacom
- Software AG ADABAS
- DB2
WebSphere Information Integrator Classic Federation for z/OS Version
8.2 is supported only with a CAF (Call Attachment Facility) ODBC connection.
This support does not include two phase commit, and database operations are
not coordinated by RRS.
- If you choose to use a remote database, you must configure the ODBC connection
to the database correctly. Refer to the documentation for the database product
that you are using for further information.
See the documentation for your database product using for WebSphere Message Broker to
determine the best options for your specific environment and requirements,
and information about how to configure remote databases access.