WebLogic Server provides support for application data access to any database using a JDBC-compliant driver that meets the following requirements:
The driver must be thread-safe.
The driver must implement standard JDBC transactional calls, such as
setTransactionIsolation(), when used in transactional aware environments.
If the driver that does not implement serializable or remote interfaces, it cannot pass objects to an RMI client application.
When WebLogic Server features use a database for internal data storage, database support is more restrictive than for application data access. The following WebLogic Server features require internal data storage:
Container Managed Persistence (CMP)
JMS/JDBC Persistence and use of a WebLogic JDBC Store
JDBC Session Persistence
RDBMS Security Providers
Database Leasing (for singleton services and server migration)
JTA Logging Last Resource (LLR) optimization
The 11g version of the Oracle Thin driver (
ojdbc6.jar, ojdbc6_g.jar, and ojdbc6dms.jar for JDK 6) is installed with Oracle WebLogic Server.
WebLogic-branded DataDirect drivers are also installed with WebLogic Server. See Using WebLogic-branded DataDirect Drivers for more information.
In addition to the Oracle Thin Driver, the mySQL 5.1.x (mysql-connector-java-commercial-5.1.22-bin.jar) JDBC driver is installed with WebLogic Server.
This driver is installed in subdirectories of
$ORACLE_HOME/oracle_common/modules. The manifest in
weblogic.jar lists this file so that it is loaded when
weblogic.jar is loaded (when the server starts). Therefore, you do not need to add this JDBC driver to your
CLASSPATH. If you plan to use a third-party JDBC driver that is not installed with WebLogic Server, you must install the drivers, which includes updating your
CLASSPATH with the path to the driver files, and may include updating your
PATH with the path to database client files. See "Supported Configurations" in What's New in Oracle WebLogic Server.
If you plan to use a different version of any of the drivers installed with WebLogic Server, you can add the new file to the front of your
WebLogic Server also includes a version of the Derby DBMS installed with the WebLogic Server examples in the
WL_HOME\common\derby directory. Derby is an all-Java DBMS product included in the WebLogic Server distribution solely in support of demonstrating the WebLogic Server examples. For more information about Derby, see
If you plan to use a third-party JDBC driver that is not installed with WebLogic Server, you need to update the WebLogic Server's
classpath to include the location of the JDBC driver classes. Edit the
commEnv.cmd/sh script in
/common/bin and prepend your classes as described in "Modifying the Classpath" in the Command Reference for Oracle WebLogic Server.
For Globalization Support with the 11g version of the Oracle Thin driver, Oracle supplies the
orai18n.jar file, which replaces
nls_charset.zip. If you use character sets other than US7ASCII, WE8DEC, WE8ISO8859P1 and UTF8 with CHAR and NCHAR data in Oracle object types and collections, you must include
orai18n-mapping.jar in your
orai18n-mapping.jar are included with the WebLogic Server installation in the
\oracle_common\modules\oracle.nlsrtl_11.2.0 folder. These files are not referenced by the
weblogic.jar manifest file, so you must add them to your
CLASSPATH before they can be used.
\oracle_common\modules\oracle.jdbc_11.2.0 folder includes the
ojdbc6_g.jar (for JDK 6) file, which are the versions of the Oracle Thin driver with classes to support debugging and tracing. To use the Oracle Thin driver in debug mode, add the path to these files at the beginning of your