WebSphere Message Brokers
File: ah14440_
Writer: Laura Cowen

Task topic

This build: July 31, 2007 21:30:10

Enabling connections to the databases

The broker uses ODBC to connect to databases. You must, therefore, define ODBC data source names (DSNs) for the broker database on each system that hosts a broker. You must also define ODBC DSNs for any user databases that are accessed by message flows that are deployed to the broker. At any one time there can be multiple connections using the same DSN definition.

z/OS platform On z/OS systems, see Data sources on z/OS for information about enabling connections to databases.

On distributed systems, when defining the DSNs, there are two important considerations that determine whether you must define a 32-bit DSN for the database, a 64-bit DSN, or both:
  • Whether the execution group and the database are 32-bit or 64-bit
  • Whether or not the message flow transactions will be globally coordinated

For more information about the 32-bit and 64-bit considerations, see Broker database connections and User database connections.

When you have defined the appropriate DSNs, you must also configure the environment so that the broker can access the correct database libraries (see Setting your environment to access databases).

To enable connections on distributed systems:

  1. Define the ODBC DSNs according to your platform:
    On Windows:
    Follow the instructions in Connecting to a database from Windows.
    On Linux (x86 platform):
    Follow the instructions in Connecting to a database from Linux and UNIX systems.
    On UNIX systems:
    Depending on your broker configuration, for each database you might need to define a 32-bit ODBC DSN, a 64-bit ODBC DSN, or both.
    Refer to the following tables to check which DSNs you must define. For more information about 32-bit and 64-bit considerations, see Broker database connections and User database connections.
    Table 1. Enabling connections to databases.
      32-bit execution group 64-bit execution group

    32-bit broker

    Broker database: 32-bit

    User database: 32-bit

    Broker database: 32-bit and 64-bit

    User database: 64-bit

    64-bit broker

    (HP-UX (Integrity platform) only)

    Not possible.

    Broker database: 64-bit

    User database: 64-bit

    Table 2. Enabling connections to databases with global coordination using a 64-bit queue manager
      32-bit execution group 64-bit execution group

    32-bit broker

    Broker database: 32-bit and 64-bit

    User database: 32-bit and 64-bit

    Broker database: 32-bit and 64-bit

    User database: 64-bit

    64-bit broker

    (HP-UX (Integrity platform) only)

    Not possible.

    Broker database: 64-bit

    User database: 64-bit

    All WebSphere MQ Version 6 queue managers on 32-bit platforms are 32-bit.
    Table 3. Enabling connections to databases with global coordination using a 32-bit queue manager
      32-bit execution group 64-bit execution group

    32-bit broker

    Broker database: 32-bit

    User database: 32-bit

    Not possible.

    64-bit broker

    (HP-UX (Integrity platform) only)

    Not possible.

    Not possible.

    All WebSphere MQ Version 6 queue managers on 32-bit platforms and all WebSphere MQ Version 5.3 queue managers are 32-bit.
    You have now configured the ODBC DSN for your broker database and the ODBC DSNs for any user databases.
  2. Configure the environment for issuing console commands and for running the broker so that it can access the required database libraries. For more information, see Setting your environment to access databases.
You have now enabled the broker to make connections to the broker database and to any user databases.
Next, return to the instructions in Configuring databases.
Related tasks
Configuring databases
Related reference
Supported databases
odbc.ini sample file
odbc64.ini sample file
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:30:10

ah14440_ This topic's URL is: