After configuring a JDBC data source, you can configure a messaging
engine data store to use the data source.
About this task
A messaging engine uses an instance of a JDBC data source to interact
with the database that contains the data store for that messaging engine.
Use
the WebSphere® Application Server administrative
console to set the data store configuration parameters.
Procedure
- In the navigation pane, click .
- Check that the Message store type is Data
store.
- Click [Additional Properties] Message store.
The data store configuration detail panel is displayed.
- Specify the following data store configuration details:
- Data source JNDI name
- Type the JNDI name of the data source that provides access to database
that holds the data store.
- Schema name
- Type the name of the database schema that contains the tables used by
the data store.
General tip: The schema name
is usually the same as the user ID that is declared in the authentication
alias. With some databases, for example DB2®, you can provide an alternative schema
name. For more information about the relationship between users and schema,
refer to the documentation for your chosen RDBMS.
Informix tip: When you configure your messaging engine
to use an Informix® database,
you must specify the schema name in lowercase letters.
When
it is starting, a messaging engine that uses a data store checks to see if
its data store exists. If the Create tables option is selected for
the configuration, the messaging engine creates the tables in its chosen schema.
The
Schema
name field is optional. If you require a schema name, consider the following:
- The default schema name is IBMWSSIB.
- If you delete the text so that field is blank, the messaging engine takes
the user id defined in the authentication alias to be the schema name.
- If you define a schema name explicitly, that schema name is used by the
messaging engine.
- If there are multiple messaging engines, you must configure each messaging
engine to use a unique schema, otherwise FFDC error messages stating that Connection
cannot be provided as Datasource has been disabled! might appear.
This applies to DB2 in particular.
- Authentication alias
- Select the authentication alias that enables access to the data source.
- Create tables
- Select the check box if you want WebSphere Application Server to
create the database tables automatically. For more information, see Planning the configuration of a messaging engine to use a data store.
Note: The user ID that the
messaging engine uses to connect to the data source must have sufficient authority
to create the database tables and indexes.
DB2 for z/OS restriction: Do not select Create tables if you are
using DB2 for z/OS, otherwise an exception will be thrown when WebSphere Application Server attempts
to create the tables.
- Number of tables for permanent objects
- Permanent tables contain persistent objects for the data store.
Note: You
can only increase the number of permanent tables, not decrease them.
- Number of tables for temporary objects
- Temporary tables contain nonpersistent objects that have been saved to
the data store to reduce the messaging engine memory requirement.
Note: You
can only increase the number of temporary tables, not decrease them.