Before you can create a broker, you must create and configure a database for the broker to use to store its internal data; multiple brokers can store their tables in a single database. Even if you do not use any other databases with WebSphere Message Broker, you must still configure the broker's database so that the broker can connect to it. If your message flows access user databases to manipulate business data, you must also configure these databases so that the broker can connect to them on behalf of the message flows.
There are additional tasks to perform if you want message flow transactions to be globally coordinated, if you use 64-bit execution groups, or if you want to deploy publish/subscribe message flow applications to the broker.
For more information about these issues, see Databases overview.
For additional information about setting up databases
on z/OS, see DB2 planning on z/OS and Customizing the z/OS environment.
To create and configure your databases: