[Version 5.0.1 and later]Creating and configuring a JDBC provider and data source

This topic outlines the process for configuring access to a relational database, and provides links to more detailed instruction.

Steps for this task

  1. Decide which data source to use: Data source (Version 4.0), see Data Sources (Version 4) or a Version 5.0 data source, see Data Source collection .
  2. Next, 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.
  3. Create a JDBC provider.

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

    OR

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

    OR

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

  4. Create a data source.

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

    OR

    Using the wsadmin scripting client, see Example: Configuring a new data source using wsadmin.

    OR

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

    Tip: Different database vendors require different properties for implementations of their JDBC drivers. Set these properties on the WebSphere Application Server data source. Because Application Server contains templates for many vendor JDBC implementations, the administrative console surfaces the required properties and prompts you for them as you create a data source. However, if you script your data access configurations, you must consult the article Vendor-specific data sources minimum required settings for the required properties and settings options.

  5. Optional: Configure custom properties.
    Like the required properties, custom properties for specific vendor JDBC drivers must be set on the Application Server data source. Consult your database documentation for information about available custom properties.
  6. Bind the resource reference. See Binding to a data source
  7. [Version 5.0.1 and later]Test the connection (for non-container-managed persistence usage). See Test connection.

    Note: When the data source configuration is saved, it will be saved in the resource.xml file. You should not need to modify the jdbc-resource-provider-templates.xml. However, special consideration should be taken if you need to update the jdbc-resource-provider-templates.xml file. See Creating and configuring a JDBC provider and data source using the Java Management Extensions API.


Related concepts
Test connection
JDBC providers
Data sources
Looking up data sources with resource references for relational access
Binding to a data source
Related reference
Data Source collection
Data Sources (Version 4)
JDBC Provider collection



Searchable topic ID:   tccrtprovds
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/ae/tdat_tccrtprovds.html

Library | Support | Terms of Use | Feedback