WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Configuring user databases

Configure databases to hold application or business data that you can access from your message flows.

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, and for some applications, you might need to ensure the integrity of the data that you hold in user databases across multiple systems and resource managers by coordinating table updates and 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, user databases, and the restrictions that apply, see Databases overview.

The process of making databases available has the following phases:

  1. 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.
  2. 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. If you want to access user databases from your deployed message flows, create and configure the databases and the connections to them:
    1. Create the databases.
    2. Authorize access to the databases.
    3. Optional: If you want your databases to participate in globally coordinated transactions, configure the databases for global coordination.
  2. On distributed platforms, create and configure connections to the databases that you have created:
    1. If your message flows use an ODBC connection to a database, enable an ODBC connection for that database. Repeat this step for each database that you want to access in this way.

      Note that you can use the mqsicvp command as an ODBC test tool; see Enabling ODBC connections to the databases for further information.

    2. If your message flows use a JDBC connection to a database, enable a JDBC connection for that database. Repeat this step for each database that you want to access in this way.
  3. On z/OS, connect to the database.
  4. Optional: If you want your databases to participate in globally coordinated transactions, configure the environment for global coordination.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:48:29


Task topicTask topic | Version 8.0.0.7 | bz90115_