Data sources
An application uses a data source to access the data from
the database.
A data source is associated with a JDBC provider that supplies the specific
JDBC driver implementation class. The data source represents the J2EE Connector
Architecture (JCA) connection factory for the relational resource adapter.
You can create multiple data sources
associated with the same JDBC provider. Each JDBC provider supports the interfaces
defined by Sun Microsystems listed below. These interfaces enable the application
to run in a single-phase or two-phase transaction protocol.
Previously, the function of data access was provided by a single connection
manager (CM) architecture. This connection manager architecture remains available
to support J2EE 1.2 applications, but a new connection manager architecture
is provided, based on the JCA architecture supporting the new J2EE 1.3 application
style.
These two separate CM 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.
- Data source (Version 4.0) - this data source runs under the CM architecture.
Applications using this data source behave as if they were running in Version
4.0.
- Data source - this data source uses the JCA standard architecture to provide
J2EE 1.3 support. It runs under the JCA connection manager and the relational
resource adapter. Applications using this type of data source might behave
differently because of the J2EE 1.3 architecture.
Choice of data source
- J2EE 1.2 application - all enterprise beans, JDBC applications, or Servlets
2.2 components must use the 4.0 data source.
- J2EE 1.3 application -
- EJB 1.1 Module - all EJB 1.x beans must use the 4.0 data source.
- EJB 2.0 Module - enterprise beans that include container-managed persistence
(CMP) Version 2.0 and 1.x must use the new data source.
- JDBC applications and Servlet 2.3 - must use the new data source.

Resource adapter
JDBC providers

Accessing data from application clients
Creating and configuring a data source using the administrative console
Creating and configuring a JDBC provider using the administrative console
Creating and configuring a JDBC provider and data source using the Java Management Extensions API
Configuring data access for application
clients using the Assembly Toolkit and ACRCT![[Version 5.0.2 and later]](../../v502x.gif)
Configuring data access for application
clients using the AAT and ACRCT![[5.0 only]](../../v50.gif)
![[Version 5.0.1]](../../v501.gif)
![[Version 5.0.2]](../../v502.gif)
Creating or changing a resource reference
using the Assembly Toolkit![[Version 5.0.2 and later]](../../v502x.gif)
Creating or changing a resource reference
using the AAT![[5.0 only]](../../v50.gif)
![[Version 5.0.1]](../../v501.gif)
![[Version 5.0.2]](../../v502.gif)
Assembling data access applications using
the Assembly Toolkit![[Version 5.0.2 and later]](../../v502x.gif)
Assembling data access applications using
the AAT![[5.0 only]](../../v50.gif)
![[Version 5.0.1]](../../v501.gif)
![[Version 5.0.2]](../../v502.gif)
Deploying data access applications
Developing data access applications
Creating a JDBC provider on multiple nodes
Migrating a version 4.0 data access application to version 5.1
Creating and configuring a JDBC provider and data source
Searchable topic ID:
datasor
Last updated: Jun 21, 2007 4:55:42 PM CDT
WebSphere Application Server Network Deployment, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/cdat_datasor.html