Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Service integration > Administer message stores > Administer data stores > Configure a messaging engine to use a data store


Configure a messaging engine data store to use a data source

After configuring a JDBC data source, you can configure a messaging engine data store to use the data source.

To complete this task, have chosen or created a bus and a messaging engine, and the messaging engine must specify data store as its message store type.

We must also have configured a data source, as described in Create the database, schema and user ID for a messaging engine.

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 console to set the data store configuration parameters.


Procedure

  1. In the navigation pane, click Service integration -> Buses -> bus_name -> [Topology] Messaging engines -> engine_name .
  2. Check that the Message store type is Data store.

  3. Click [Additional Properties] Message store. The data store configuration detail panel is displayed.
  4. 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, 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, 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.

    Apache Derby Tip: When you create a new Network Attached Apache Derby data store, by default you get a blank authentication alias. If you use Apache Derby in Network Attached mode with the DB2 Universal JDBC Driver (that is, you use the "JDBC provider for Derby Network Server using the (DB2) Universal JDBC Driver"), specify an authentication alias. This requirement is documented in Data source minimum required settings for Apache Derby. See also the following troubleshooting tip: User ID not supported exception when connecting to a Network Attached Apache Derby v10.3 database

    Create tables

    Select the check box if you want WAS to create the database tables automatically.

    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 WAS attempts to create the tables.

    Number of tables for permanent objects

    Permanent tables contain persistent objects for the data store.

    We 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.

    We can only increase the number of temporary tables, not decrease them.


Configure a JDBC data source for a messaging engine
Generate the DDL statements needed to create data store tables manually
Increasing the number of data store tables to relieve concurrency bottleneck
Create data store tables

+

Search Tips   |   Advanced Search