Enable identity-based connection pooling for a JDBC data source

Before you begin

Configure credential mapping for a JDBC data source

You can map WebLogic Server user IDs to database user IDs. If credential mapping is enabled on the data source, when an application requests a database connection from the data source, WebLogic Server determines the current WebLogic Server user ID and then sets the mapped database ID as a light-weight client ID on the database connection.

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 enable identity-based connection 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 tab.
Select the Enable Identity Based Connection Pooling check box and then click Save.
Note: Enable Credential Mapping 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 seperate data sources -- one for with Enable Credential Mapping and one with Enable Identity Based Connection Pooling.
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).