Behindthe scenes, the application server retrieves a physical connection from the
connectionpool that corresponds to the database. The pool denes connection attributes
suchas the database name (URL), user name, and password.
3. Nowthat it is connected to the database, the application can read, modify, and add data to
thedatabase.
Theapplications access the database by making calls to the JDBC API. The JDBC driver
translatesthe application’s JDBC calls into the protocol of the database server.
4. Whenit is nished accessing the database, the application closes the connection.
Theapplication server returns the connection to the connection pool. Once it’s back in the
pool,the connection is available for the next application.
Setting Up Database Access
Tosetup a database access:
1. Installa supported database product.
Fora list of database products supported by the Enterprise Server, see the Release Notes.
2. Installa JDBC driver for the database product.
3. Makethe driver’s JARle accessible to the domain’s server instance.
4. Createthe database.
Usually,the application provider delivers scripts for creating and populating the database.
5. Createa connection pool for the database.
6. Createa JDBC resource that points to the connection pool.
Nowto integrate the JDBC driver into an administrative domain, do either of the following:
1. Makethe driver accessible to the common class loader.
Copythe driver’s JARand ZIP les into the domain-dir/lib directory or copy its class les
intothe domain-dir/lib/ext directory.
2. Restartthe domain.
3. Identifythe fully-qualied path name for the driver's JAR le.
SettingUp Database Access
Chapter3 •JDBC Resources 45