Configuring a JDBC data source for a messaging engine

If you 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.

Before you begin

Restriction: When you are configuring a service integration bus member to use a data store, be aware that using a type 2 JDBC driver for the data store is not supported for configurations where WebSphere® MQ server definitions are also used. If your configuration includes WebSphere MQ server definitions and you are using a data store, you must use type 4 JDBC drivers.
[AIX Solaris HP-UX Linux Windows][IBM i]Apache Derby Tip: [AIX Solaris HP-UX Linux Windows][IBM i]When you create a new Network Attached Apache Derby data store, by default you get a blank authentication alias. [AIX Solaris HP-UX Linux Windows][IBM i]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), you must specify an authentication alias. This requirement is documented in Data source minimum required settings for Apache Derby. [AIX Solaris HP-UX Linux Windows][IBM i]See also the following troubleshooting tip: User ID not supported exception when connecting to a Network Attached Apache Derby Version 10.3 database
[z/OS]DB2 Tip: For the z/OS® platform, you should use a DB2 Universal JDBC type 4 driver. If you must use the DB2 Universal JDBC type 2 driver, you must set the JDBC driver custom property fullyMaterializeLobData to false. For more information, see the following troubleshooting tip: Messaging engine does not start up with a DB2 Universal JDBC type 2 driver.
Oracle Tip: Use the Oracle 10g thin driver for the service integration data store. This driver is compatible with earlier versions of Oracle.

About this task

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 that contains the data store for that messaging engine.

Use the administrative console to set the data source configuration parameters. Note that your choice of relational database management system (RDBMS) determines the parameters you set.

Procedure

  1. Create a JDBC provider.
    Under General Properties, in the Select the implementation type field, ensure that you select Connection pool data source.

    For information about the settings for your chosen RDBMS, see Data source minimum required settings, by vendor.

  2. Create a data source for the JDBC provider.
    1. Under Additional Properties, ensure that you select Data sources.
    2. Configure the connection pool for the JDBC data source. Set the Maximum connections to the number of connections you require, for example, at least 50. The default number of connections is 10.
      For more information, see Tuning the JDBC data source of a messaging engine.
  3. Test the connection by using the test connection service provided for validating data source configurations