1 Introduction and Roadmap

This chapter describes the contents and organization of this guide—Programming JDBC for Oracle WebLogic Server.

Document Scope and Audience

This document is a resource for software developers and system administrators who develop and support applications that use the Java Database Connectivity (JDBC) API. It also contains information that is useful for business analysts and system architects who are evaluating WebLogic Server. The topics in this document are relevant during the evaluation, design, development, pre-production, and production phases of a software project.

It is assumed that the reader is familiar with Java EE and EJB concepts. This document emphasizes the value-added features provided by WebLogic Server EJBs and key information about how to use WebLogic Server features and facilities to get an EJB application up and running.

Guide to this Document

Related Documentation

This document contains JDBC-specific programming information.

For comprehensive guidelines for developing, deploying, and monitoring WebLogic Server applications, see the following documents:

JDBC Samples and Tutorials

In addition to this document, Oracle provides a variety of JDBC code samples that show JDBC configuration and API use, and provide practical instructions on how to perform key JDBC development tasks.

Avitek Medical Records Application (MedRec)

MedRec is an end-to-end sample Java EE application shipped with WebLogic Server that simulates an independent, centralized medical record management system. The MedRec application provides a framework for patients, doctors, and administrators to manage patient data using a variety of different clients.

MedRec demonstrates WebLogic Server and Java EE features, and highlights Oracle-recommended best practices. MedRec is included in the WebLogic Server distribution, and can be accessed from the Start menu on Windows machines. For Linux and other platforms, you can start MedRec from the WL_HOME\samples\domains\medrec directory, where WL_HOME is the top-level installation directory for WebLogic Platform.

JDBC Examples in the WebLogic Server Distribution

WebLogic Server optionally installs API code examples in the WL_HOME\samples\domains\medrec directory, where WL_HOME is the top-level directory of your WebLogic Server installation. You can start the examples server, and obtain information about the samples and how to run them from the WebLogic Server Start menu.

New and Changed Features in This Release

This release includes the following new and changed features:

For a comprehensive listing of the new WebLogic Server features introduced in this release, see What's New in Oracle WebLogic Server.

Java EE 6 DataSource Resource Definintions

Java EE 6 provides the option to programmatically define DataSource resources for a more flexible and portable method of database connectivity. See Using DataSource Resource Definitions.

Oracle Type 4 JDBC drivers from DataDirect

Oracle Type 4 JDBC drivers from DataDirect are now referred to as WebLogic-branded DataDirect drivers. Oracle has retired the documentation in Type 4 JDBC Drivers for Oracle WebLogic Server and no longer provides detailed information on DataDirect drivers. Oracle continues to provide information on how WebLogic-branded drivers are configured and used in WebLogic Server environments at Using WebLogic-branded DataDirect Drivers. Oracle recommends reviewing DataDirect documentation for detailed information on driver behavior, see "Progress DataDirect for JDBC User's Guide Release 4.2" and "Progress DataDirect for JDBC Reference Release 4.2" at http://www.datadirect.com/index.html.

Secure RMI Driver Communication

Secure RMI driver client communication with DataSource objects at the server level by setting the RMI JDBC Security parameter, see Security Considerations for WebLogic RMI Drivers.


The following weblogic.jdbc.extensions interfaces and exceptions are deprecated in WebLogic Server

  • weblogic.jdbc.extensions.Driverinterceptor

  • weblogic.jdbc.extensions.ConnectionDeadSQLEsception

  • weblogic.jdbc.extensions.Connection UnavailableSQLEsception

  • weblogic.jdbc.extensions.PoolDisabledSQLException

  • weblogic.jdbc.extensions.PoolLimitSQLException

  • weblogic.jdbc.extensions.PoolPermissionsSQLException

  • weblogic.jdbc.extensions.PoolUnavailableSQLException