Enable set client ID on connection for a JDBC data source

When enabled, WebLogic Server sets a client ID on connection for the data source. When an application requests a database connection, WebLogic Server sets a light-weight client ID on the database connection. By default, it uses the credential mapping to map WebLogic Server user IDs to database user IDs. However, if UseDatabaseCredentials is set to true, then the credential mapping is not done and the WebLogic Server User ID is used directly as a database user ID.

Note:

This feature relies on features in the JDBC driver and DBMS. It is only supported for use with Oracle and DB2 databases and with the Oracle Thin and DB2 UDB JDBC drivers, respectively.

To configure homogeneous credential-based pooling for a JDBC data source:

If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
Navigate to the data source that you want to modify:
- Navigate to JDBC data source system resources
- Navigate to JDBC application modules
Select the Configuration: Identity Options page.
Select the Set Client ID On Connection check box and then click Save.
Note: Oracle Proxy Connection and Enable Identity Based Connection Pooling are mutually exclusive. If you think you need both mechanisms to pass security credentials in your application environment, create separate data sources -- one for with Oracle Proxy Connection and one with Enable Identity Based Connection Pooling.
If you are not using database credentials, map your WebLogic Server ID to a database ID. See Configure credential mapping for a JDBC data source.
To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
Not all changes take effect immediately—some require a restart (see Use the Change Center).

Administration Console Online Help

Enable set client ID on connection for a JDBC data source