Using the administrative console to configure the JDBC provider and data source

This topic describes how to configure a JDBC provider and data source for the business process container using the administrative console.

Steps for this task

  1. In the administrative console, click Resources> JDBC Providers.
  2. Click New.
  3. 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).
  4. Click Apply.
  5. 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.
  6. Enter a suitable description for the JDBC provider, for example, JDBC Provider for Process Choreographer
  7. 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

  8. 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.
  9. Click Apply and Save.
  10. Click Resources> JDBC Provider
  11. Select the name of the new provider that you just created.
  12. In Additional Properties, select Data Sources.
  13. Click New.
  14. On the data source panel perform the following actions:
    1. 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.
    2. Enter the JNDI name, for example, jdbc/BPEDB.
    3. Select the check box for container managed persistence.
    4. Enter a suitable description, for example, DataSource for Process Choreographer.
    5. Enter the category Process Choreographer.
    6. Enter the statement cache size, for example, 30 .
    7. 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.
    8. 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.
    9. Click Apply.
  15. Scroll down to Additional Properties and select Custom Properties.
  16. Verify that the settings for your data source match the values described in install wizard settings. If necessary click on a property and change the value.
  17. Save your changes.
  18. 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


Results

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.

What to do next

Configure the queue resources.

Related tasks
Configuring WebSphere Application Server for DB2 access
Related reference
Business process container install wizard settings



Searchable topic ID:   t2damadminconsole
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/workflow/tasks/t2damadminconsole.html

Library | Support | Terms of Use | Feedback