1 Introduction and Roadmap

This section describes the contents and organization of this guide—Oracle Fusion Middleware Configuring and Managing JDBC Data Sources 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.

This document does not address specific JDBC programming topics. For links to WebLogic Server documentation and resources for this topic, see Related Documentation.

It is assumed that the reader is familiar with Java EE and JDBC concepts. This document emphasizes the value-added features provided by WebLogic Server.

Guide to this Document

Related Documentation

This document contains JDBC data source configuration and administration 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 and tutorials that show configuration and API use, and provide practical instructions on how to perform key JDBC development tasks.

Avitek Medical Records Application (MedRec) and Tutorials

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 WL_HOME\samples\server\examples\src\examples, 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 JDBC Data Source 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.

Enhanced Oracle RAC Support

This release provides a new data source type, a GridLink Data Source, to provide enhanced support for Oracle RAC. GridLink Data Sources provide:

  • A simplified and consolidated method to configure Oracle RAC connectivity between a single WebLogic Server data source and a service targeted to an Oracle RAC cluster.

  • The ability to adaptively respond to state changes in the Oracle RAC Cluster, including support for:

    • Fast Connection Failover (FCF)

    • Runtime Connection Load Balancing (RCLB)

    • Graceful data base shutdown

  • Additional performance features, such as XA Affinity for global transactions, that ensures all the data base operations performed on an Oracle RAC cluster are directed to the same Oracle RAC instance.

  • Supports for Oracle Single Client Access Name (SCAN) addresses. This allows multiple GridLink data source database listener addresses and ONS daemon addresses to register to SCAN listeners and appear as a single name used to access an Oracle RAC instance. A GridLink data source containing SCAN addresses does not need to change if you add or remove Oracle RAC nodes.

For more information, see Using GridLink Data Sources

Reorganization of JDBC Resources

JDBC resources have been reorganized within the WebLogic Server Administration Console domain tree. Generic Data Sources, GridLink Data Sources, and Multi Data Sources are all located under the Services > Data Sources brance of the Domain Tree in the Administration Console.

Data Source Factories

Data Source Factories (deprecated) are still supported in this release but do not appear in the domain tree unless you have upgraded an existing domain that contains Data Source Factories. If your upgraded domain contains Data Source Factories, they will be located under Services > Data Source Factories branch of the Domain Tree in the Administration Console.

Performance Enhancements

This release supports provides several Data Source performance enhancements when using a supported Oracle driver, including:

  • Oracle Net Sdp

  • Oracle Dynamic Buffering

  • Oracle Reduced Data Copies

These enhancements may require specific hardware, software, and configuration. For more information, see Configuring Oracle Parameters.

Connection-based System Properties

This release supports setting driver properties using the value of system propertiessee Enabling Connection-based System Properties.

Keep Connection After Local Transaction

This release provides a new attribute, Keep Connection After Local Transaction, that enables WebLogic Server to keep a physical database connection associated with a logical connection when committing or rolling back a local transaction. See KeepConnAfterLocalTx in the Oracle WebLogic Server MBean Reference.