Database locations

You can deploy message flows that access databases to one or more of your brokers.

• 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 or V5R4.
  • 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 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.
  • You must use DB2 Connect on Linux, UNIX, and Windows.

  For further details, see the Program Directory for IBM Integration Bus for z/OS in the IBM® Publication Center publication number, GI13-3314.

  InfoSphere Federation Server databases

  • You can configure message flows on all distributed systems to access user data in InfoSphere Federation Server for Linux, UNIX, and Windows, Version 9.1.

    You can also configure message flows to access user data, by using JDBC only, in InfoSphere Classic Federation Server for z/OS, Version 9.1 on operating systems for which the InfoSphere Classic Federation Server client code is provided.

  • You can configure message flows on z/OS brokers to access user data, by using JDBC only, in InfoSphere Classic Federation Server for z/OS, Version 8.2. This support provides connectivity with the following z/OS data sources:
    • IMS™
    • VSAM
    • ISAM
    • Sequential files
    • CA-IDMS
    • CA-Datacom
    • Software AG ADABAS
    • DB2

    Brokers can connect directly to InfoSphere Classic Federation Server for z/OS, Version 9.1 by JDBC only.

    Brokers can connect indirectly to InfoSphere Classic Federation Server for z/OS, Version 9.1 through an intermediate DB2 system on z/OS. If you use this configuration, only an ODBC Call Attachment Facility (CAF) connection is supported between the broker and DB2; this connection therefore does not support two-phase commit.

    You must configure all broker ODBC data resources as either CAF or Recoverable Resource Services Attachment Facility (RRSAF). If you use CAF, database operations are not coordinated by RRSAF.

• If you 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 more information.

See the documentation for the database product that you are using with IBM Integration Bus to determine the best options for your specific environment and requirements, and information about how to configure remote database access.