Your broker domain requires databases to
support product components (the broker and the Configuration Manager;
the User Name Server has 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 only DB2 for the configuration repository
for the Configuration Manager. You are recommended to use
a local database for this repository, mainly for performance reasons. If you
choose to use a remote database, you must create and configure it on a distributed
system. A DB2 database on z/OS or OS/400 is not supported.
You can use a local or remote database for
the Configuration Manager, 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 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 iSeries
-
- Database support on iSeries (OS/400) is DB2 only.
- Your OS/400 installation must be V5R2 or V5R3.
- Your OS/400 installation must be V5R1, with PTFs SI03013
and SI04047, or V5R2. If you are using Client Access Express to connect to
OS/400, V5R1 also requires PTF SI05361 and V5R2 requires PTF SI05854.
- 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.
New Era of Network nodes within message flows cannot access an
iSeries database.
Stored procedures are supported.
- Database on z/OS
-
- Database support on z/OS is DB2 only.
See the Program Directory for WebSphere
Business Integration Message Broker for
z/OS or the Program Directory for WebSphere Rules and Formatter
Option for z/OS.
- You must use DB2 Connect on Linux, UNIX, and Windows.
New Era of Network nodes within message flows cannot access a
database on z/OS.
Large database objects (LOBs) support requires
DB2 Connect V8.1 FixPak 4 and DB2 for z/OS 7.1 at RSU0310.
- WebSphere Information Integrator Support
- Brokers can access WebSphere Information Integrator databases for user
data on WebSphere Information Integrator for Linux, UNIX and Windows Version
8.2, and on WebSphere Information Integrator Classic Federation for z/OS Version
8.2. On z/OS this 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 does not support two phase commit, and you must set up all ODBC connections
with CAF (Call Attachment Facility), not the default option which is RRSAF
(Recoverable Resource Manager Services Attachment Facility).
- 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
Business Integration Message Broker to
determine the best options for your specific environment and requirements,
and information about how to configure remote databases access.