Create users and schemas in the database
After creating a database, create the schema in which all tables in the data store are held. Depending on which database we are using, we create one or more database user IDs to enable the messaging engine to access the data store tables.
Before beginning this task, create the database for our messaging engine.
All the tables in the data store must be stored in the same schema. Create more than one data store in a database, provided that we use a different schema name for each data store. Although every messaging engine uses the same table names, its relationship with the schema gives each messaging engine exclusive use of its own tables.
To connect to WebSphere Application Server, create at least one messaging engine user ID. The number of user IDs we need depends on the database we use:
- If we are using Derby, DB2, or Oracle, the messaging engine can be configured to create any additional schemas that might be required for other data stores. That is, if we only create one user, it can have one to many relationships with the schemas in the database. See Configure a messaging engine data store to use a data source for details.
- For all other types of databases, the schemas must be created before starting the messaging engines that depend on them.
If a database user ID can be configured to use multiple schemas, then only that user ID is needed for all messaging engines. Otherwise the user ID is restricted to using tables in its own schema. In this case there can be only one user ID per schema.
Tasks
- Create the users and schema in accordance with the documentation for our chosen relational database management system (RDBMS). With DB2 databases, we create users and schema in separate steps. With the other databases, there is a one-to-one relationship between a schema and a user.
- Ensure that the messaging engine user ID has the privileges required to enable the messaging engine to access the data store tables and, if required, create the data store tables automatically. See Database privileges.
Create the database for a data store Database privileges