The broker can access databases
set up on the local computer or on a remote server, subject to restrictions.
A broker domain requires databases to support its brokers. In addition, your brokers can host message flows that
access user databases. (The Configuration
Manager and
the User Name Server have no requirement for
database access.)
You can create and configure a broker database
on the local broker system, or on a remote system, with the exception
that you cannot create a remote broker database on i5/OS®, OS/400®,
or z/OS®.
- You can use a local or remote database for user data, subject
to the following restrictions:
- Databases on i5/OS and OS/400
-
- You can use only DB2® (UDB)
on iSeries® (System i®) under OS/400 or i5/OS.
- You must install OS/400 V5R2
or i5/OS V5R3.
- On Linux®, UNIX®, and Windows®, you can connect using DB2® Connect™. On Windows only, you can also use iSeries Access
for Windows.
- You cannot define globally-coordinated (XA) transactions.
- You cannot configure message flows that include Rules and Formatter
Extension nodes to access a database on i5/OS or OS/400.
- You can call stored procedures only if access to the remote database
is provided by DB2 Connect.
- Databases on z/OS
-
- You can use only DB2 (UDB)
on z/OS. If you install DB2 V8.1,
you must apply the PTF for APAR PQ84976.
- 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.
- You cannot configure message flows that include Rules and Formatter
Extension nodes to 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 databases
- You can configure message flows on all distributed
systems to access user data in WebSphere Information
Integrator for Linux, UNIX, and Windows Version 8.2.
You
can also configure message flows to access user data in WebSphere Information
Integrator Classic Federation (IICF) for z/OS Version 8.2, on broker platforms
for which WebSphere IICF client code is provided.
- You can configure message flows on z/OS brokers to access user data
in 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 Recoverable Resource Services (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 the database
product that you are using with WebSphere Message
Broker to
determine the best options for your specific environment and requirements,
and information about how to configure remote database access.