WebSphere WebSphere Application Server Version 6.1.x Feature Pack for Web Services Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

Configuring a JDBC data source for a messaging engine

Learn about how to use the WebSphere Application Server administrative console to configure a data source for a messaging engine.

Before you begin
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 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.

Cloudscape (Derby) Tip: For distributed platformsFor i5/OS platforms When you create a new Network Attached Cloudscape Version 10.1.x (Derby) data store, by default you get a blank authentication alias.
DB2 Tip: For z/OS platforms For the z/OS platform, you should use a DB2 Universal JDBC type 4 driver. If you have to 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.

Configure the messaging engine as described in Configuring a messaging engine to use a data source.

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 WebSphere Application Server administrative console to set the data source configuration parameters. Note that your choice of relational database management system (RDBMS) determines the parameters you set.

Perform the following steps to configure the data source:

Procedure

  1. Create a JDBC provider. Refer to Creating and configuring a JDBC provider using the administrative console. 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, refer to Vendor-specific data sources minimum required settings.

  2. Create a data source for the JDBC provider. Refer to Creating and configuring a data source using the administrative console.
    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, refer to Tuning the JDBC data source of a messaging engine.
  3. Test the connection. Refer to Test connection.
Related concepts
JDBC providers
Data sources
Related tasks
Configuring a messaging engine to use a data source
Creating the tables

Task topic

Terms of use | Feedback


Timestamp icon Last updated: 27 November 2008
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.pmc.wsfep.multiplatform.doc/tasks/tjm0040_.html

Copyright IBM Corporation 2004, 2008. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)