Data sources

Installed applications use a data source to obtain connections to a relational database. A data source is analogous to the Java Platform, Enterprise Edition (Java EE) Connector Architecture (JCA) connection factory, which provides connectivity to other types of enterprise information systems (EIS).

A data source is associated with a JDBC provider, which supplies the driver implementation classes that are required for JDBC connectivity with your specific vendor database. Application components transact directly with the data source to obtain connection instances to your database. The connection pool that corresponds to each data source provides connection management.

You can create multiple data sources with different settings, and associate them with the same JDBC provider. For example, you might use multiple data sources to access different databases within the same vendor database application. WebSphere® Application Server requires JDBC providers to implement one or both of the following data source interfaces, which are defined by Sun Microsystems. These interfaces enable the application to run in a single-phase or two-phase transaction protocol.

Prior to version 5.0 of the application server, the function of data access was provided by a single connection manager (CM) architecture. This connection manager architecture remains available to support Java 2 Platform, Enterprise Edition (J2EE) 1.2 applications, but another connection manager architecture is provided, based on the JCA architecture supporting the J2EE 1.3 application style, J2EE 1.4 and Java EE applications.

These architectures are represented by two types of data sources. To choose the right data source, administrators must understand the nature of their applications, EJB modules, and enterprise beans.

Choice of data source

  • J2EE 1.2 application - all EJB 1.1 enterprise beans, JDBC applications, or Servlet 2.2 components must use the 4.0 data source.
  • J2EE 1.3 (and subsequent releases) application -
    • EJB 1.1 module - all EJB 1.x beans must use the 4.0 data source.
    • EJB 2.0 (and subsequent releases) module - enterprise beans that include container-managed persistence (CMP) Version 1.x, 2.0, and beyond must use the new data source.
    • JDBC applications and Servlet 2.3+ components - must use the new data source.



Related concepts
Relational resource adapters and JCA
JDBC providers
Related tasks
Accessing data from application clients
Configuring a JDBC provider using the administrative console
Configuring a data source using the administrative console
Configuring a JDBC provider using wsadmin
Configuring new data sources using wsadmin
Configuring new WAS40 data sources using wsadmin scripting
Creating and configuring a JDBC provider and data source using the JMX API
Configuring data access for application clients using the assembly tool and ACRCT
Creating or changing a resource reference using the assembly tool
Assembling data access applications using the assembly tool
Deploying data access applications
Developing data access applications
Configuring a JDBC provider for a clustered environment
Migrating applications to use data sources of the current Java EE Connector Architecture (JCA)
Configuring a JDBC provider and data source
Using one-phase and two-phase commit resources in the same transaction
Concept topic Concept topic    

Terms of Use | Feedback

Last updatedLast updated: Sep 19, 2011 3:08:41 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-nd-zos&topic=datasor
File name: cdat_datasor.html