Why and when to perform this task
After you create a JDBC provider, you must create a data source to access the backend data store. Application components use the data source to access connection instances to your database; a connection pool is associated with each data source. The product supports two different versions of data source:Steps for this task
For data sources of the latest standard version:
Important:(For components with res-auth=Container) Both the Container-managed Authentication Alias and Mapping-Configuration Alias settings are deprecated. They are superseded by the specification of a login configuration on the resource-reference mapping at deployment time. You must now use this login setting to define the aliases at deployment.
What to do next
You are now ready to install the application for which you configured the data sources. During installation, you can bind resource references to these data sources.Related concepts
Binding to a data source
Data sources
JDBC providers
Security of lookups with component managed authentication
Related reference
WebSphere Application Server data source properties collection
Example: Using the Java Management Extensions API to create a JDBC
driver and data source for bean-managed persistence, session beans, or servlets
Example: Using the Java Management Extensions API to create a JDBC
driver and data source for container-managed persistence
Vendor-specific data sources minimum required settings
Data source settings
Data source (Version 4) settings
Connection pool settings