This topic describes how to configure a JDBC provider and data
source for the business process container using the administrative console.
- In the administrative console, click Resources>
JDBC Providers.
- Click New.
- In the drop-down list for JDBC Providers,
select the template for your database:
- For Cloudscape, select Cloudscape
JDBC Driver (XA).
- For DB2 UDB for Linux, UNIX,
and Windows, select DB2 Legacy CLI-based Type 2 JDBC Driver (XA).
- For DB2 UDB for iSeries, select template
DB2 UDB for iSeries (Toolbox XA).
- For a remote DB2 UDB for z/OS,
select DB2 Legacy CLI-based Type 2 JDBC Driver (XA).
- For Informix Dynamic Server,
select Informix JDBC Driver (XA).
- For Oracle, select Oracle
JDBC Driver (XA).
- For Microsoft SQL Server, using
the WebSphere embedded ConnectJDBC driver, select WebSphere embedded
ConnectJDBC driver for MS SQL Server (XA).
- For Microsoft SQL Server, using
the DataDirect SequeLink JDBC driver, select DataDirect SequeLink
type 3 JDBC driver for MS SQL Server (XA).
- For Sybase Adaptive Server,
select Sybase JDBC Driver (XA).
- Click Apply.
- Enter the JDBC driver name:
- For Cloudscape, enter BPEJdbcDriverCloudscape.
- For DB2 UDB for Linux, UNIX, and Windows, enter BPEJdbcDriverDB2.
- For DB2 UDB for iSeries, enter BPEJdbcDriverDB2iSeries.
- For DB2 UDB for z/OS, enter BPEJdbcDriverDB2zos.
- For Informix Dynamic Server, enter BPEJdbcDriverInformix.
- For Oracle, enter BPEJdbcDriverOracle.
- For Microsoft SQL Server, enter BPEJdbcDriverMsSql.
- For Sybase Adaptive Server, enter BPEJdbcDriverSybase.
- Enter a suitable description for the JDBC provider, for example, JDBC
Provider for Business Process Choreographer
- Enter the class path for the JDBC driver:
- For Cloudscape, enter ${CLOUDSCAPE_JDBC_DRIVER_PATH}/db2j.jar.
- For DB2 UDB for Linux, UNIX, and Windows, enter ${DB2_JDBC_DRIVER_PATH}/db2java.zip.
- For DB2 UDB for iSeries, enter ${OS400_TOOLBOX_JDBC_DRIVER_PATH}/jt400.jar.
- For DB2 UDB for z/OS, enter ${DB2_JDBC_DRIVER_PATH}/db2java.zip.
- For Informix Dynamic Server, enter:
${INFORMIX_JDBC_DRIVER_PATH}/ifxjdbc.jar
${INFORMIX_JDBC_DRIVER_PATH}/ifxjdbcx.jar
- For Oracle, enter ${ORACLE_JDBC_DRIVER_PATH}/ojdbc14.jar.
- For Microsoft SQL Server, using the WebSphere embedded ConnectJDBC driver,
enter:
${WAS_LIBS_DIR}/sqlserver.jar
${WAS_LIBS_DIR}/base.jar
${WAS_LIBS_DIR}/util.jar
${WAS_LIBS_DIR}/spy.jar
- For Microsoft SQL Server, using the DataDirect SequeLink JDBC driver,
enter:
${WAS_LIBS_DIR}/sljc.jar
${WAS_LIBS_DIR}/spy-sl53.jar
- For Sybase Adaptive Server, enter ${SYBASE_JDBC_DRIVER_PATH}/jconn2.jar .
Note: Click Environment>
Manage WebSphere Variables, and check that the variable for the
JDBC driver path is set to an appropriate value. For example, on Windows systems
to c:/sqllib/java. For Microsoft SQL Server, the variable WAS_LIBS_DIR must
point to the WebSphere lib directory
- Enter the implementation class name:
- For Cloudscape, enter com.ibm.db2j.jdbc.DB2jXADataSource.
- For DB2 UDB for Linux, UNIX, and Windows, enter COM.ibm.db2.jdbc.DB2XADataSource.
- For DB2 UDB for iSeries, enter com.ibm.as400.access.AS400JDBCXADataSource.
- For DB2 UDB for z/OS, enter COM.ibm.db2.jdbc.DB2XADataSource.
- For Informix Dynamic Server, enter com.informix.jdbcx.IfxXADataSource.
- For Oracle, enter oracle.jdbc.xa.client.OracleXADataSource.
- For Microsoft SQL Server, using the WebSphere embedded ConnectJDBC driver,
enter com.ibm.websphere.jdbcx.sqlserver.SQLServerDataSource.
- For Microsoft SQL Server, using the DataDirect SequeLink JDBC driver,
enter com.ddtek.jdbcx.sequelink.SequeLinkDataSource.
- For Sybase Adaptive Server, enter com.sybase.jdbc2.jdbc.SybXADataSource.
- Click Apply and Save.
- Click Resources> JDBC Provider
- Select the name of the new provider that you just created.
- In Additional Properties, select Data Sources.
- Click New.
- On the data source panel perform the following actions:
- Enter the data source name:
- For Cloudscape, enter BPEDataSourceCloudscape.
- For DB2 UDB for Linux, UNIX, and Windows, enter BPEDataSourceDb2.
- For DB2 UDB for iSeries, enter BPEDataSourceDb2iSeries.
- For DB2 UDB for z/OS, enter BPEDataSourceDb2zos.
- For Informix Dynamic Server, enter BPEDataSourceInformix.
- For Oracle, enter BPEDataSourceOracle.
- For Microsoft SQL Server, enter BPEDataSourceMsSql.
- For Sybase Adaptive Server, enter BPEDataSourceSybase.
- Enter the JNDI name, for example, jdbc/BPEDB.
- Select the check box for container managed persistence.
- Enter a suitable description, for example, DataSource
for Business Process Choreographer.
- Enter the category Business Process Choreographer.
- Enter the statement cache size, for example, 30 .
- Enter the data source helper class name:
- For Cloudscape, enter com.ibm.websphere.rsadapter.CloudscapeDataStoreHelper.
- For DB2 UDB for Linux, UNIX, and Windows, enter com.ibm.websphere.rsadapter.DB2DataStoreHelper.
- For DB2 UDB for iSeries, enter com.ibm.websphere.rsadapter.DB2AS400DataStoreHelper.
- For DB2 UDB for z/OS, do not use the default value for this field, enter com.ibm.websphere.rsadapter.DB2390DataStoreHelper.
- For Informix Dynamic Server, enter com.ibm.websphere.rsadapter.InformixDataStoreHelper.
- For Oracle, enter com.ibm.websphere.rsadapter.OracleDataStoreHelper.
- For Microsoft SQL Server, using the WebSphere embedded ConnectJDBC driver,
enter com.ibm.websphere.rsadapter.WSConnectJDBCDataStoreHelper.
- For Microsoft SQL Server, using the DataDirect SequeLink JDBC driver,
enter com.ibm.websphere.rsadapter.SequeLinkDataStoreHelper.
- For Sybase Adaptive Server, enter com.ibm.websphere.rsadapter.SybaseDataStoreHelper.
- If
you are not using a Cloudscape database, select the authentication alias that
you want to use to access the database. If necessary, create a
new component-managed authentication alias in Security>
JAAS Configuration> J2C Authentication Data,
by selecting New, entering the user ID and password
to access the database, then clicking Apply and Save.
- Click Apply.
- Scroll down to Additional Properties and
select Custom Properties.
- Verify that the settings for your data source match the values
described in installation wizard settings. If necessary click on
a property and change the value.
- Save your changes.
- If you are using Oracle, you must also create a non-XA data source, by
repeating all the steps in this task, but using the following values:
Field |
Value for non-XA Oracle data source |
JDBC provider name |
Oracle JDBC Driver |
JDBC driver name |
BPEJdbcDriverOracleNonXA |
Classpath |
${ORACLE_JDBC_DRIVER_PATH}/ojdbc14.jar |
Implementation class name |
oracle.jdbc.pool.OracleConnectionPoolDataSource |
Data source name |
BPEDataSourceOracleNonXA |
Data source helper class name |
OracleDataStoreHelper |
The JDBC provider and data source for your database have been configured
for the business process container. The new data source is now listed in the
data source panel.
Configure the queue resources.