Creating the databases

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.

  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 Windows or Linux.
  2. Create the database. Instructions are provided for DB2 in Creating a DB2 database on Windows and Creating a DB2 database on Linux and UNIX systems.

    To create a Derby database, see the mqsicreatedb command. Derby database support is described in Using Derby databases on Windows.

    For another database, refer to the documentation for that database. The commands that you can use in relation to databases are described in Issuing database commands on Windows.

  3. If your database is DB2, customize it for WebSphere Event Broker use. Customization is described in Customizing DB2 databases.
  4. Establish connections to the database. Refer to Connecting to the databases.
  5. Authorize access to the database. This task is described in Authorizing access to the databases.
Related concepts
Issuing database commands on Windows
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
Connecting to the databases
Authorizing access to the databases
Related reference
Supported databases
Database locations
mqsicreatedb command
mqsideletedb command
mqsichangedbimgr command