When creating
the database for your messaging engine using a data store you must
do it according to your Relational Database Management System (RDBMS)
.
Before you begin
Choose which Relational Database Management System (RDBMS)
you want to use for the data store. Unless you are using the embedded
Cloudscape
Version 10.1.x (Derby) provider, create the database before you
create a messaging engine. Make a note of the database parameters
that you need for configuring the data source. Refer to
Configuring a JDBC data source for a messaging engine for more
information.
Procedure
Refer to the documentation for your chosen RDBMS for information
about how to create a database. The
default database is an embedded Cloudscape Version 10.1.x (Derby) for a
data store. If you have chosen to configure the bus member to use
a data store with default settings, it can only be a server. Unless
the data store database exists already, the messaging engine creates
the database automatically when the messaging engine makes its initial
connection.
Sybase tips:
- Ensure that you create the database server with
a page size of at least 4k.
- Ensure that you set the lock scheme property
on your server to the value datarows. This avoids
the possibility of a deadlock on the data store tables.
- Ensure that you set the enable housekeeper
GC property on your server to the value 5.
This improves the ability of the server to reclaim redundant space
within your database when it is under heavy load.
- Ensure that you select the allow nulls
by default option for your database instance. This is required
for the correct operation of the messaging engine.
Informix tip: The one-to-one relationship between a messaging engine
and a data store means that every messaging engine must have its own
database tables. If you are using the Informix® RDBMS, configure a separate database
instance for each messaging engine. Problems have been observed in
this environment when the data stores for multiple messaging engines
were configured to use separate schemas in the same database.