Use this task to configure a messaging engine to
use a data source.
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 administrative console to set the data store configuration
parameters.
Perform the following steps to configure the messaging engine to
use a data source:
Configure the data store.
Use the administrative console to complete the following steps- In the navigation pane, click .
- In the content pane, click the name of the bus to which your messaging engine belongs.
- Under Additional Properties, click Messaging
engines. A list of messaging engines displays.
- Click the messaging engine name.
- Under Additional Properties, click Data
store.
- Under General Properties, specify the
following properties:
- Data source 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, ensure that you specify the schema name in lower case.
- Authentication alias
- Select the authentication alias that enables access to the data source.
Cloudscape tip: If you use the Cloudscape Network
Attach mode, you must specify an authentication alias. Cloudscape itself does
not require this authentication alias, but the DB2 Universal JDBC Driver,
which Cloudscape uses when running in Network Attached mode, does require
an alias.
- Create tables
- Select the check box if you want WebSphere Application Server to
create the database tables automatically. For more information, refer to Creating the tables.
Note: The user ID that the data store uses
to connect to the data source must have sufficient authority to create the
database tables and indexes.
DB2 for z/OS restriction: The option for
WebSphere Application Server to
create the tables is not available with DB2 for z/OS. Do not select
Create
tables, otherwise an exception will be thrown when
WebSphere Application Server attempts
to create the tables. Refer to
Enabling your database administrator to create the data store tables if
you use DB2 for z/OS.