WAS v8.5 > Administer applications and their environment > Welcome to administering Service integration > Administer message stores > Administer data stores

Configure a messaging engine to use a data store

Although the default message store for a typical messaging engine is file store, we can also configure a messaging engine to use a data store. Each messaging engine has its own file store or data store. If the data store is chosen the messaging engine uses an instance of a JDBC data source to interact with the database containing the data store for that messaging engine.

When a new messaging engine that uses a data store is created on a single server, it is configured to use an Apache Derby data source by default. This enables the messaging engine to run without needing any additional configuration.

To configure a new messaging engine to use your chosen data source when we create that messaging engine on a single server, see Add a server as a new bus member.

If we do not want to use the default data source configuration, we can use the WebSphere Application Server dmgr console to change the configuration parameters. For example, we can change the data source or we can configure the data store to use a different JDBC provider.

WAS supports direct customer use of the Apache Derby database in test environments only. WAS v8.5 does not support direct customer use of Apache Derby database in production environments.

Subtopics

• Create the database, schema and user ID for a messaging engine
  Before the data store for a messaging engine can be set up, first create the database, the schema and the database user ID the messaging engine needs to access the data store tables.
• Create data store tables
  When you create the data store tables, we have two options. We can either choose that WAS does it automatically, or the database administrator does it manually.
• Configure a JDBC data source for a messaging engine
  If we are using a data store for a messaging engine, the messaging engine uses an instance of JDBC data source to interact with the database containing the data store.
• Configure a messaging engine data store to use a data source
  After configuring a JDBC data source, we can configure a messaging engine data store to use the data source.

Subtopics

• Create the database, schema and user ID for a messaging engine
  Before the data store for a messaging engine can be set up, first create the database, the schema and the database user ID the messaging engine needs to access the data store tables.
• Create data store tables
  When you create the data store tables, we have two options. We can either choose that WAS does it automatically, or the database administrator does it manually.
• Configure a JDBC data source for a messaging engine
  If we are using a data store for a messaging engine, the messaging engine uses an instance of JDBC data source to interact with the database containing the data store.
• Configure a messaging engine data store to use a data source
  After configuring a JDBC data source, we can configure a messaging engine data store to use the data source.

Related concepts:

Bus members

Related

Tune the JDBC data source of a messaging engine
Add a server as a new bus member

Related information:

Data store [Settings]

+

Search Tips   |   Advanced Search