WebSphere
Business Integration Event 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.
- 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
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; these identifiers separate
the data for each broker.
- 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. 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 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.