WebSphere Event Broker requires
a database for each broker.
This topic provides information about these databases and links to topics
that tell you how to create them in your chosen database system.
On Windows, if you use the Default Configuration
wizard, it automatically creates a broker database for the default broker,
either in DB2 or in Derby. The following information also applies to databases
created by the wizard.
- 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 Linux or UNIX, depending on your operating system,
you can create the broker database in DB2, Oracle, or Sybase, or an SQL Server
database on a Windows machine. On Windows, you can create the broker database
in DB2, Oracle, Sybase, SQL Server, or Derby. See Supported databases to
check which databases are supported on your operating system.
- The Configuration
Manager database
- The Configuration
Manager also stores configuration and control
information in its database, which is known as the internal configuration
repository. It is created and managed automatically by the Configuration
Manager.
- 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 the
broker database;
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.
- Database schema
- When you create 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 (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 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.