Thursday, February 19, 2009

Weblogic Server

Using Third-Party Drivers with WebLogic Server

The following sections describe how to set up and use third-party JDBC drivers:


Overview of Third-Party JDBC Drivers

WebLogic Server works with third-party JDBC drivers that offer the following functionality:

  • Are thread-safe
  • Can implement transactions using standard JDBC statements
  • Third-party JDBC drivers that do not implement Serializable or Remote interfaces cannot pass objects to a remote client application.

For more information, see "Supported Database Configurations" in Supported Configurations for WebLogic Platform 8.1.

The following sections describe how to set up and use third-party JDBC drivers with WebLogic Server:

Using Third-Party JDBC Drivers Installed with WebLogic Server

The following third-party drivers are installed with WebLogic Server:

  • Oracle Thin Driver 10g and 9.2.0
  • Sybase jConnect 4.5 (jConnect.jar), 5.5 (jconn2.jar), and 6.0 (jconn3.jar)

Note: JDBC Driver support changed in the following releases:

    • In WebLogic Server 8.1SP3, the default version of the Oracle Thin driver was changed to the 10g driver (the version in WL_HOME\server\lib). In previous releases of WebLogic Server 8.1, the 9.2.0 version of the Oracle Thin driver was the default version of the driver.
    • In WebLogic Server 8.1SP6, support was added for the Sybase JConnect 6.0 (JDBC 2.0) driver.

Drivers installed with Weblogic server are located in the WL_HOME\server\lib folder (where WL_HOME is the folder where WebLogic Platform is installed) with weblogic.jar. The manifest in weblogic.jar lists these files so that they are loaded when weblogic.jar is loaded (when the server starts). Therefore, you do not need to add these JDBC drivers to your CLASSPATH.

Using Third-Party JDBC Drivers not Installed with WebLogic Server

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 WL_HOME/common/bin and prepend your classes as described in "Modifying the Classpath" in WebLogic Server Command Reference.

No comments:

Post a Comment