A broker depends on a database to hold configuration and control information. This database must be defined before you create the broker (because creating the broker creates tables within the specified database), and it must be authorized for access by 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.
You 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; this separates the data for each broker.
The Configuration Manager also depends upon a database, known as the configuration repository. This database must be defined before you create the Configuration Manager (because creating the Configuration Manager creates tables within the specified database), and it must be authorized for access by 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 database in DB2.
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).
WebSphere Business Integration Event 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.
If you use DB2 for your broker database on Windows, you can use the same database for the configuration repository but, to simplify maintenance and recovery, you are recommended to create two different databases to hold two independent sets of tables.
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. If you develop message flows that support many publishers or subscribers, you might need to increase your initial sizings.
If you want to create a DB2 database, refer to Creating a DB2 database on Windows and Creating a DB2 database on UNIX platforms for instructions on how to complete this task. You also need to customize a DB2 database for WebSphere Business Integration Event Broker use; this is described in Customizing DB2 databases.
If you want to create an Oracle or Sybase database, refer to Preparing Oracle or Sybase databases on UNIX platforms and to the documentation for the database.
If you want to create the broker database in an alternative database, refer to the documentation for that database.
When you have created the database, you must establish connections to it (described in Connecting to the databases) and authorize access to it (described in Authorizing access to the databases).
Related tasks
Creating a DB2 database on Windows
Creating a DB2 database on UNIX platforms
Customizing DB2 databases
Preparing Oracle or Sybase databases on UNIX platforms
Connecting to the databases
Authorizing access to the databases
Related reference
Supported databases
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ah14430_ |