WebLogic Server: Behavior of "Set Client Id On Connection" and "Enable Identity-based Connection Pooling" on a JDBC Datasource (Doc ID 1349934.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle Weblogic Server - Version: 10.3.3 and later   [Release: and later ]
Information in this document applies to any platform.

Goal

  1. What is the usage of the "Set Client Id on Connection" and "Enable Identity based connection pooling" options available for the datasource being created in WebLogic Server?
  2. How will it behave for the scenarios mentioned below?
    • Credential mapping configured with actual username/password of Database.
    • Credential mapping configured with actual username but wrong password of Database.
    • Credential mapping configured with some random username/password which is not available in the Database.
  3. What is the usage of Credential Mapping with the username/password field, if it doesn't require the actual database username and password?

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms