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 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 OS/400 is DB2 only.
- 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.
- Large database objects (LOBs) are not supported.
- Globally coordinated (XA) transactions are not supported.
- You can call stored procedures if access to the remote database is provided
by DB2 Connect (available on Windows and UNIX). It is not supported if access
is provided by Client Access Express (available on Windows only).
- Database on z/OS
-
- Database support on z/OS is DB2 only.
- Large database objects (LOBs) are not supported.
- You must use DB2Connect on both UNIX and Windows.
- Table and column names cannot be greater than eighteen characters.
- Trigger and constraint names cannot be greater than eight characters.
- SQL batch jobs that have been run in a distributed DB2 environment
must be reviewed and revised. This is because some Data Definition Language
(DDL) and Data Manipulation Language (DML) commands and statements are inappropriate
or incorrect for DB2 running on z/OS.
- 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.
There are advantages and disadvantages to local and remote database
usage. You must refer to the documentation supporting the database that you
are using for WebSphere Business Integration Message Broker to determine the
best options for your specific environment.