This chapter describes the contents and organization of this guide—Administering JDBC Data Sources for Oracle WebLogic Server 12.1.3.
This chapter includes the following sections:
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 and higher 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.3.0 includes Oracle 12c JDBC drivers and is certified to operate with the Oracle 12c database. For details, see "Supported Configurations" in What's New in Oracle WebLogic Server.
For information on limitations when using Application Continuity, see Limitations with Application Continuity with Oracle 12c Database.
The Derby Database driver has been updated to version 10.10.1.1.
As part of a secure configuration, it may be necessary to provide one or more connection property values that should not appear as clear text in the Data Source descriptor file. Update existing Data Source configurations using the Encrypted Properties attribute. See Using Encrypted Connection Properties.
WebLogic Server provides two new connection pool properties, ConnectionLabelingHighCost and HighCostConnectionReuseThreshold, to allow a connection pool to use brand-new physical connections to serve connection requests from different tenants without incurring re-initialization overhead on other tenant connections already in the pool. See Using Initialization and Reinitialization Costs to Select Connections.
WebLogic Server supports callbacks, such as labeling and connection initialization, in EAR or WAR files used by packaged applications. See Using Connection Labeling with Packaged Applications.
weblogic.j2ee.descriptor.wl.JDBCOracleParamsBean.OracleEnableJavaNetFastPath is not supported in WebLogic Server 12.1.3. This functionality is always enabled by default for Oracle Exalogic environments.
A new Test Table name value of SQL ISVALID is now supported for Oracle databases. To improve connection testing performance of your Oracle data source, the default setting of the Test Table Name attribute of the connection pool is now SQL ISVALID. See Database Connection Testing Options.
As of this release, the CountOfTestFailuresTillFlush and CountOfRefreshFailuresTillDisable attributes are disabled when their value is set to 0. In prior releases, the value was 2147483647. See "JDBCConnectionPoolParamsBean" in the MBean Reference for Oracle WebLogic Server.
A default value of 10 minutes has been implemented for the weblogic.jdbc.securityCacheTimoutSeconds parameter. See Tuning Maintenance Timers
When the JDBC 4.0 setPoolable(false) method is called for a WebLogic data source that has prepared statement caching enabled, the statement is removed from the cache in addition to calling the method on the driver object. See Managing the Statement Cache for a Data Source.