WebSphere Application Server - Express, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Creating and configuring a JDBC provider using the administrative console

Why and when to perform this task

An application installed on WebSphere Application Server accesses a relational database through a JDBC provider, which is essentially a system-level software driver. For at-a-glance information on which provider type is appropriate for your database configuration and application requirements, see the JDBC provider table.

You can easily establish a JDBC provider from the administrative console.

Steps for this task

  1. Open the administrative console.
  2. Click Resources > JDBC Providers.
  3. Select the scope of your definition. (This scope becomes the scope of your data source.) You can choose cell, node, cluster, or server. For more information, see Administrative console scope settings.
  4. Click New.
    Note: If Java script is disabled for your browser, you do not see the three drop-down lists that are described in the next three steps (for database type, provider type, and implementation type) . Instead, you see a single drop-down box that lists all JDBC provider choices simultaneously (inclusive of every database, provider, and implementation type).
  5. Use the first drop-down list to select the database type of the JDBC provider you need to create. If the list of supported JDBC provider types does not include the JDBC provider that you want to use, select the User-Defined JDBC Provider. Then consult the JDBC provider vendor's documentation for information on specific properties required for data sources associated with this provider, and skip to step eight of this list.
  6. From the second drop-down list, select your JDBC provider type.
  7. From the third drop-down list, select the implementation type necessary for your application. If your application does not require that connections support two-phase commit transactions, choose Connection Pool Data Source. Choose XA Data Source, however, if your application requires connections that support two-phase commit transactions. Applications using this data source configuration have the benefit of container-managed transaction recovery.
  8. Click Next to view the general property settings page for your JDBC provider.
  9. Ensure that all required properties have valid values. For more information, see JDBC Provider settings.
  10. Click Apply to view the page with your new JDBC provider settings. Note that two active data source links now appear under the Additional Properties heading on this page. To set up a data source, click the link that corresponds to the type required by your application, the Version 4 data source or the later version data source. (For more information, refer to the section entitled "Choice of data source" in the Data sources topic.)
  11. Click OK to return to the JDBC providers page, where your new JDBC provider appears in the list.
    Attention: If you modify the class path or native library path of a JDBC provider: After clicking OK, you must restart every application server within the scope of that JDBC provider for the new configuration to work. Otherwise, you receive a data source failure message.

What to do next

For detailed information on creating a data source for association with your JDBC provider, see Creating and configuring a data source using the administrative console.



Sub-topics
JDBC Provider collection

Related concepts
JDBC providers
Data sources

Related tasks
Creating and configuring a data source using the administrative console

Related reference
Vendor-specific data sources minimum required settings
Data source settings

Task topic    

Terms of Use | Feedback

Last updated: Jun 8, 2005 12:45:23 PM EDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/tdat_ccrtprov.html

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