Create the database for a data store
When we are creating a database to use as the data store for our messaging engine, we must choose a relational database management system (RDBMS) and create the database in accordance with your selected RDBMS.
Choose which Relational Database Management System (RDBMS) we want to use for the data store. Unless we are using the embedded Apache Derby provider, create the database before creating a messaging engine. Make a note of the database parameters needed for configuring the data source. See Configure a JDBC data source for a messaging engine.
Tasks
Refer to the documentation for our chosen RDBMS for information about how to create a database.
The default database for a data store is an embedded Apache Derby database. If we 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:
- Create the database server with a page size of at least 4 KB.
- Set the lock scheme property on the server to the value datarows. This avoids the possibility of a deadlock on the data store tables.
- Set the enable housekeeper GC property on the server to the value 5. This improves the ability of the server to reclaim redundant space within the database when it is under heavy load.
- Select the allow nulls by default option for our 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 we 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.
Create users and schemas in the database