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.

Restriction: When 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 IBM MQ server definitions are also used. If the configuration includes IBM MQ server definitions and we are using a data store, we must use type 4 JDBC drivers.

Apache Derby Tip: (iSeries) (Dist) When we create a new Network Attached Apache Derby data store, by default we get a blank authentication alias. If we use Network Attached mode with the DB2 Universal JDBC Driver (that is, we 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 Version 10.3 database

(ZOS) DB2 Tip: For the z/OS platform, we should use a DB2 Universal JDBC type 4 driver. If we must use the DB2 Universal JDBC type 2 driver, set the JDBC driver custom property fullyMaterializeLobData to false. See 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.

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.

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

Tasks

1. Create a JDBC provider.

   Under General Properties, in the Select the implementation type field, ensure that we select Connection pool data source.

   See Data source minimum required settings, by vendor.

2. Create a data source for the JDBC provider.

   1. Under Additional Properties, ensure that we select Data sources.

   2. Configure the connection pool for the JDBC data source.

      Set the Maximum connections to the number of connections required, for example, at least 50. The default number of connections is 10.

3. Test the connection using the test connection service.

Related:

JDBC providers

Data sources

Add a messaging engine to a cluster

Configure a messaging engine data store to use a data source

Create data store tables