This section describes the contents and organization of this guide—Administering JDBC Data Sources for Oracle WebLogic Server.
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.
This chapter, Chapter 1, "Introduction and Roadmap," introduces the organization of this guide and lists new features in the current release.
Chapter 2, "Configuring WebLogic JDBC Resources," provides an overview of WebLogic JDBC resources.
Chapter 3, "Configuring JDBC Data Sources," describes WebLogic JDBC data source configuration.
Chapter 4, "Configuring JDBC Multi Data Sources," describes WebLogic JDBC multi data source configuration.
Chapter 5, "Using Active GridLink Data Sources," describes WebLogic Active GridLink Data Source configuration.
Chapter 6, "Advanced Configurations for Oracle Drivers and Databases," provides advanced configuration options that can provide improved data source and driver performance when using Oracle drivers and databases.
Chapter 7, "Connection Harvesting," describes how to configure and use connection harvesting in your applications.
Chapter 8, "Labeling connections," provides information on how to label connections to increase performance.
Chapter 9, "JDBC Data Source Transaction Options," provides information on XA, non-XA, and Global Transaction options for WebLogic data sources.
Chapter 10, "Understanding Data Source Security," provides information on how WebLogic Server uses configuration options to secure JDBC data sources.
Chapter 11, "Creating and Managing Oracle Wallet," provides information on how to create and manage an Oracle Wallet to store database credentials for WebLogic Server datasource definitions.
Chapter 12, "Deploying Data Sources on Servers and Clusters," provides information on how to deploy data sources on servers and clusters.
Chapter 13, "Using WebLogic Server with Oracle RAC," describes how to configure WebLogic Server for use with Oracle Real Application Clusters.
Chapter 14, "Using JDBC Drivers with WebLogic Server," describes how to use JDBC drivers from other sources in your WebLogic JDBC data source configuration.
Chapter 15, "Monitoring WebLogic JDBC Resources," describes how to monitor JDBC resources, gather profile information about database connection usage, and enable JDBC debugging.
Chapter 16, "Managing WebLogic JDBC Resources," describes how to administer data sources.
Chapter 17, "Tuning Data Source Connection Pools," provides information on how to properly tune the connection pool attributes in JDBC data sources in your WebLogic Server domain to improve application and system performance.
Appendix A, "Using an Oracle 12c Database," provides information on how to configure WebLogic Server Release 12.1.2 to interoperate with an Oracle 12c database.
Appendix B, "Configuring JDBC Application Modules for Deployment," describes how to package a WebLogic JDBC module with your enterprise application.
Appendix C, "Using Multi Data Sources with Oracle RAC," describes how to configure multi data sources for use with Oracle Real Application Clusters.
Appendix D, "Using Connect-Time Failover with Oracle RAC (Deprecated)," describes how WebLogic Server provides Connect-Time Failover (deprecated) for legacy applications that use data sources configured to use connect-time failover and load balancing.
Appendix E, "Using Fast Connection Failover with Oracle RAC," describes how to use WebLogic server with Oracle Fast Connection Failover.
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:
Developing JDBC Applications for Oracle WebLogic Server is a guide to JDBC API programming with WebLogic Server.
Developing Applications for Oracle WebLogic Server is a guide to developing WebLogic Server applications.
Deploying Applications to Oracle WebLogic Server is the primary source of information about deploying WebLogic Server applications in development and production environments.
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.
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 optionally installed with the WebLogic Server installation. You can start MedRec from the ORACLE_HOME\user_projects\domains\medrec directory, where ORACLE_HOME is the directory you specified as the Oracle Home when you installed Oracle WebLogic Server.
WebLogic Server optionally installs API code examples in EXAMPLES_HOME\wl_server\examples\src\examples, where EXAMPLES_HOME represents the directory in which the WebLogic Server code examples are configured. For more information, see "Sample Applications and Code Examples" in Understanding Oracle WebLogic Server.
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.
WebLogic Server 12.1.2.0 is certified to operate with the Oracle 12c database and Oracle 12c JDBC driver. For details, see "Supported Configurations" in What's New in Oracle WebLogic Server.
This release of WebLogic Server supports the JDBC 4.1 Specification when the environment is using JDK 7 and the JDBC driver is JDBC 4.1 compliant. To use new JDBC 4.1 methods with the Oracle thin client, you must use the ojdbc7.jar. If the methods are called for a driver that does not support JDBC 4.1, a java.lang.AbstractMethodError is thrown. See "JDBC™ 4.1 Specification" at https://download.oracle.com/otndocs/jcp/jdbc-4_1-mrel-spec/index.html.
Note:
WebLogic Server currently does not support thejava.sql.driver interfaces required to use the Java SE 7 getParrentLogger method. See http://docs.oracle.com/javase/7/docs/api/index.html?java/sql/Driver.html.JDK 7 also brings support for minor changes in Rowset 1.1 defined at http://jcp.org/aboutJava/communityprocess/maintenance/jsr114/114MR2approved.pdf. The WebLogic Server implementation of the new RowSetFactory is called weblogic.jdbc.rowset.JdbcRowSetFactory.
Application Continuity is an Oracle database feature that provides a general purpose, application-independent infrastructure that enables recovery of work and masks many system, communication, and hardware failures. See Application Continuity.
Database Resident Connection Pooling (DRCP) is an Oracle database server feature that provides the ability to share connections among multiple connection pools that can span across mid-tier systems. See Database Resident Connection Pooling.
You can improve the connection testing performance of your Oracle data source by setting the Test Table Name attributed of the connection pool to SQL PINGDATABASE. See Oracle Database Connection Testing Using PINGDATABASE.
Global Data Services (GDS) is an Oracle database server feature that provides automated load balancing, fault tolerance and resource utilization in a distributed database environment. See Global Database Services.
This release extends the Pinned-to-Thread feature to an Active GridLink Data Source. Using Pinned-to-Thread can increase performance by minimizing the time it takes for an application to reserve a database connection from a data source and eliminating contention between threads for a database connection. See Using Pinned-To-Thread Property to Increase Performance.
In this release, you can configure and use an Active GridLink data source without enabling Fast Application Notification (FAN). See Using Active GridLink Data Sources without FAN Notification.
To simplify the configuration of large numbers of users, WebLogic Server provides a data source configuration option that sets the user for Identify based pooling and/or the client identifier directly using the WebLogic Server user, rather than using a credential mapper. See Understanding Data Source Security.
If you are using an Oracle 12c database with WebLogic Server release12.1.2 and higher, you are no longer required to provide the ONS Listener list as part of an Active GridLink data source configuration. The ONS list is automatically provided from the database to the driver. See Enabling FAN Events.
This release provides two new connection pool tuning attributes, CountOfTestFailuresTillFlush and CountOfRefreshFailuresTillDisable, that can improve performance in some situations by minimizing the delay caused by testing dead connections. See Connection Testing When Database Connections are Created.
WebLogic JDBC provides several new timer properties that allow you to tune the performance or your JDBC data sources:
weblogic.jdbc.gravitationShrinkFrequencySeconds
weblogic.jdbc.harvestingFrequencySeconds
weblogic.jdbc.securityCacheTimeoutSeconds
Identity based pooling was previously documented as not supported with pinned-to-thread. It is now flagged as a configuration error that causes a data source to fail to deploy. See Using Pinned-To-Thread Property to Increase Performance.
This document refers to the Derby database. The references regarding use of the Derby are equally applicable to Java DB. Java DB is Oracle's distribution of the open source Apache Derby Java database. It is distributed as part of the Java Development Kit. See Java DB at http://www.oracle.com/technetwork/java/javadb/overview/index.html.
Edition-based Redefinition is an Oracle database feature that enables you to upgrade the database component of an application while it is in use. See Enabling Edition-Based Redefinition.
Container Database (CDB) is an Oracle Database feature that minimizes the overhead of having many of databases by consolidating them into a single database with multiple Pluggable Databases (PDB) in a single CDB. See Container Database with Pluggable Databases.
WebLogic Server SmartUpgrade is an Oracle JDeveloper extension and command-line utility that analyzes the applications previously deployed on Oracle OC4J. It then offers advice and performs actions that can help you successfully redeploy the applications on Oracle WebLogic Server. You can analyze an application archive, or you can analyze an application or project you have opened in Oracle JDeveloper. In addition, SmartUpgrade can analyze the OC4J server where you deployed your applications and provide advice on how to set up a similar configuration in Oracle WebLogic Server. See Smart Upgrade Support for JDBC.
Many JDBC files that were located in the wlserver/server/lib directory have moved to the following locations:
The following files have moved to ORACLE_HOME/oracle_common/modules/datadirect:
The following files have moved to ORACLE_HOME/oracle_common/modules/oracle.jdbc_11.2.0:
The following files have moved to ORACLE_HOME/oracle_common/modules/oracle.nlsrtl_11.2.0:
The following files have moved to ORACLE_HOME/oracle_common/modules/oracle.ons_12.1.1:
The following files have moved to ORACLE_HOME/oracle_common/modules :