Creating the databases

WebSphere Business Integration Message Broker requires a database for each broker and for the Configuration Manager. This topic provides information about these databases and links to topics that tell you how to create them in your chosen database system. If you define message flows that store data into or retrieve data from databases, you can follow the instructions provided for these user databases too.

The broker database
A broker stores configuration and control information in its database. You must define the database before you create the broker (because creating the broker creates tables within the specified database), and you must authorize access to the database for specific users. The broker database is also known as the broker's local persistent store. Choose a unique name for the broker database, for example WBRKBKDB, and keep a note of it for when you create the broker.

If you create a broker on Windows, you can create the broker database in DB2, Oracle, Sybase, or SQL Server. On Linux, you can create the database in DB2 only. On other UNIX platforms, you can create the broker database in DB2, Oracle, or Sybase.

The Configuration Manager database
The Configuration Manager also stores configuration and control information in its database, which is known as the configuration repository. You must define the database before you create the Configuration Manager (because creating the Configuration Manager creates tables within the specified database), and you must authorize access for specific users. Choose a unique name for the configuration repository, for example WBRKCMDB, and keep a note of it for when you create the Configuration Manager.

You must create the configuration repository in DB2.

Database sharing
Start of changeYou can create a database for each broker, or you can use one database for multiple brokers if the platforms are compatible. The tables for each broker are identified with the broker name; these identifiers separate the data for each broker.End of change
Database size
There is no fixed size requirement for either the broker database, or the configuration repository; the size required depends on the complexity of your message flows and message sets. If you develop message flows that include message aggregation or support many publishers or subscribers, you might need to increase your initial sizings.
Database schema
When you create the Configuration Manager or a broker, the database tables required by that component are created in the default schema associated with the user ID used to access that database. You specify this user ID on the create command (mqsicreateconfigmgr or mqsicreatebroker).
  • For DB2 and Oracle, the default behavior is for the schema name to default to the user ID used to access the database.
  • For Sybase and SQLServer, the typical behavior is to use the database owning schema (dbo).

WebSphere Business Integration Message Broker does not require a particular schema or set of tablespaces; you can configure the database and access privileges of the user ID to choose your own values.

  1. On UNIX systems, complete the setup procedures defined in Preparing databases on UNIX systems before you create the database. You do not have to complete this task if your database is on WindowsStart of change or LinuxEnd of change.
  2. Start of changeCreate the database. Instructions are provided for DB2 in Creating a DB2 database on Windows and Creating a DB2 database on Linux and UNIX systems.

    For another database, refer to the documentation for that database.

    End of change
  3. If your database is DB2, customize it for WebSphere Business Integration Message Broker use. Customization is described in Customizing DB2 databases.
  4. Establish connections to the database. Refer to Configuring access to databases.
  5. Authorize access to the database. This task is described in Authorizing access to the databases.
Related tasks
Preparing databases on UNIX systems
Creating a DB2 database on Windows
Creating a DB2 database on Linux and UNIX systems
Customizing DB2 databases
Configuring access to databases
Authorizing access to the databases
Related reference
Supported databases