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

Creating and configuring a JDBC provider and data source

Applications access relational databases through two primary objects, the JDBC provider and the data source. You can configure these objects at the application, server, cluster, node, or cell scope.

Before you begin

Determine which version of data source you need. If you are using the Enterprise JavaBean (EJB) 1.0 specification or the Java Servlet 2.2 specification, you need the Version 4.0 data source. If you are using more advanced releases of these specifications, you need the current version data source (which is designated in WebSphere Application Server simply as "Data source," with no associated version number).

Steps for this task

  1. Determine which JDBC provider is appropriate for your data source version, database configuration, and application requirements. The topic Vendor-specific data sources minimum required settings is a comprehensive source for this information. It includes a summary table and detailed listings.
  2. Create a JDBC provider.

    From the administrative console, see Creating a JDBC provider using the administrative console.

    OR

    Using the wsadmin scripting client, see Configuring a JDBC provider using scripting.

    OR

    Using the Java Management Extensions (JMX) API, see Creating a JDBC provider and data source using the Java Management Extensions API.

  3. Create a data source.

    From the administrative console, see Creating a data source using the administrative console.

    OR

    Using the wsadmin scripting client, see Configuring new data sources using scripting. (For V4 data sources, see Configuring new WAS40 data sources using scripting.)

    OR

    Using the JMX API, see Creating a JDBC provider and data source using the Java Management Extensions API.

  4. Bind the resource reference. See Binding to a data source
  5. Test the connection (for non-container-managed persistence usage). See Test connection.
    Note: When you save the data source configuration, it is saved in a resource.xml file. In most environments, you should not need to modify the jdbc-resource-provider-templates.xml file. However, if updating the file becomes necessary, observe the special considerations that are discussed in J2EE Connector Architecture migration tips.



Sub-topics
Vendor-specific data sources minimum required settings
Creating and configuring a JDBC provider using the administrative console
Creating and configuring a data source using the administrative console
Creating and configuring a JDBC provider and data source using the Java Management Extensions API
Verifying a connection
Test connection service

Related concepts
JDBC providers
Data sources
Looking up data sources with resource references for relational access
Binding to a data source

Related tasks
Configuring a JDBC provider using scripting
Configuring new data sources using scripting
Configuring new WAS40 data sources using scripting

Related reference
Data source collection
Data sources (Version 4)
JDBC Provider collection

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_tccrtprovds.html

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