Configuring broker and user databases

A broker stores internal performance and operational data in a database that you must create and configure before you create the broker. You might also choose to access databases to hold application or business data.

Start of changeMultiple brokers that are at the same version can store their tables in a single database schema, if appropriate, even if they are not on the same computer.End of change

Databases that hold application or business data are known as user databases, and are read from and written to by nodes within the message flows that you deploy to one or more brokers in your domain.

In some situations, the data that you hold in user databases might be critical to the success of your applications, and a particular step in their processing. You might therefore need to coordinate table updates, or the writing to one database with the deletion of data in another. To achieve these goals, you must configure your databases, your brokers, and your message flows to be globally coordinated.

For more information about the requirement for, and set up of, broker and user databases, and the restrictions that apply, see Databases overview.

z/OS platform For additional information about setting up databases on z/OS®, see DB2 planning on z/OS and Customizing the z/OS environment.

The process of making databases available has the following phases:

  1. Start of changeRequired: Create and configure a broker database.

    If you are migrating from a previous release, you can continue to use the same broker database, but you must check and update your ODBC configuration to ensure continued database access. Database access requires different configuration in each release; see Migrating from Version 5.0 products or Migrating from Version 2.1 products.

    If you are not migrating, you must create and configure a database for each broker that you create, and you must configure the ODBC resources required by the broker to connect to that database.

    Optional: if you want to deploy publish/subscribe message flow applications, and you have created a broker database on a Sybase database instance, you must modify the database to operate successfully in this environment.

    End of change
  2. Optional: Create and configure user databases. If your message flows interact with databases, you must create and configure those databases ready for connection by the broker on behalf of the message flows. For user databases, you can configure ODBC and JDBC connections.
  3. Optional: If your user databases contain critical information, coordinate their updates through a transaction manager.

    On distributed systems, the WebSphere MQ queue manager is the transaction manager that interacts with the resource managers (the database providers). On z/OS, RRS provides equivalent coordination.

To complete these phases:

  1. Start of changeFor a new installation, create and configure the broker database:End of change
    1. Create the databases.
    2. Authorize access to the database.
    3. Enable the ODBC connection.
    4. Optional: If you are creating a publish/subscribe broker domain and you are using a Sybase broker database, configure the database to support retained publications.
    Start of changeFor an existing broker that you are migrating, follow the instructions in the appropriate topics in Migrating and upgrading.

    You have now completed the only mandatory step for database configuration; now you can create and configure your broker domain components:

    1. If you have one or more components on z/OS, customize the z/OS environment.
    2. Configure broker domain components.
    3. Configure a broker domain in the workbench.
    4. Optional: If you want to establish a publish/subscribe network, configure a publish/subscribe topology.
    End of change
  2. Optional: If you want to access user databases from your deployed message flows, create and configure additional databases and connections:
    1. Create the databases.
    2. Authorize access to the databases.
    3. Start of changeOptional: If you want your databases to participate in globally coordinated transactions, configure the databases for global coordination.End of change
    4. Enable an ODBC connection.
  3. Optional: If you want your databases to participate in globally coordinated transactions, configure the environment for global coordination.
Related tasks
Migrating from Version 5.0 products
Migrating from Version 2.1 products
Configuring broker domain components
Configuring a broker domain in the workbench
Customizing the z/OS environment
Configuring a publish/subscribe topology
Related reference
Supported databases
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:22:01

ah14420_