After you have
created a database, you need to create the schema in which all tables
in the data store are held.
Before you begin
Before you begin this task, create the database for your messaging
engine.
About this task
To connect to WebSphere
® Application Server, the database
administrator must create at least one user. The number of user IDs
you need depends on the database you use:
- If you are using Derby, DB2® or
Oracle, then the messaging engine can be configured to create any
additional schemas that may be required for other data stores. That
is, if you only create one user, it can have one to many relationships
with the schemas in the database. Refer to Configuring a messaging engine to use a data source for details.
- For all other types of databases, the schema must be created prior
to starting the messaging engines that depend on them.
If the user ID can be configured
to use multiple schemas then only that user ID is needed for all messaging
engines. Otherwise the user is restricted to using tables in its own
schema. In this case there can only be one user ID per schema.
Procedure
- Refer to the documentation for your chosen relational database
management system (RDBMS) for more information about how to create
users and schema. With DB2 databases,
you create users and schema in separate steps. With the other databases,
there is a one-to-one relationship between a schema and a user.
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.
- Refer to Database privileges for
information about the authorities that you require to access the data
store.