Data sources for IBM Business Process Manager

Data sources provide a link between applications and relational databases. The data sources that you use are affected by whether you set up a stand-alone environment or a network deployment environment.

Applications use a data source to obtain connections to a relational database. A data source is analogous to the Java™ EE Connector Architecture (JCA) connection factory, which provides connectivity to other types of enterprise information systems (EIS).

A data source is associated with a Java Database Connectivity (JDBC) provider, which supplies the driver implementation classes that connect with a specific type of database. Application components interact directly with the data source to obtain connection instances to your database. The connection pool that corresponds to each data source provides connection management.

You can create multiple data sources with different settings, and associate them with the same JDBC provider. For example, you might use multiple data sources to access different databases within the same database application. In IBM® Business Process Manager, JDBC providers must implement one or both of the following data source interfaces. Use these interfaces to run the application in a single-phase or two-phase transaction protocol.

Note: Business Process Choreographer data sources are created using the Business Process Choreographer configuration tools. Refer to Configuring Business Process Choreographer .

ConnectionPoolDataSource: A data source that supports application participation in local and global transactions, except two-phase commit transactions. When a connection pool data source is involved in a global transaction, the transaction manager does not provide transaction recovery. The application is responsible for providing the backup recovery process if multiple resource managers are involved.

XADataSource: A data source that supports application participation in any single-phase or two-phase transaction environment. When this data source is involved in a global transaction, the WebSphere® Application Server transaction manager provides transaction recovery.

The following tables provide examples of typical stand-alone environment setups and typical deployment environment setups:

Table 1. Typical stand-alone environment setup
Datasource	Component	Scope	JNDI Name
WBI DataSource	CommonDB	Node	jdbc/WPSDB
SCA Application Bus ME data source	SCA ME	Server	jdbc/com.ibm.ws.sib/nlNode01.server1-SCA.APPLICATION.localhostNode01Cell.Bus
Business Process Choreographer data source	BPC	Server	jdbc/BPEDB
Business Process Choreographer ME data source	BPC ME	Server	jdbc/com.ibm.ws.sib/nlNode01.server1-BPC.localhostNode01Cell.Bus
event	CEI	Server	jdbc/cei
CEI ME data source	CEI ME	Server	jdbc/com.ibm.ws.sib/nlNode01.server1-CEI.`cellName`.BUS

Table 2. Typical deployment environment setup
Datasource	Component	Scope	JNDI Name
WBI DataSource	CommonDB	Cell	jdbc/WPSDB
SCA Application Bus ME data source	SCA ME	Cluster	jdbc/com.ibm.ws.sib/clusterone-SCA.APPLICATION.enduranceTestCell01.Bus
Business Process Choreographer data source	BPC	Cluster	jdbc/BPEDB
Business Process Choreographer ME data source	BPC ME	Cluster	jdbc/com.ibm.ws.sib/clusterone-BPC.enduranceTestCell01.Bus
event	CEI	Cluster	jdbc/cei
CEI ME data source	CEI ME	Cluster	jdbc/com.ibm.ws.sib/clusterone-CEI.`cellName`.BUS