Usage

DataSource is used in different ways, in different applications.

All options are presented with some code examples. For more information, see the JDBC 2.0 Optional Package (formerly the JDBC 2.0 Standard Extension API), and the JNDI documentation on the Oracle Java Web site.

Configuration by Administrator: LDAP
jConnect has supported LDAP connectivity since version 4.0. As a result, the recommended approach, which requires no custom software, is to configure DataSources as LDAP entries using the LDAP Data Interchange Format (LDIF).
Access by Client
A JDBC client application allows you to access the server name to obtain a reference to a DataSource object, instead of accessing the DriverManager and providing a JDBC URL.
Programmatic Configuration
The purpose of programmatic configuration is to define a data source, then deploy it under a logical name to a name server.
Retrieve Datasource Object by Client
The client retrieves the DataSource object by setting its JNDI properties the same way the DataSource was deployed.

Parent topic: JNDI for Naming Databases