WebSphere® Event Broker uses databases to store internal data about the broker. You must create and configure the broker database before you can create a broker.
WebSphere Event Broker supports the databases that are listed in Supported databases
A broker stores
configuration and control information in its database. You must create
the broker database before you can create the broker because when
the broker is created, the broker's tables are automatically created
and initialized.
If you create a broker on Linux® or UNIX® systems, depending on your
operating system, you can create the broker database in DB2®, Oracle, SQL Server, or Sybase.
On Windows®, you
can create the broker database in DB2,
Oracle, SQL Server, Sybase, or Derby. See Supported databases to
check which databases are supported on your operating system.
If you create a 64-bit execution groups in the broker, the broker database must be a 64-bit database instance.
You can create a database schema for each broker, or you can configure brokers to share a database schema if all brokers are at the same version.
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.
The size of the broker database is not fixed; it 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.
When you have created a broker database, you must enable a connection from the broker to the database. On all platforms except Linux on System z® and Linux on POWER™, the broker connects to databases using ODBC. For 32-bit brokers (all platforms except HP-UX on Itanium) , you must always enable a 32-bit ODBC connection. For 64-bit brokers (HP-UX on Itanium only) , you must always enable a 64-bit ODBC connection. ODBC drivers are supplied with WebSphere Event Broker.
For more information about enabling 32-bit and 64-bit connections to the broker database see Broker database connections
On Windows or Linux on x86, if you use the Default Configuration wizard to create the Default Configuration, the wizard automatically creates a broker database for the broker. On Linux systems, the wizard creates the broker database using DB2; on Windows, if DB2 is not installed, the wizard uses the Derby database manager by default, although you can choose to use DB2 if it is installed.