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]](../images/dist.gif)
![[IBM i]](../images/iseries.gif)
![[IBM i]](../images/iseries.gif)
![[AIX Solaris HP-UX Linux Windows]](../images/dist.gif)
![[IBM i]](../images/iseries.gif)
![[AIX Solaris HP-UX Linux Windows]](../images/dist.gif)
![[IBM i]](../images/iseries.gif)
![[AIX Solaris HP-UX Linux Windows]](../images/dist.gif)
![[z/OS]](../images/ngzos.gif)
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.